From: Sean Upton <seanupton@yahoo.com>
To: ultralinux@vger.kernel.org
Subject: glibc 2.1.3 Build - locale/C-ctype.c
Date: Thu, 30 Nov 2000 22:56:49 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-97562491722740@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
2 quick questions...
I have sort of naively stumbled on to a problem and
solution in building glibc 2.1.3 on sparc. Buillding
a custom distro, and I was trying to build glibc 2.1.3
on an Ultra 10 in sparc32 mode, and had a problems
building it with gcc 2.95.3 and 2.95.2, because
compile failed due to parse error in locale/C-ctype.c
that seemsed sort of weird. I believe this issue was
a syntax problem that prevented compilation on
big-endian arcitectures (look at the code, you'll see
what I mean). I added a comma to line 377 and tried
rebuilding, with 100% success. diff output is
attached. Has anyone else seen this, and would
patching this file in this manner cause problems for
little-endian boxes?
2.1.3 deals with endian issues with preprocessor
directives, from looking at the code in glibc 2.2, it
deals with the endian issues differently, so this
should be a non-issue with 2.2. Has anyone had decent
luck using glibc running on sparc/linux?
C-ctype.c:379: parse error before `{'
C-ctype.c:382: parse error before `}'
make[2]: ***
[/lfs/usr/src/glibc-build/locale/C-ctype.o] Error 1
Thanks in advance,
Sean
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
[-- Attachment #2: sparc.diff --]
[-- Type: application/x-unknown, Size: 141 bytes --]
next reply other threads:[~2000-11-30 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 22:56 Sean Upton [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-01 8:24 glibc 2.1.3 Build - locale/C-ctype.c Andreas Jaeger
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=marc-linux-ultrasparc-97562491722740@msgid-missing \
--to=seanupton@yahoo.com \
--cc=ultralinux@vger.kernel.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