Michael Jinks wrote:
> > Then, rerun ldconfig (shouldn't be necessary, but does no harm) and rebuild
> > imlib from scratch. All should then be well.
>
> Nope. Still get the same errors.
This may have been premature. I double checked, and there were still two
libraries for which I hadn't found rpm's (Fnlib and libesd), so I put those back
into /usr/local/lib, re-ran ldconf, and re-ran imlib/configure. The config.h file
still looked the same, but the compile fell on its face -- I get a weird error
now:
gcc -DDJPEG_PROG=\"/usr/bin/djpeg\" -DCJPEG_PROG=\"/usr/bin/cjpeg\"
-DCONVERT_PATH=\"/usr/local/bin\" -DNETPBM_PATH=\"/usr/bin\"
-DSYSTEM_IMRC=\"/usr/local/etc/imrc\" -I. -I. -I.. -I./.. -I/usr/lib/glib/include
-I/usr/X11R6/include -I/usr/lib/glib/include -I/usr/X11R6/include -g -O2
-Wp,-MD,.deps/rend.p -c -fPIC -DPIC rend.c
gcc: vfork: Cannot allocate memory
make[2]: *** [rend.lo] Error 1
make[2]: Leaving directory `/home/michael/E/imlib/gdk_imlib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/michael/E/imlib'
make: *** [all-recursive-am] Error 2
This is new. What have I gone and done now?
My box had 64megs of RAM, and about 130M swap space, in case that's relevant to
the vfork message.
All of my libraries still pass muster with rpm -V;
Feel free to tell me to play with the little kids if this is getting exasperating
to anybody. I realize that I'm tossing user-level questions at a developers'
list.
-
To unsubscribe from this list send mail to: [EMAIL PROTECTED]
with the message contents: unsubscribe e-develop
