This is the mail archive of the
mailing list for the GDB project.
Re: S/390 Linux doesn't link on trunk
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Dr. Jochen Röhrig <roehrig at de dot ibm dot com>
- Cc: gdb at sources dot redhat dot com, msnyder at redhat dot com
- Date: Mon, 15 Apr 2002 13:11:11 -0400
- Subject: Re: S/390 Linux doesn't link on trunk
- References: <20020407173859.A31836@nevyn.them.org> <02041519022500.02708@kontiki>
On Mon, Apr 15, 2002 at 07:02:25PM +0200, Dr. Jochen Röhrig wrote:
> The problem arises from the unconditional definition of
> CHILD_PID_TO_EXEC_FILE at the end of config/nm-linux.h. According to the
> CVS-log this was added in Revision 1.11 of config/nm-linux.h on January, 8th.
> There were also changes made in config/<arch>/linux.mh for some architectures
> (linking with linux-proc.o), which, as far as I can judge it, avoid the above
> described problem on theses architectures. However s390 (and, as it seems,
> some other architectures), doesn't have a config/<arch>/linux.mh so no
> modifications were made for s390.
> My question now: are we missing something for s390 because we don't have the
> config/s390/linux.mh-file or are the changes to config/s390/nm-linux.h that I
> described above a correct solution for the problem? Or would it instead be a
> better solution to add a "NATDEPFILES += linux-proc.o" to config/s390/s390.mh?
Aha! That's a good solution. A better one is to kill
config/s390/s390.mh, create config/s390/linux.mh, and use that instead.
That's much more accurate and will help prevent this sort of error
Michael, sound right to you? I can't think of any reason not to use
linux-proc.o on S/390.
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer