[SOLVED] RE: [ANNOUNCEMENT] NEW: libtool-2.2.2-2 / Updated: libltdl7-2.2.2-2

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dave Korn wrote:
>   Uh, no, not sure what you're referring to; got a reference?

http://cygwin.com/ml/cygwin/2008-04/msg00378.html

>   Another thought occurs: does that work for cross-compilation?

You can't use /usr/bin/libtool for cross-compilation (it is coded for
the i686-pc-cygwin toolchain), but the above OBJDUMP patch uses
AC_CHECK_TOOL, so it should be fine for configure-generated libtools.

>   This would only apply to w32api files, yes?

Yes, because lib/w32api is the only directory in the standard linker
path that isn't standard to other systems.

>   Well that certainly is a problem with lib-link.m4.  Perhaps libtool should
> mark sys_lib_search_path_spec read-only?  Or would that just cause a failure
> later down the line?

I would think the latter.  I'm testing the attached patch against 0.17.

>   Ok, now I've got one for you :-)  Got any idea why libtool isn't including
> the typeinfo from my shared libstdc++ when it generates the import library?
> (If you do have any insight into this area, we should probably start a
> separate thread.)

Not without a .cygport and patches, together with some more details. :-)


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEUEAREIAAYFAkj3CkcACgkQpiWmPGlmQSOXuwCcD0vQxqpPviG9hec9kIDqJA2f
IUQAl02HUn7oJj5LziVueql0kysd73w=
=lpJm
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0.17-GETTEXT_VERSION-minimum.patch
Type: text/x-patch
Size: 363 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20081016/df41c656/attachment.bin>
-------------- next part --------------
--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/