Re: DLL hell...

G'Day Tor,
	You said bleeding edge, and I think I'm hemoraging :-)
I upgraded to libtool4b, and that seemed to help.

prehaps we could get on the same page, and you could return the
results from:

libtoolize --version
automake --version
autoconf --version
make --version
gcc --version
dlltool --version

and if you feel like it, perhaps the results of:
tar cvfz stuff.tgz configure.in Makefile.am acinclude.m4 acconfig.h
*/Makefile.am */*/Makefile.am

:-)

And just one question this time, where does depmod come from?
I copied mine from automake to the current dir ...

thanks,

Cameron

Tor Lillqvist wrote:
> 
> Cameron Gregory writes:
>  > I didn't really understand:
>  > You most probably will want to use a bleeding efge libtool, and thus
>  > have to remove the old libtool cruft from acinclude.m4, remove the old
>  > ltmain.sh, config.sub and config.guess files, and rerun libtoolize. Or
>  > something like that.
> 
>  > I don't know what libtool generates in acinclude.m4, and when I deleted
>  > those files, I didn't know how to get them back.
> 
> aclocal and libtoolize. I think. It's quite hard to remember and
> understand how the aclocal, libtoolize, automake, autoconf phases
> interact...
> 
> --tml
> 
> 
> To Post a message, send it to:   [email protected]
> To Unsubscribe, send a blank message to: [email protected]
> 
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

-- 
Please include previous messages in reply so I can follow the thread.

---------------------------------------------------------------------
Cameron Gregory
http://www.flamingtext.com/
[email protected]