From: Tony G. <Ton...@Su...> - 2005-08-23 23:24:35
|
"Gerrit P. Haase" <ge...@fa...> writes: > Tony Graham wrote: > >> "Gerrit P. Haase" <ge...@fa...> writes: >> >>>Tony Graham wrote: >>> >>>>"Gerrit P. Haase" <ge...@fa...> writes: >> .... >> >>>>>I needed only two minor changes in Makefile.am to get a clean build >>>>>(and of course reconfigury with the Cygwin autotools). >>>> >>>>What changes? >>> >>>Cygwin / Windows does not alllow to link binaries if the references >>>to functions and other imports cannot be resolved. Therefore >>>libtool needs the flsg -no-undefined and all libraries used need to >>>be added to the link command. >> Please check the latest CVS version to see if it works for you. > > Looks good. I have compiled the 0.35 release with exactly this change, > works ok with the test .fo file. BTW, it is safe to add -no-undefined > unconditional, doesn't have an affect on platform that don't use it and > IIRC also Macs need it. I was following what Pango does, but from the description of -no-undefined, it appears that you are correct: ------------------------------------------------------------ `--no-undefined' `-z defs' Report unresolved symbol references from regular object files. This is done even if the linker is creating a non-symbolic shared library. The switch `--[no-]allow-shlib-undefined' controls the behaviour for reporting unresolved references found in shared libraries being linked in. ------------------------------------------------------------ I will change it soon. Regards, Tony. |