Continued here from a post on the LQ Slackware forum:

Trying to compile your source for PDV.
This is what happens when I attempt to compile the Payload Delivery Vehicle using src2pkg:

/tmp/cce0I8rK.o: In function `cmpspecandwidgets':
util.c.text+0x574): undefined reference to `g_pdvspec'
util.c.text+0x579): undefined reference to `cmpspec'
util.c.text+0x585): undefined reference to `freespecmembers'
/tmp/cce0I8rK.o: In function `statusmsg':
util.c.text+0x680): undefined reference to `g_statusw'
util.c.text+0x6a6): undefined reference to `g_statusw'
util.c.text+0x6b2): undefined reference to `XmTextSetString'
collect2: ld returned 1 exit status
make[2]: *** [util.o] Error 1
make[2]: Leaving directory `/usr/src/panoplyx/tmp/pdv-1.5.1-src-1panoplyx/X11'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/panoplyx/tmp/pdv-1.5.1-src-1panoplyx'
make: *** [all-recursive-am] Error 2
ERROR! Compiling source code has failed.
This usually happens because of missing libraries, or
badly written Makefiles or configure scripts.
No Requires information found in pdv.spec.

src2pkg FAILURE in compile_source

Since it's your source, I figured your the best person to ask about this. I see that the complaint is about "util.o". I don't know if this is supposed to be part of the libxml2 or not. I also found something about "xar" in Google. I must be missing a dependency, I just don't know what it is.

Shhingoshi
__________________

I'm quite certain that these errors are due to the version of gcc which you are using (4.3.3?). If you have not already done so, I'd strongly suggest you build yourself a second compiler of an older version. You are going to find that there are many, many programs and libraries which will not compile using gcc-4.x.x -especially when compiling for 64bit systems.

I did not write the PDV program. The version I host on my site is a slightly-modified version. But I have not updated the code to use gcc-4. There are several common errors that come out when using later versions of compiler for code that was written for earlier versions. I managed to learn 'by heart' a couple of changes that were needed for programs which were written for gcc-2.95 or 3.2 in order to compile with gcc-3.4. I have only begun to learn some of the tricks dealing with gcc-4.x problems.
Since you are 'keen' on using gcc-4 you may find it handy to know a few tricks yourself. You could help us both out by asking about this error on the LQ programming forum or elsewhere. then we'd both have a new trick up our sleeves.
I personally keep and use all these gcc version on my machine: 2.95.3, 3.1, 3.2.3, 3.3.6, 3.4.6 and gcc-4.x.x (from slackware-12). I also have i386-linux-uClibc and i586-mingw32 compilers for special jobs(it's exicting to compile stuff on my linux box which will run on windows!).

for your purposes I'd suggest you try having gcc-3.4.6(or 3.2.3) around for those times when something won't compile with gcc4.
You can find my build materials for 3.4.6 here:
http://distro.ibiblio.org/pub/linux/...vel/gcc-3.4.6/
using the above build makes it pretty easy to have a dual-compiler system without a lot of hassles.

this is a very poorley wriiten program and throw it away good luck. it may have compiled on the programers system but that was for his system and not global ok . so it is asking to meet dependecies but in his program it doesnt tell the average guy how and what version of what library to use in order to meet the deppendecies good luck.

your right gnashley the 4.12 bug is somthing else lol. i have kept my 3.4 and 3.2 gcc stuff.

pdv has no dependencies other than glibc. It's a very old program, but I found it to have some good ideas and very usable code for what it is supposed to do. I have used it to build self-extracting archives. I've thought of actually incorporating tar and minbunzip into the executable stub created by the program. But, using shar archives really makes more sense because it avoids compatibility issues (since what I was thinking of distributing are source code archives.

Still, the pdv installers can be setup as a sort of click-to-compile and run archive. I have experimented with packaging AppDirs this way -just run the execute the odv file, it unpacks and compiles the sources and runs the program when finished. Knida cool to see in action.

As for gcc-4 I pretty much despise it since it won't work with all the old sources that I love.