[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] GUB: fix cross/gcc for darwin-x86

From: Patrick McCarty
Subject: Re: [PATCH] GUB: fix cross/gcc for darwin-x86
Date: Mon, 2 Nov 2009 13:29:22 -0800
User-agent: Mutt/1.5.20 (2009-06-14)

On 2009-11-02, Jan Nieuwenhuizen wrote:
> Op donderdag 29-10-2009 om 02:21 uur [tijdzone -0700], schreef Patrick
> McCarty:
> > Hi,
> > 
> > With luck, I finally managed to compile darwin-x86::cross/gcc with the
> > attached patch.  See the commit summary for an explanation.
> > 
> > I could never find the source of the error, even after extensive shell
> > tracing.  :(
> Is this with a LIBRESTRICT=open:stat build, or with a build that
> still has traces of that (ie, bash or sed installed in 
> target/tools/root; libtool built with that bash, etc?)

It is with LIBRESTRICT=open, but I can reproduce it with open:stat

> I ask because one source of problems with open:stat restriction
> is mismatches in $SHELL/$(SHELL) usage/ detection by configure, 
> or in Makefiles.
> +-            $(SHELL) ./ ../../gcc/$${fix_dir} \
> ++            $(SHELL) -c true ../../gcc/$${fix_dir} \
> I'm not sure what does, exactly, but this is effectively
> undoing that -- possibly that's a bit crude?

Yes, it's crude.  I wasn't expecting you to apply this patch; I just
wanted to report that it fixes the compile for me, so this might shed
some light on the problem.

I've tried doing `sh -x ./', but that didn't reveal any

I suppose I'll try doing a `sh -x ./' with
freebsd-x86::cross/gcc, which uses gcc 4.3.2 too (and is succeeding).
Comparing the logs might provide some hints.

Are there any other ways to debug this issue besides shell tracing?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]