At 16 Jun 2003 22:46:34 -0600, Eric W. Biederman wrote: > > Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > > > It compiles fine here. I suspect you have a bad copy of libc or > > binutils somewhere in your system; make sure it's using the right > > headers, libraries, and linker please. > > Hmm. How weird.... I am looking. > > Ok. I have tracked it down and I'm not certain what to grumble at. > The tip off was checking the libraries gcc -print-search-dirs reported. > > I had some libraries for a home spun x86-64 cross compiler installed > in i386-linux. gcc was search in there and finding an old copy of glibc-2.2 > Which explains why the new symbols were not found. > > I will agree that i386-linux was not the best name for a cross > compiler directory. But why was that being searched before lib?
I guess your old copy is derived from SuSE's or something? x86-64 in debian is under development, so it's not a "bug", I think. (I don't know well, but I guess x86-64 might be designed to be capable for both ia32 and amd64). BTW, this bug seemed being fixed, so could I close it? Regards, -- gotom
