Re: libiconv package must be recompiled

[Charles Wilson <cwilson at ece dot gatech dot edu>]

Sam Steingold wrote:

> The following message is a courtesy copy of an article
> that has been posted to gmane.os.cygwin as well.
>
> It appears that the current cygwin libiconv package still has problems
> described in the following messages:
> <http://article.gmane.org/gmane.lisp.clisp.general/6832>
> <http://article.gmane.org/gmane.lisp.clisp.general/6767>
> it also appears that all it takes to fix the problem is to
> recompile the libraries from the current sources.
>
> Charles, are you the maintainer of the cygwin package?
> If yes, could you please remake the package?
> If no, could you please ask the maintainer to do that?

Sorry for the delay in responding; gmane web access was down and I 
couldn't review the messages you reference above until today.

It seems odd that simply recompiling libiconv/libcharset will "fix" this 
problem (whatever it is).  Is there any explanation for WHY this "fixes" 
the problem (I'd hate to actually be *hiding* the problem, instead of 
fixing it -- which is fairly likely, if we don't know what's really 
going on...)

What's the problem?  A missing export?  The fact that I'd now be using a 
fancy new binutils (the existing libiconv package was built a year ago, 
and there have been a few binutils releases since then).

Or worse -- somehow we've tickled an incompatibility between DLLs built 
with "old" ld and apps built with "new" ld?

I'm sorry, but while I have no objection to rebuilding the package per 
se, I need more than "stir in this magic powder and it works!" before 
I'm entirely comfortable with this.

--Chuck



--
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/