From: Jeffrey A Law <law@cygnus.com>
To: David Huggins-Daines <dhd@linuxcare.com>
Cc: Alan Modra <alan@linuxcare.com.au>,
Paul Bame <bame@noam.fc.hp.com>,
Alan Modra <amodra@puffin.external.hp.com>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Non-bootable kernel problems
Date: Fri, 14 Jul 2000 10:37:36 -0600 [thread overview]
Message-ID: <1970.963592656@upchuck> (raw)
In-Reply-To: Your message of 14 Jul 2000 12:02:37 EDT. <87lmz4zoma.fsf@linuxcare.com>
In message <87lmz4zoma.fsf@linuxcare.com>you write:
> Jeffrey A Law <law@cygnus.com> writes:
>
> > In message <Pine.LNX.4.21.0007141038590.15538-100000@front.linuxcare.co
> m.au>y
> > ou write:
> > > Zap these two lines, and I think the problem will go away.
> > But that's totally the wrong thing to do as it will break hpux.
> >
> > The linker is the problem.
>
> I've conditionalized it on the existence of GNU ld, is that okay?
No, because you're working around a bug in GNU-ld. GCC is following
the defined behavior for the PA32 ABI.
jeff
prev parent reply other threads:[~2000-07-14 16:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 23:35 [parisc-linux] Non-bootable kernel problems Richard Hirst
2000-07-13 17:14 ` Paul Bame
2000-07-13 18:46 ` David Huggins-Daines
2000-07-13 21:14 ` David Huggins-Daines
2000-07-13 19:20 ` Jeffrey A Law
2000-07-14 16:10 ` David Huggins-Daines
2000-07-14 16:39 ` Jeffrey A Law
2000-07-14 18:53 ` David Huggins-Daines
2000-07-14 20:40 ` David Huggins-Daines
2000-07-14 22:14 ` GAS fix for reloc problems (was Re: [parisc-linux] Non-bootable kernel problems) David Huggins-Daines
2000-07-15 8:33 ` Alan Modra
2000-07-15 1:31 ` [parisc-linux] Non-bootable kernel problems Alan Modra
2000-07-13 23:45 ` David Huggins-Daines
2000-07-14 0:44 ` Alan Modra
2000-07-14 16:02 ` Jeffrey A Law
2000-07-14 16:02 ` David Huggins-Daines
2000-07-14 16:37 ` Jeffrey A Law [this message]
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=1970.963592656@upchuck \
--to=law@cygnus.com \
--cc=alan@linuxcare.com.au \
--cc=amodra@puffin.external.hp.com \
--cc=bame@noam.fc.hp.com \
--cc=dhd@linuxcare.com \
--cc=parisc-linux@thepuffingroup.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