Bug 16993 - compiling QT fails with __res_state undef...
compiling QT fails with __res_state undef...
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
7.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-26 17:36 EDT by Need Real Name
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-29 21:05:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-08-26 17:36:16 EDT
to reproduduce, install pinstripe iso.
download QT source, do ./configure, then make.
It builds the libraries but on the first app
link it says...

g++ -L/grumpy/peter/src/kde_cvs/qt-copy/lib
-Wl,-rpath,/grumpy/peter/src/kde_cvs/qt-copy/lib -L/usr/X11R6/lib
-Wl,-rpath,/usr/X11R6/lib   -o /grumpy/peter/src/kde_cvs/qt-copy/bin/uic
uic.o ../shared/widgetdatabase.o ../shared/domtool.o   -lqutil -L../lib
-lqt -lXext -lX11 -lm   -lSM -lICE -L/usr/X11R6/lib -lGLU -lGL -lXmu
-lresolv
/grumpy/peter/src/kde_cvs/qt-copy/lib/libqt.so: undefined reference to
`__res_state(void)'
collect2: ld returned 1 exit status
make: *** [/grumpy/peter/src/kde_cvs/qt-copy/bin/uic] Error 1
[peter@grumpy uic]$ pwd
/gr

[peter@grumpy qt-copy]$ nm /usr/lib/libresolv.so | grep res_stat
         U __res_state@@GLIBC_2.2
[peter@grumpy qt-copy]$   

Is it a glibc thing?
Comment 1 Need Real Name 2000-08-27 22:21:26 EDT
I entered "pinstripe" as the version, initially, but that got changed into 4.2.
Suspect a problem in bigzilla.

oh... and it's the network/qdns.cpp module implicitly using __res_state.
The #includes look ok (the struct is defined in resolv.h, which looks like
it is included) Why is it saying it's a (void) ?

Comment 2 Jakub Jelinek 2000-09-01 05:29:29 EDT
It was a bug in glibc's resolv.h header, fixed on 2000-08-09.

Note You need to log in before you can comment on or make changes to this bug.