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: Phil Edwards <phil at codesourcery dot com>
To: DJ Delorie <dj at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org, mark at codesourcery dot com
Date: Mon, 20 Oct 2003 17:50:40 -0400
Subject: Re: [PATCH] Add various VxWorks target configs (3/3)
References: <3F943823.3020504@codesourcery.com> <200310202023.h9KKNH031153@greed.delorie.com>

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.

Phil

--
LUKE:  Is Perl better than Python?
YODA:  No... no... no.  Quicker, easier, more seductive.
LUKE:  But how will I know why Python is better than Perl?
YODA:  You will know.  When your code you try to read six months from now.

Follow-Ups:
- Re: [PATCH] Add various VxWorks target configs (3/3)
  - From: Mark Mitchell

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]