From: Michael R. <re...@eu...> - 2003-09-30 17:45:49
|
Hi Ronald, I'm CCing this to the lcd4linux mailing list, to Martin Hejl (he has encountered some problems while cross-compiling for uClibc) and to Patrick Schemitz (he and me tried to build a shared library) >>I'm resending this mail because I didn't get any any response. i hope >>you didn't loose interest... anyway, a response would be helpful! Thanks >>in advance! > > Either I didn't get it, or it got drowned in my spam filter.. Oh... or probably mine... you never can tell with spam filters :-) >>>What exactly is the problem? Perhaps I can help.. >> >>lcd4linux is a quite small and straightforward project, its main purpose >>is to collect some data and display it on an LCD. It's just a simple >>(single) application, no libraries are built. >> >>Now a guy wants to extract the hardware- and display-specific stuff into >>a (shared) library, and create python bindings for it. >> >>lcd4linux uses autoconf and automake, which worked fine without >>libraries. Now I tried to integrate a library target into automake. The >>first try was a static library, which was quite easy, but for python >>bindings you need a shared library. >> >>I tried to figure out how shared library targets are handled by >>automake, and found this libtool stuff. My first try succeded, but other >>people were having massive problems from this point on (I had to remove >>the target again). >> >>one of the problems have been: >> >>/bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. >>-I/usr/X11R6/include -D_GNU_SOURCE -Wall -g -O2 -c display.c >>./libtool: line 1: s%^.*/%%: No such file or directory >>./libtool: line 1: -e: command not found Martin, this was the error you encountered, right? >>other people had problems with cross-compiling for uClibc... >> >>Maybe I did the whole autoconf/automake stuff wrong (I've no experience >>with it). > > Possibly, but I'd have to see what you did with your Makefile.am files, your > configure.{ac|in} file and what the errors were. As you wrote later, the files look ok to you, you did already get the package or the CVS version? >>If I want to provide a source package, has libtool to be installed at >>the client? autoconf/automake is not necessary, if you provide the final >>'configure' script... > > No: libtoolize generates a libtool script for your package, which you should > send along. If you make your package using `make dist', it will be packaged > for you. Yes, that's what I would expect. > Your Makefile.am file looks OK (if you re-enable Libtool). > Your configure.in file needs only one of AC_PROG_LIBTOOL and AM_PROG_LIBTOOL - > i.e. the AC_* version. It always worked for me. But I have all the automake/autoconf/libtool toolchain installed. > What versions of the autotools were you using? merlin:~ $ autoconf --version autoconf (GNU Autoconf) 2.57 merlin:~ $ automake --version automake (GNU automake) 1.4-p6 merlin:~ $ libtool --version ltmain.sh (GNU libtool) 1.5.0a (1.1220.2.25 2003/08/01 19:08:35) Debian: 49 $ merlin:~ $ libtoolize --version libtoolize (GNU libtool) 1.5.0a > What were the problems you > encountered? Martin, Patrick, could you please report your versions, too? And could you please try to re-enable the currently commented lines in Makefile.am and configure.in: Makefile.am: # deactivateing shared lib target for the moment until # libtool works cleanly... #lib_LTLIBRARIES = liblcd4linux.la [...] # deactivated # liblcd4linux_la_LDFLAGS = -version-info 9:11:9 # liblcd4linux_la_SOURCES = \ [...] configure.in: # Using `AC_PROG_RANLIB' is rendered # obsolete by `AC_PROG_LIBTOOL' :-( AC_PROG_RANLIB # Deactivating libtool for the moment until # we find a way this beast works cleanly... #AC_PROG_LIBTOOL #AM_PROG_LIBTOOL and the report any problems? Lets discuss this stuff on the mailing list! Thanks in advance to all of you! I really want to get this stuff usable. Another guy asked for perl bindings for lcd4linux today... bye, Michael -- netWorks Vox: +43 316 698260 Michael Reinelt Fax: +43 316 692343 Geisslergasse 4 GSM: +43 676 3079941 A-8045 Graz, Austria e-mail: re...@eu... |