Re: 2.2_r6 jigdo files cdimage.d.o
On Wed, 10 Apr 2002, Richard Atterer wrote:
> On Tue, Apr 09, 2002 at 01:05:38PM +0200, Mattias Wadenstein wrote:
> [compiling jigdo-file]
>
> > It then procedes to fail to find db_create in -ldb[lots of versions]
> > despite that being installed. --without-libdb gives a failure later on at:
> > checking whether dgettext works... no
> > * Make sure gettext is installed, or use
> > * --disable-nls to switch off gettext support.
> > configure: error: dgettext() call could not be linked.
> [snip]
> > With g++ (and a bunch of hacking), it compiles but fails to link.
>
> It seems you have a linker problem both with the native compiler and
> g++. The libdb and gettext tests all call the linker. Once that is
> resolved, ./configure --without-gui (maybe also --disable-nls) should
> work.
Well, --disable-nls is one of the things I labeled as "a bunch of
hacking", actually it wasn't all that much of hacking. :)
This is where it ends up:
g++ -o jigdo-file cachefile.o compat.o configfile.o glibc-getopt.o
glibc-getopt1.o glibc-md5.o jigdo-file.o jigdo-file-cmd.o jigdoconfig.o
md5sum.o mkimage.o mktemplate.o recursedir.o rsyncsum.o scan.o string.o
zstream.o debug.o -ldb -lz -L/usr/local/lib
ld: 0711-317 ERROR: Undefined symbol: Base64Out<Base64StringOut>::code
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
information.
collect2: ld returned 8 exit status
gmake[1]: *** [jigdo-file] Error 1
gmake[1]: Leaving directory `/import/src/jigdo/jigdo-0.6.4/src'
gmake: *** [all] Error 2
> > I haven't had time to take a better look at it yet, or turn the
> > software over to someone else around here. It is still painful,
> > especially compared to jigdo-port which compiled cleanly and without
> > problems.
>
> I'm very interested in getting it to compile cleanly on your machine.
> I guess it's not possible for me to get an account on your uni's
> machine so I can fix it myself?
Sorry, Rules from higher up. Outsiders not allowed.
Do you have a good documentation for the change in file format, so that I
could perhaps hack jigdo-port into working again? I have much more clue
when it comes to C than C++ (which might not be saying all that much
though), and if it is just a couple of small changes...
/Mattias Wadenstein
--
To UNSUBSCRIBE, email to debian-cd-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: