[lcd4linux] Re: need help with autmake, libtool and

[Ronald Landheer-C. <bly...@us...>]

On Tue, Sep 30, 2003 at 07:45:40PM +0200, Michael Reinelt wrote:
> 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)
OK.

> >>>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?
Looks like a buggy Libtool..

> >>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?
I've browsed them with ViewCVS on SourceForge.

> >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:
note: if their versions and your versions are not the same, it might work for 
you but not for them, as the package will be re-bootstrapped. Generally, only
developers should re-bootstrap packages: end-users shouldn't touch the 
Makefile.am or configure.in files as the changes they make will have impacts
other than just their changes on the generated scripts if their versions 
differ from yours.

I'll subscribe to the list :)

rlc

-- 
I just need enough to tide me over until I need more.
		-- Bill Hoest