Re: iconv.dll should be libiconv.dll??

G'Day,
	I tried this for both your old version, and this new one.
But it doesn't work.  I get link time errors.

Instead I tried:
$ mv iconv.lib iconv.dll.a
$ mv iconv.dll libiconv.dll

and I get..
c:\mingw\bin\..\lib\gcc-lib\mingw32\2.95.3-5\..\..\..\..\mingw32\bin\ld.exe:
war
ning: cannot find entry symbol _DllMainCRTStartup@12; defaulting to
00401000
c:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-5/../../../libmingw32.a(main.o)(.text
+0x8d):main.c: undefined reference to `WinMain@16'
make: *** [libgimp.la] Error 1

So renameing the dll, doesn't really make sense .. so
$ mv libiconv.dll iconv.dll ; make clean ; amke

and I get.... (and most other combinations I can think of (libiconv.a
and iconv.a...)

*** Warning: linker path does not have real file for library -liconv.
*** I have the capability to make that library automatically link in
when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libiconv and none of the candidates passed a file format test
*** using a file magic. Last file checked: localcharset.dll
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.

*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.

I had one other combo that gave be bad link errors, but I can't
seem to get that back now.

arrghh :-) (mind you I am back to libtool 1.4.2 .. maybe I should go
back
to 1.4d and see what happens .. I need faster computer :-) )

Cameron


Tor Lillqvist wrote:
> 
> Cameron Gregory writes:
>  > > there is (was) a libiconv.a, wasn't there? That is enough. The
>  > > .dll. part of the libfoo.dll.a name is just libtool's convention. (And
>  >
>  > umm .. no, not in your old one, or the new one.
>  > (libiconv-1.7-w32.bin.zip)
> 
> In that case just rename iconv.lib to libiconv.a, that works
> fine. Umm, now I remember, this is probably also the cause for the
> warning message you got from libtool: Libtool doesn't know about
> foo.lib style libraries, it only looks for libfoo.a, I think. Or maybe
> also libfoo.dll.a. Confusing? Sure.
> 
> --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]