Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: deuling@de.ibm.com (Markus Deuling)
Cc: deuling@de.ibm.com (Markus Deuling),
	        brobecker@adacore.com (Joel Brobecker),
	        gdb-patches@sourceware.org (GDB Patches),
	        drow@false.org (Daniel Jacobowitz),
	kevinb@redhat.com (Kevin Buettner),
	        eliz@gnu.org
Subject: Re: [PING 2] [rfc]: Framework for looking up multiply defined global          symbols  in shared libraries
Date: Mon, 02 Jul 2007 18:24:00 -0000	[thread overview]
Message-ID: <200707021824.l62IORIn025947@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <4683D468.4090808@de.ibm.com> from "Markus Deuling" at Jun 28, 2007 05:31:52 PM

Markus Deuling wrote:

> Ok, I renamed the testsuite files to solib-symbol.exp and solib-symbol-{main,lib}.c The header has been removed.
> 
> I also changed the NEWS entry. Eli, is this ok ?

Thanks, Markus.


> @@ -2572,7 +2572,7 @@
>  	$(objfiles_h) $(exceptions_h) $(gdbcore_h) $(command_h) $(target_h) \
>  	$(frame_h) $(gdb_regex_h) $(inferior_h) $(environ_h) $(language_h) \
>  	$(gdbcmd_h) $(completer_h) $(filenames_h) $(exec_h) $(solist_h) \
> -	$(observer_h) $(readline_h)
> +	$(observer_h) $(readline_h) $(objfiles_h)
>  solib-frv.o: solib-frv.c $(defs_h) $(gdb_string_h) $(inferior_h) \
>  	$(gdbcore_h) $(solist_h) $(frv_tdep_h) $(objfiles_h) $(symtab_h) \
>  	$(language_h) $(command_h) $(gdbcmd_h) $(elf_frv_h) $(solib_h)

This part of the Makefile.in change does not appear to be necessary -- there is
no corresponding source code change to the solib-svr4.c file in the patch.

Please verify this, and re-send the patch with an up-to-date ChangeLog
entry -- I'll check it in then.


Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  parent reply	other threads:[~2007-07-02 18:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 12:33 [PING] " Markus Deuling
2007-05-10 13:00 ` Daniel Jacobowitz
2007-05-10 14:52   ` Markus Deuling
2007-05-14 17:53     ` Daniel Jacobowitz
2007-05-14 18:25 ` Daniel Jacobowitz
2007-05-15  5:49   ` Markus Deuling
2007-05-18  4:13     ` Markus Deuling
2007-05-31 21:40       ` Ulrich Weigand
2007-06-05  3:46         ` Markus Deuling
2007-06-20  6:58           ` [PING 2] " Markus Deuling
2007-06-26 18:31             ` Joel Brobecker
2007-06-26 18:35             ` Joel Brobecker
2007-06-26 20:34               ` Markus Deuling
2007-06-28 15:32                 ` Ulrich Weigand
2007-06-28 15:33                   ` Joel Brobecker
2007-06-28 18:20                   ` Markus Deuling
2007-06-29 17:03                     ` Eli Zaretskii
2007-07-02 18:24                     ` Ulrich Weigand [this message]
2007-07-03  4:04                       ` Markus Deuling
2007-07-03 12:17                         ` Ulrich Weigand
2007-07-03 12:28                           ` Daniel Jacobowitz
2007-07-04  3:50                           ` Markus Deuling
2007-06-29 17:15                   ` Eli Zaretskii
2007-06-25 21:48           ` [PING] " Kevin Buettner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200707021824.l62IORIn025947@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=deuling@de.ibm.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox