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]
Other format:	[Raw text]

Re: Bug in gcc.c for_each_path() (leads to invalid crt0.o selection)?

From: Joseph Myers <joseph at codesourcery dot com>
To: Sebastian Huber <sebastian dot huber at embedded-brains dot de>
Cc: GCC <gcc at gcc dot gnu dot org>, RTEMS <devel at rtems dot org>
Date: Tue, 6 Dec 2016 17:09:28 +0000
Subject: Re: Bug in gcc.c for_each_path() (leads to invalid crt0.o selection)?
Authentication-results: sourceware.org; auth=none
References: <58452D10.3030005@embedded-brains.de> <alpine.DEB.2.20.1612052140260.15680@digraph.polyomino.org.uk> <58468BCC.3010003@embedded-brains.de>

On Tue, 6 Dec 2016, Sebastian Huber wrote:

> thanks for the detailed explanation. I guess, then the root cause for my
> problem is that the Newlib provided crt0.o files in the build tree are not in
> the same relative location of the installation tree. In the build tree, they
> reside in a "newlib" subdirectory. I changed the Newlib build flags set by GCC
> to use -L instead of -B and this seems to work (comment is wrong now). Does it
> make sense to submit such a patch or has it maybe some nasty side-effects?

I don't know what the effects of such a change might be.

-- 
Joseph S. Myers
joseph@codesourcery.com

Follow-Ups:
- Re: Bug in gcc.c for_each_path() (leads to invalid crt0.o selection)?
  - From: Sebastian Huber

References:
- Bug in gcc.c for_each_path() (leads to invalid crt0.o selection)?
  - From: Sebastian Huber
- Re: Bug in gcc.c for_each_path() (leads to invalid crt0.o selection)?
  - From: Joseph Myers
- Re: Bug in gcc.c for_each_path() (leads to invalid crt0.o selection)?
  - From: Sebastian Huber

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