From: Jeremy Katz <katzj@linuxpower.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Problems Rebuilding glibc
Date: Fri, 19 Nov 1999 15:52:08 -0500 [thread overview]
Message-ID: <19991119155208.I31049@blackhole.ncssm.net> (raw)
Hi. I'm currently working on getting all sorts of kerberos/afs/hesiod
nastiness working under linuxppc. At present, doing this requires a
patch to glibc for hesiod initgroups support (I actually think that the
patch is in the current cvs tree for glibc, but didn't quite make it
into the glibc-2.1.2 release). Unfortunately, while trying to rebuild
the rpm with the patches, I get the following internal compiler error --
rtld.c:143: warning: `_dl_start' defined but not used
/usr/src/redhat/BUILD/egcs-1.1.2/gcc/config/rs6000/rs6000.c:2296:
Internal compiler error in function rs6000_got_register
make[2]: ***
[/home/katzj/projects/redhat/BUILD/glibc-2.1/build-ppc-linux/elf/dl-profile.os]
Error 1
make[2]: Leaving directory `/mnt/home/katzj/BUILD/glibc-2.1/elf'
make[1]: *** [elf/subdir_lib] Error 2
make[1]: Leaving directory `/mnt/home/katzj/BUILD/glibc-2.1'
make: *** [all] Error 2
Bad exit status from /var/tmp/rpm-tmp.66411 (%build)
Note that I'm building using the glibc rpm from RedHat 6.1 with the one
necessary patch. Are there any PPC specific patches which need to be
applied (from looking at the srpm for the normal linuxppc glibc, it
doesn't look like it)
Thanks,
Jeremy
PS Please CC me as I'm only subscribed to linuxppc-dev-digest
--
Jeremy Katz http://linuxpower.org
Personal: katzj@linuxpower.org
School: jlkatz@unity.ncsu.edu
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-11-19 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-19 20:52 Jeremy Katz [this message]
1999-11-19 21:03 ` Problems Rebuilding glibc David Edelsohn
1999-11-19 21:25 ` Franz Sirl
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=19991119155208.I31049@blackhole.ncssm.net \
--to=katzj@linuxpower.org \
--cc=linuxppc-dev@lists.linuxppc.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 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 NNTP newsgroup(s).