On Mon, Nov 12, 2007, Jeff Johnson wrote:

> On Nov 11, 2007, at 10:26 PM, David Halik wrote:
>>
>> First let me say, congrats on the first 5.0 release! (even if it is alpha
>> ;) I was able to take out a bunch of my patches and it seems to compile
>> much cleaner in general than 4.4.9.
>>
>> It looks like I'm running into some kind of internal linking issue, or
>> maybe a missing header that needs to be pointed to during the rpmconstant
>> portion of the build. Up until that this point it had been running
>> smoothly and I thought it might actually go all the way. For most Sun
>> Studio issues I usually have a work around up my sleeve, but this seems to
>> be something internal since these are all defined within the package.
>>
>> cc -g -xs -D_GNU_SOURCE -D_REENTRANT -D_LARGEFILE64_SOURCE -DNE_LFS -o
>> .libs/rpmconstant constant.o  -L/usr/local/lib -L/usr/local/ssl/lib
>> ./.libs/librpmconstant.so -ldl -lm -lpopt -lbeecrypt -lpthread
>> /usr/local/lib/libneon.so -lssl -lcrypto -lnsl -lsocket -lz
>> /usr/local/lib/libexpat.so  -R/usr/local/lib -R/usr/local/ssl/lib
>> Undefined                       first referenced
>>  symbol                             in file
>> rpmdsInit                           constant.o
>> rpmdsNext                           constant.o
>> rpmdsTagN                           constant.o
>> rpmHeaderFormats                    constant.o
>> hdrVec                              constant.o
>> rpmTagTable                         constant.o
>> rpmdsSearch                         constant.o
>> rpmdsResult                         constant.o
>> rpmTags                             constant.o
>> rpmdsIx                             constant.o
>> rpmdsDNEVR                          constant.o
>> rpmdsSetResult                      constant.o
>> ld: fatal: Symbol referencing errors. No output written to
>> .libs/rpmconstant
>>
>> Any thoughts?
>
> Weird. None of those symbols are used (or needed by) rpmconstant.
> [...]
>
> Here's what I see on linux/i386 w gcc:
> [...]

Same for me. I even tried under sparc64-solaris9 today myself and at
least with the "./devtool standalone" procedure and CC=gcc I *CANNOT*
reproduce the problem. Either it is related to the used C compiler
(perhaps Sun Studio?) or some other local problem.

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com