Re: [PATCH] Add various VxWorks target configs (3/3)

[Mark Mitchell <mark at codesourcery dot com>]

On Mon, 2003-10-20 at 14:50, Phil Edwards wrote:
> DJ Delorie wrote:
> >>This is the toplevel configury patch.  VxWorks doesn't need or use
> >>libiberty.
> > 
> > Very few targets need or use libiberty.  It's provided for the end
> > user.  Can vxworks build a usable libiberty?  If so, then it should
> > build it.
> 
> No, it couldn't build libiberty at the time (the main reason I disabled it),
> and I'm afraid I no longer have the error messages around.  I will try again
> with updated 3.4 sources.

Failure to build libiberty would be a good reason to disable it,
indeed...

The VxWorks version of libiberty is of course hacked up relative to the
FSF libiberty, principally with better support for non-Cygwin Windows
operation, if I recall correctly.  (I vaguely remember Zack and DJ
disagreeing about something, and us therefore having local patches.) 
So, it might be that the FSF libiberty builds OK, even though our
VxWorks version does not.

-- 
Mark Mitchell <mark@codesourcery.com>
CodeSourcery, LLC