On Wed, 2005-01-05 at 13:02 +0100, Ralf Wildenhues wrote: > Please don't reply above quotes -- thank you. > > * pete wrote on Tue, Jan 04, 2005 at 11:11:48PM CET: > > On Tue, 2005-01-04 at 20:00 +0100, Ralf Wildenhues wrote: > > > * pete stagman wrote on Tue, Jan 04, 2005 at 07:12:28PM CET: > > > > > > > > >From here I downloaded the package and extracted it. The ltmain.sh file > > > > contained: > *snip* > > > > So if I just do a > > > > ./configure > > > > make > > > > won't that create the same libtool and the same error? > > > > > > No. `make' should not cause automake nor autoconf nor libtoolite to be > > > called (unless you modified some source files, for example > > > configure.in). > > > > removed directories, untarred package, ran the script > > Still get the same error, I looked through the script to see if it > > changes any files, it renames a bunch and moves the directories, but it > > doesn't look like it edits the configure.in or anything. > > Please notify the package author about the broken setup. > > As a workaround, you can update ltmain.sh by running libtoolize with the > appropriate options for the package before starting the script (your > bugreport shows that the libtool m4 macros are updated by aclocal, so > you don't have to deal with that). > > Regards, > Ralf
Hi Ralf, Did that last night, libtoolize fixed the libtool problem. Thanks, appreciate the help. --Pete PS: off topic I know this isn't a libtool problem but maybe you can answer this. After the compile I tried to load the new module: #dmesg ledxmit_dev: Unknown symbol copy_to_user ledxmit_serial: Unknown symbol copy_from_user ledxmit_serial: Unknown symbol ledxmit_unregister_plugin ledxmit_serial: Unknown symbol ledxmit_register_plugin -- pete <[EMAIL PROTECTED]> _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool