From: hjl@lucon.org (H.J. Lu)
To: hro@barney.lanl.gov (Heinrich Roder)
Cc: egcs@cygnus.com
Subject: Re: make dies in libio
Date: Tue, 04 Nov 1997 14:22:00 -0000 [thread overview]
Message-ID: <m0xSrMj-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: <199711042303.QAA20687@barney.lanl.gov>
>
> Does anyone know about this? I am running RH4.2, gnulibc2.0.5,
> NU ld version 2.8.1 (with BFD linux-2.8.1.0.1), libg++2.7.2.8,
> libc5.4.38, and the make goes until here:
> .
> .
> .
> .
>
>
> test -z "" || \
> /packages/egcs-971031/gcc/xgcc -B/packages/egcs-971031/gcc/ -c -O2 -g -fvtable-thunks -fno-implicit-templates -I. -I. -nostdinc++ -D_IO_MTSAFE_IO stdstrbufs.cc -o pic/stdstrbufs.o
> /packages/egcs-971031/gcc/xgcc -B/packages/egcs-971031/gcc/ -c -O2 -g -fvtable-thunks -fno-implicit-templates -I. -I. -nostdinc++ -D_IO_MTSAFE_IO stdstrbufs.cc
> stdstrbufs.cc:67: syntax error before `='
> stdstrbufs.cc:67: `_IO_stdfile_0_lock' was not declared in this scope
> stdstrbufs.cc:67: warning: excess elements in aggregate initializer
> stdstrbufs.cc:68: syntax error before `='
> stdstrbufs.cc:68: `_IO_stdfile_1_lock' was not declared in this scope
> stdstrbufs.cc:68: warning: excess elements in aggregate initializer
> stdstrbufs.cc:69: syntax error before `='
> stdstrbufs.cc:70: `_IO_stdfile_2_lock' was not declared in this scope
> stdstrbufs.cc:70: warning: excess elements in aggregate initializer
> make[1]: *** [stdstrbufs.o] Error 1
> make[1]: Leaving directory `/packages/egcs-971031/libraries/libio'
> make: *** [all-target-libio] Error 2
>
You may need a patch to glibc header files. Please check
the egcs archive. I think I have posted it a few times.
BTW, please use the one for glibc 2.0.5c, not glibc 2.1.
H.J.
prev parent reply other threads:[~1997-11-04 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-04 14:02 Heinrich Roder
1997-11-04 14:22 ` H.J. Lu [this message]
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=m0xSrMj-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=hro@barney.lanl.gov \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).