This is the mail archive of the gcc-patches@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]
Other format:	[Raw text]

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

From: Mark Mitchell <mark at codesourcery dot com>
To: DJ Delorie <dj at redhat dot com>
Cc: phil at codesourcery dot com, gcc-patches at gcc dot gnu dot org
Date: 20 Oct 2003 13:31:27 -0700
Subject: Re: [PATCH] Add various VxWorks target configs (3/3)
Organization: CodeSourcery, LLC
References: <3F943823.3020504@codesourcery.com> <200310202023.h9KKNH031153@greed.delorie.com>

On Mon, 2003-10-20 at 13:23, 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.

Phil --

I see that Wind River has historically shipped libiberty.a with its
toolchains.  So, that's another reason in favor of DJ's position.

I think you can check the patch in as is, but please see whether
libiberty builds, and, if so, reactive it ASAP.

Thanks,

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

References:
- [PATCH] Add various VxWorks target configs (3/3)
  - From: Phil Edwards
- Re: [PATCH] Add various VxWorks target configs (3/3)
  - From: DJ Delorie

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