I am trying to compile a C program on Red Hat 9.0 and it works great until I add the -static option to this compile script :

gcc program.c -oprogram -lXm -lXmu -lXt -lX11 -lm \
-L/usr/X11R6/LessTif/Motif1.2/lib \
-L/usr/X11R6/lib -I/usr/X11R6/LessTif/Motif1.2/include

It lists a bunch of 'undefined references' all of which seem to be in
/usr/include/pthread.h & /usr/include/X11/SM/SMlib.h

I know these headers are getting in, because I can add the -E switch and look at the results of the perprocessor output. And the definitions are there!!

What is going on ?? I have lost two days over this, so any help would be apprectiated.

Thanks
Craig

Since nobody else has replied, I'll take a shot at it... Do you have the right version of each library installed? If I'm not mistaken, libraries ending in ".so" are shared object libraries. Libraries ending in ".a" are the static equivalents. I think you can only statically link using the appropriate ".a" version of the library.

I may be way off base, but I guess it's a place to start. I'm sure someone else will correct me if I'm mistaken though.

do you mean undefined reference or unresolved external, theres a big difference. an undefined reference is caused by something wrong with the code, an unresolved external is when a symbol cant be found in the supplied libraries, as the error happends when you compile with the -static flag i'll take a guess at an unresolved external. this means you are missing the static archive version of the library or as Dark_Helmet says "the .a version" so depending on your distribution you want the static devel .rpm/.deb/.epkg/.tar.gz, if your distribution is mandrake then i wish you luck, else they shouldnt be too hard to find.

No, these are 'undefined reference to 'SmcCloseConnection' (as an example) . 'SMlib.h' contains the declaration for most all of the error messages I am getting, and it is included in the output code of the preprosessor. I am stumped !! Any other ideas??

Hmmmm... did you compile the libraries yourself, or did you install them as binaries from rpm's or the like? If from source, were there any compilation options that might influence the way the libraries are built? I would figure both libraries would suffer the same problem if that were the case... Was the code snagged as a stable release or CVS?

Is there any chance that maybe the include headers and the compiled library don't match up? I mean something like the library is version 1.2, and the headers are version 1.1?

Another grasp at straws: what is the name of the library you're trying to include? I'm going to assume it's 'SMlib' since that's the name of the header you mentioned. Doesn't the command line need "-lSMlib" in that case? The only reason I mention it is that the error sounds very similar to if you were to use the sqrt() function, but forget to add the "-lm" option to gcc.

I installed the libraries as RPM's thru the standard install process of redhat 9.0. The error message is coming from functions in the libXt.a and libX11.a libraries with reference to definitions that should be in the SMlib.h and pthread.h header files. I know these header files are being included because I can see them. There is no SMlib, but I did add -lSM and the errors changed to ICE related. I just added -lICE and now the only errors are 'pthread' related. So, I think you have me on the right track. THANK-YOU!!! What library calls the pthread.h header?

I don't know for certain. I thought all the pthread code was a part of glibc, and I'm reasonably certain glibc is automatically included whenever you compile anything.

Are you getting the same types of unresolved errors, or are they different?

how about /usr/lib/libpthread.{a,so} so maybe try -lpthread

I had a problem which looks quite similar. Do a search on user="bwMarkus", there's also a problem with static linking.