bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Minor compilation bug on Linux


From: Eric
Subject: Minor compilation bug on Linux
Date: Thu, 25 Sep 2003 09:41:51 -0500
User-agent: KMail/1.5.1

Hello,
        I would like to report a minor bug but I can't access the bug database. 
I am 
trying to connect to Bug Database  http://bugs.gnu.org/cgi-bin/gnatsweb.pl
and it times out.Anyhow Glibc 2.3.2/GCC somehow generates a weird 
csu/version-info.h file that stops the compilation process.
I can reproduce this everytime.
        System Glibc/GCC
                GNU C Library stable release version 2.3.2, by Roland McGrath 
et al.
                Compiled by GNU CC version 3.3 20030226 (prerelease) (SuSE 
Linux).
                Compiled on a Linux 2.4.20 system on 2003-03-13.
        Glibc: 2.3.2
        Configure line: ../glibc-2.3.2/configure --enable-add-ons=linuxthreads 
--prefix=/ --enable-kernel=2.4.21

The file generated looks like this
csu/version-info.h
"Compiled on a Linux 2.4.20 system on 2003-09-25.
"
"Available extensions:
"
"       GNU libio by Per Bothner\n"
"       crypt add-on version 2.1 by Michael Glad and others\n"
"       linuxthreads-0.10 by Xavier Leroy\n"
"       BIND-8.2.3-T5B\n"
"       libthread_db work sponsored by Alpha Processor Inc\n"
"       NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk\n"
Notice that it is missing quotation marks on the right side so the process 
stops. Whenever I try a clean build this happens. I just edit in the quotes 
and it builds fine. However this is very annoying when I have to recompile 
several times as the edited file is deleted at make clean and or make 
distclean.

Is this a Glibc bug? Or maybe linuxthreads is adding its info wrong? Or maybe 
even GCC. I hope this information helps. Let me know if I should post this 
info to the GCC or linux-threads list instead.

CC me if you need to, I am not subscribed to the list.

----------------------
Eric Bambach   
Eric (at) CISU (dot) net 
----------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]