On Fri, 2008-10-10 at 02:16 +0000, Kai-Martin Knaak wrote: > On Wed, 08 Oct 2008 13:51:37 +0100, Peter Clifton wrote: > > [GMP tests not failing] > > I wonder if you have a working Wine installation, which might be running > > the executables through binfmt-misc or whatever mechanism there is for > > running "alien" binaries. > > Yes, I have wine installed. > > > I'm not entirely surprised some tests failed. Perhaps you could skip the > > tests some how. > > I just removed the misc dir form the list of paths where tests are > searched. > > > [building guile] > >> How do I tell the Makefile not to build texi docs? > > > > I have no idea. It is possible that you have to hack the Makefile.am to > > remove those targets, or perhaps there is some configure option? > > Thanks for the hint. Removing the doc dir from the list of targets in > Makefile.am did the trick. With guile successfully compiled I gave gschem > a try. However, configure still complains about a bad interpreter: > > checking libguile compile flags... configure: /usr/i586-mingw32msvc/bin/ > guile-config: /usr/i586-mingw32msvc/bin/guile: bad interpreter: No such > file or directory > > Seems like the configure script is not as smart as the GMP test > procedures and tries to run guile rather than guile.exe > After I cheated with a symlink to /usr/bin/guile the configure script > seemed to run ok. However, make failed somewhere down the road with a > complaint about an unknown option -pthread :
Send me (private email), the config.log and generated Makefile from the toplevel, and I'll try to figure out where the problem is coming from. The errors in gschem_struct.h seem to suggest the GTK header hasn't been included yet. What version of gEDA are you building? My line-numbers, and header-file arrangement appears different to that of your build logs, possibly because I'm looking at git HEAD code. Is it possible that you're build is picking up the wrong libgeda header files? You need to ensure PKG_CONFIG_PATH is set to point where "make intsall" for your windows cross-build installed the libgeda.pc file. [snip] > What can I do to fix this one? > I tried the option --disable-threads in configure but make emitted "-pthread" > anyway. Maybe -pthread does not hurt, but something else is wrong with > gschem_struct.h -pthread is probably coming from some pkgconfig flags. Make sure you have PKG_CONFIG_PATH set so it also includes the .pc files from your cross-compiled GTK. Unfortunately, the problem you saw with guile might be the cause of -pthread. guile doesn't use "pkg-config", but its own thing. For example, on my box, I have: guile-config link -pthread -lguile -lltdl -Wl,-Bsymbolic-functions -lgmp -lcrypt -lm -lltdl Your cross-build will still be picking up the compile options for the guile installed on your system. As a kludgy, hacky workaround, you might like to run your built guile-config.exe under wine, with the "link" and "compile" options, then hack libgeda's configure.ac.in to change: GUILE_FLAGS to GUILE_CFLAGS="....." GUILE_LDFLAGS="....." And remove the rest of the block checking for guile. (A quick check shows this test in gattrib, gnetlist, gschem, gsymcheck, libgeda and utils). You'll need to edit the "configure.ac.in" where it exists, otherwise "configure.ac", and then re-run "./autogen.sh" in that directory afterwards. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
