From: hjl@nynexst.com (H.J. Lu)
To: raeburn@cygnus.com (Ken Raeburn)
Cc: gas2@cygnus.com, bfd@cygnus.com
Subject: Re: procfs patches for Linux
Date: Tue, 25 Apr 1995 07:27:00 -0000 [thread overview]
Message-ID: <9504251425.AA21877@titanic.nynexst.com> (raw)
In-Reply-To: <9504250459.AA05647@cujo.cygnus.com>
>
>
> As I understand it, a.out versus ELF is not the issue. As Mike
> explained it to me, the procfs support is at least somewhat separate
> from the a.out/ELF issue.
>
> The problem is whether the ELF support can be compiled. With this
> change, anyone who wants to build the gas snapshots targeted for any ELF
> configuration -- be it i386-linux or powerpc-elf or sparc-solaris or
> anything else -- has to have your latest software, only a few days old.
>
> Because of the way BFD is set up, core file support is compiled in even
> for cross configurations. (This is a bug, and I'll happily take patches
> to fix it.) So the Linux core file support has to compile, because
Will you? Please take a look at below.
> people may be using Linux as a development system for a cross-assembler.
That was what I faced more than 2 years ago while bootstrapping
gcc for Linux in a cross-compile environment. One solution is:
# cd bfd
# mdkir targets
# cd targets
We move all the target stuff from bfd/hosts to bfd/targets. In
bfd/configure, we do:
2. if [ -f $srcdir/targets/target.h ]; then
link $srcdir/targets/target.h to tsysdep.h.
link $srcdir/hosts/host.h to hsysdep.h.
echo include "hsysdep.h" > sysdep.h
echo include "tsysdep.h" >> sysdep.h
else
link $srcdir/hosts/host.h to sysdep.h.
fi
>
> I'm not entirely convinced that the switch to ELF as the default for gcc
> and binutils won't screw some of those people, where version numbers
> aren't factored into it in any way. Have you gotten into the FSF's gcc
> documentation (and, ideally, into the release announcement too) some
> notes about using "linuxaout" if people have older Linux systems? Or do
Yes. I changed install.texi for gcc. But again, I am not sure if
they will read it.
> you just assume everyone always wants the latest development code,
> stability be damned?
>
> I'm disabling HAVE_PROCFS for Linux in BFD for now, until you can give
> me something that supports both system environments, with sys/procfs.h
> and without.
>
I will fix it on the linux side. How about my suggestion to
bfd?
BTW, do you need a patch for elf32.em to fix the -Lxxxx bug?
--
H.J. Lu
NYNEX Science and Technology, Inc. hjl@nynexst.com
next parent reply other threads:[~1995-04-25 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9504250459.AA05647@cujo.cygnus.com>
1995-04-25 7:27 ` H.J. Lu [this message]
1995-04-25 9:52 ` Ken Raeburn
1995-04-25 10:51 ` H.J. Lu
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=9504251425.AA21877@titanic.nynexst.com \
--to=hjl@nynexst.com \
--cc=bfd@cygnus.com \
--cc=gas2@cygnus.com \
--cc=raeburn@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).