Richard Merryweather wrote: > Using midgard 1.4.2 as available on the website, upgrading my dev > server. > > Partially through running ./mkall I get the message: > > /usr/bin/ld: cannot find -lmidgard > collect2: ld returned 1 exit status
In config.mv, after LIBS="$LIBS "`$MIDGARDCONFIG --libs` add LFLAGS="$LFLAGS -Pmgd -olex.yy.c" This has been fixed in CVS, but this should get you going. > I'm not sure where to go from here. If I midgard-config --report > > /usr/local/midgard/bin/midgard-config --report > version : 1.4.2 > sitegroups : 1 > prefix : /usr/local/midgard > host : i686-pc-linux-gnu > exec-prefix: /usr/local/midgard > cppflags : -I/usr/include/glib-1.2 -I/usr/lib/glib/include - > I/usr/include/mysql -I/usr/local/include -I/usr/local/midgard/include > libs : -L/usr/local/midgard/lib -lmysqlclient -L/usr/local/lib - > lexpat -lm -lz -lcrypt -lglib -lmidgard > > Does this all seem right? I had to edit midgard-config to stop it > adding the wrong path onto header files that already specified it > correctly (to get mod_midgard to compile), but changing it back to > previous just in case it still breaks. You mean -I/usr/local/midgard/include instead of -I/usr/local/midgard/include/midgard? That too has been addressed. Editing it out of midgard-config is sufficient unless you reinstall midgard-lib. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
