From: willy@thepuffingroup.com
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] latest glibc checked in
Date: Sat, 4 Mar 2000 23:34:20 -0500 [thread overview]
Message-ID: <20000304233420.D9944@thepuffingroup.com> (raw)
with that Implies checked in, it'll get as far as trying to build in the
csu directory. There's a problem with initfini.s -- the autogenerated
one looks something like this:
_init
.PROC
.CALLINFO
.ENTRY
/* cut here */
.EXIT
.PROCEND
and then the same for _fini. Then there's a nasty little sed script
which cuts the file into chunks and leaves the chunk before `cut here'
in one file and the chunk after in another. So I just delete the 5
directives there and then type `make' and it carries on compiling merrily.
I suspect gcc needs to be fixed to not output those directives for ELF.
Just so I know (not so I can hold your feet to the fire), who's interested
in doing toolchain work, and who's interested in doing glibc work?
next reply other threads:[~2000-03-05 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-05 4:34 willy [this message]
2000-03-07 3:10 ` [parisc-linux] latest glibc checked in Ulrich Drepper
-- strict thread matches above, loose matches on Subject: below --
2000-03-05 0:19 Michael Ang
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=20000304233420.D9944@thepuffingroup.com \
--to=willy@thepuffingroup.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