This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: auto-sync of top-level 'include' & 'config' directories?


On Sun, Nov 04, 2001 at 06:49:26PM -0800, Zack Weinberg wrote:
> On Mon, Nov 05, 2001 at 12:28:40PM +1300, Bryce McKinlay wrote:
> > 
> > >Unless someone knows a good reason to avoid use of system iconv on
> > >some platforms, I would have it default to using system iconv
> > >(possibly in libc), and not distinguishing between system-provided
> > >libiconv and user-installed libiconv.
> > >
> > On some systems (eg Solaris), the system iconv is buggy, so it would be 
> > nice to be able to override the system implementation with the in-tree 
> > libiconv in those cases. We already have a bunch of workarounds in GCJ 
> > and libjava to deal with the Solaris iconv.
> 
> Do you happen to know if buggy system-provided iconv()s are common or
> rare?  If they're just about all buggy, it would make sense to act
> like libintl does now and use the bundled version except with GNU
> libc.  If they're mostly okay, we just need to blacklist Solaris.

I recommend you look at Mutt's configure script; a substantial portion
of the traffic on mutt-dev is about broken iconv libraries and code to
detect them.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]