Yaakov (Cygwin Ports) wrote on 13 October 2008 04:52:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Dave Korn wrote:
>> Yep, you've got it. The problem is that OBJDUMP is not set to
>> anything, and so the regexes all fail pretty hard. And the reason that
>> OBJDUMP is not set to anything is due to this very common idiom in GNU
>> projects that exercise recursive makes:
>
> Actually, I hate to burst your bubble, but I think that this is not the
> reason. Remember that I fixed the missing OBJDUMP defines, and Chuck
> included those patches in 2.2.2-2 and pushed them upstream.
Uh, no, not sure what you're referring to; got a reference? Hmm, I see an
"OBJDUMP=objdump" definition near the top of usr/bin/libtool. I /thought/ I'd
been using uptodate libtool to build gcc packages (I do that on my home PC and
I'm at work now so can't check), but I guess I can infer that I must not have
been after all; I'm absolutely certain the only problem I had was no
definition of objdump (the symptoms are immediately distinguishable when you
see the output running under "bash -x".)
Another thought occurs: does that work for cross-compilation?
> "/usr/lib /lib/w32api /lib /usr/local/lib". However, since
> AM_GNU_GETTEXT (or AM_ICONV) is invariably called *after*
> AC_PROG_LIBTOOL/LT_INIT, the correct value is clobbered, and suddenly
> libtool can't find a library that the linker can.
This would only apply to w32api files, yes?
> Thoughts?
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?
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.)
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
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/
