From: David Huggins-Daines <dhuggins@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Weekly News [2000/02/18]
Date: 18 Feb 2000 21:43:37 -0500 [thread overview]
Message-ID: <ltaekxnc86.fsf@doppelbock.thepuffingroup.com> (raw)
In-Reply-To: willy@thepuffingroup.com's message of "Fri, 18 Feb 2000 21:26:19 -0500"
willy@thepuffingroup.com writes:
> * The ELF toolchain has received some updates this week. Sammy
> contributed initial support for Linux/PARISC ELF32. Matthew contributed
> some build fixes for HP/UX and David H-D contributed Debian and Red
> Hat build support for x86.
And Alpha - actually someone needs to build an i386 binary package for
Debian. Note that the Debian build support is in CVS, so you can just
run 'debian/rules build && fakeroot debian/rules binary-arch' from
within a checked-out tree to get a binary package for your
architecture.
Sammy or some other toolchain hacker: can you look at the diff from
the SRPM? I haven't checked it into CVS because it's a really bad
kludge, but it's needed to compile on Alpha.
As far as I can tell, BFD64 gets defined if either the target *or* the
host is 64-bit. The assembler and linker code then expects that it is
being built for a 64-bit target, but the build system (rightly) obeys
the arch specification string and only builds elf32 targets in BFD.
--
David Huggins-Daines, Senior Linux Consultant, Linuxcare, Inc.
613.562.1239 tel
dhuggins@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
prev parent reply other threads:[~2000-02-19 3:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-19 2:26 [parisc-linux] Weekly News [2000/02/18] willy
2000-02-19 2:43 ` David Huggins-Daines [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=ltaekxnc86.fsf@doppelbock.thepuffingroup.com \
--to=dhuggins@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