* [Linux-ia64] Error compiling c++ support with glibc 2.2
@ 2000-10-05 16:55 Michael Madore
2000-10-05 17:49 ` Jim Wilson
2000-10-05 17:55 ` Ulrich Drepper
0 siblings, 2 replies; 3+ messages in thread
From: Michael Madore @ 2000-10-05 16:55 UTC (permalink / raw)
To: linux-ia64
Hi,
I'm getting the following error when trying to compile the 0925 gnupro on
glibc 2.2(From 10/02 CVS):
/usr/src/turbo/BUILD/gnupro-2.96/build/gcc/g++ -B/usr/src/turbo/BUILD/gnupro-2.96/build/gcc/ -B/usr/ia64-cygnus-linux/bin/ -L/usr/src/turbo/BUILD/gnupro-2.96/build/ia64-cygnus-linux/libstdc++ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates -I. -I../../../src/libio -nostdinc++ -D_IO_MTSAFE_IO ../../../src/libio/isgetline.cc
../../../src/libio/iostream.cc: In method `istream &istream::get (char
&)':
./../../src/libio/iostream.cc:75: `_IO_USER_LOCK' undeclared (first
use this function)
../../../src/libio/iostream.cc:75: (Each undeclared identifier is
reported only once for each function it appears in.)
../../../src/libio/isgetline.cc: In method `istream &istream::getline
(char *, int, char)':
../../../src/libio/isgetline.cc:41: `_IO_USER_LOCK' undeclared (first
use this function)
../../../src/libio/isgetline.cc:41: (Each undeclared identifier is
reported only once for each function it appears in.)
make[1]: *** [isgetline.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [iostream.o] Error 1
make[1]: Leaving directory `/usr/src/turbo/BUILD/gnupro-2.96/build/ia64-cygnus-linux/libio'
make: *** [all-target-libio] Error 2
Bad exit status from /var/tmp/rpm-tmp.11588 (%build)
According to Jim Wilson, iostream.cc is including
/usr/include/bits/stdio-lock.h which references _IO_USER_LOCK. However,
_IO_USER_LOCK is defined in /usr/include/libio.h which is not being
included. Has anyone else run accross this problem? Any solutions?
Thanks
--
Mike Madore
Software Engineer
TurboLinux, Inc.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Linux-ia64] Error compiling c++ support with glibc 2.2
2000-10-05 16:55 [Linux-ia64] Error compiling c++ support with glibc 2.2 Michael Madore
@ 2000-10-05 17:49 ` Jim Wilson
2000-10-05 17:55 ` Ulrich Drepper
1 sibling, 0 replies; 3+ messages in thread
From: Jim Wilson @ 2000-10-05 17:49 UTC (permalink / raw)
To: linux-ia64
I have since noticed that the same bug got reported to gcc-bugs, and a
patch was applied Sept 23 which should fix this problem. I have not yet
tried to extract the patch and test it.
2000-09-23 Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
* stdstreams.cc: Include <libio.h>, not "libio.h".
* iolibio.h: Likewise.
(_IO_pos_BAD): Use _IO_off_t instead of _IO_fpos_t.
* libio.h (_IO_USER_LOCK): Define.
http://gcc.gnu.org/ml/gcc-bugs/2000-09/msg00563.html
Jim
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Linux-ia64] Error compiling c++ support with glibc 2.2
2000-10-05 16:55 [Linux-ia64] Error compiling c++ support with glibc 2.2 Michael Madore
2000-10-05 17:49 ` Jim Wilson
@ 2000-10-05 17:55 ` Ulrich Drepper
1 sibling, 0 replies; 3+ messages in thread
From: Ulrich Drepper @ 2000-10-05 17:55 UTC (permalink / raw)
To: linux-ia64
Jim Wilson <wilson@cygnus.com> writes:
> I have since noticed that the same bug got reported to gcc-bugs, and a
> patch was applied Sept 23 which should fix this problem. I have not yet
> tried to extract the patch and test it.
This patch is correct, you can apply it.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2000-10-05 17:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-10-05 16:55 [Linux-ia64] Error compiling c++ support with glibc 2.2 Michael Madore
2000-10-05 17:49 ` Jim Wilson
2000-10-05 17:55 ` Ulrich Drepper
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox