From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] glibc build fails / bash bug
Date: Sun, 12 Nov 2000 11:06:38 -0700 [thread overview]
Message-ID: <20001112110638.A1005@tausq.org> (raw)
Bdale, taggart and I have been looking at trying to build glibc on hppa
from Debian's sources. What we saw was that it looks like a lot of the
syscalls were not being reocognized as such by one part of the build, so
it tries to build things from the sysdeps/generic directory and fails.
After a lot of digging, I *think* what is at fault is actually bash. It
looks like during the build, a shell script (make-syscalls.sh) parses
through syscalls.list to generate syscall stubs that are needed for the
build to happen correctly, but these are not being generated. What it
boils down to, I think, is this:
(on hppa - bdale's J5K)
=============================
tausq@j5k:/space/tausq $ bash --version
GNU bash, version 2.04.0(1)-release (hppa-unknown-linux-gnu)
Copyright 1999 Free Software Foundation, Inc.
tausq@j5k:/space/tausq $ dpkg -l |grep bash
ii bash 2.04-7 The GNU Bourne Again SHell
tausq@j5k:/space/tausq $ cat test.sh
#!/bin/sh
echo "1 2 3 4 5
a b c d e
" |
while read a b c d e; do
echo $a $b $c $d $e
done
tausq@j5k:/space/tausq $ /bin/bash test.sh
1 2 3 4 5
=============================
(on other archs, tested with i386 and sparc)
samwise[11:06] ~% bash --version
GNU bash, version 2.04.0(1)-release (i386-pc-linux-gnu)
Copyright 1999 Free Software Foundation, Inc.
samwise[11:06] ~% dpkg -l |grep bash
ii bash 2.04-7 The GNU Bourne Again SHell
samwise[11:06] ~% /bin/bash test.sh
1 2 3 4 5
a b c d e
This causes the parsing routines to die quite miserably....
Anyone feel like trying to fix this? :-)
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next reply other threads:[~2000-11-12 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-12 18:06 Randolph Chung [this message]
2000-11-12 20:27 ` [parisc-linux] glibc build fails / bash bug bame
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=20001112110638.A1005@tausq.org \
--to=randolph@tausq.org \
--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