From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org, dave.anglin@nrc-cnrc.gc.ca
Subject: Re: [parisc-linux] 64-bit kernel builds with gcc-3.4 experimental cross.
Date: Wed, 17 Sep 2003 18:54:07 -0400 [thread overview]
Message-ID: <20030917225406.GG30176@systemhalted> (raw)
In-Reply-To: <200309171643.h8HGhJlw013649@hiauly1.hia.nrc.ca>
On Wed, Sep 17, 2003 at 12:43:18PM -0400, John David Anglin wrote:
> > Any thoughts? This ld was from a multi-arch binutils that had
> > enable-targets with hppa64-linux.
> >
> > ---
> > hppa64-linux-ld -r -o kernel.o sched.o dma.o fork.o exec_domain.o
> > panic.o printk.o module.o exit.o itimer.o info.o time.o softirq.o
> > resource.o sysctl.o acct.o capability.o ptrace.o timer.o user.o signal.o
> > sys.o kmod.o context.o
> > hppa64-linux-ld: Relocatable linking with relocations from format
> > elf32-hppa-linux (sched.o) to format elf32-hppa-linux (kernel.o) is not
> > supported
>
> As far as I know, there is no multi-arch support in ld or as.
> There isn't multi-arch support in GCC either. You need separate
> compilers for 32 and 64 bits.
Separate compilers yes. Separate linker and assembler no.
I thought I could use '--enable-targets=hppa64-linux' in binutils.
c.
next prev parent reply other threads:[~2003-09-17 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 16:18 [parisc-linux] 64-bit kernel builds with gcc-3.4 experimental cross Carlos O'Donell
2003-09-17 16:43 ` John David Anglin
2003-09-17 22:54 ` Carlos O'Donell [this message]
2003-09-17 23:15 ` John David Anglin
2003-09-18 0:38 ` Matthew Wilcox
2003-09-18 1:40 ` Carlos O'Donell
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=20030917225406.GG30176@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.