From: bame@puffin.external.hp.com
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] New glibc and new linker SEGV
Date: Fri, 02 Jun 2000 16:39:12 -0600 [thread overview]
Message-ID: <m12y05x-001VscC@chalet> (raw)
I mergeed our glibc with June 1 sources from sourceware.cygnus.com
and it appears to be pretty healthy so I'm committing it. FYI the
CVS e-mail message is truncated because after 30 minutes of CPU time
I got tired of waiting for the damn perl script and killed it :->
However the glibc build needs to be faked out a bit because the latest
(otherwise pretty darn good) linker is dying inside the glibc build
with:
hppa1.1-linux-gcc -nostdlib -nostartfiles -o locale/localedef [...]
collect2: ld terminated with signal 11 [Segmentation fault], core dumped
make[2]: *** [/work/xc-build/build-glibc/locale/localedef] Error 1
Since these glibc-built executables aren't being used yet, I fake out
the build by doing "cp /bin/date locale/localedef", then run make again,
copy /bin/date over the next failed link target, repeat until the make
succeeds.
Oh, and if you see
test ! -d CVS || cvs commit -m'Regenerated from ../sysdeps/gnu/errlist.awk ../manual/errno.texi' ../sysdeps/gnu/errlist.c
Permission denied
just restart the make :-(
I updated the pre-built toolchain for Debian potato x86 at
ftp://puffin.external.hp.com/pub/parisc/binaries/tgz/elf32x86.tar.gz
-Paul Bame
next reply other threads:[~2000-06-02 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-02 22:39 bame [this message]
[not found] <Pine.LNX.4.21.0006031200490.22936-100000@front.linuxcare.com.au>
2000-06-03 4:23 ` [parisc-linux] New glibc and new linker SEGV Alan Modra
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=m12y05x-001VscC@chalet \
--to=bame@puffin.external.hp.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 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.