This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: intermittent gcc bug with /usr/ccs/bin/as
- From: Edward Peschko <esp5 at pge dot com>
- To: Mike Stump <mrs at apple dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 9 Dec 2004 16:41:51 -0800
- Subject: Re: intermittent gcc bug with /usr/ccs/bin/as
- References: <20041209224724.GA27975@venus> <875610BD-4A3B-11D9-B6E2-003065BDF310@apple.com>
On Thu, Dec 09, 2004 at 03:39:11PM -0800, Mike Stump wrote:
> On Thursday, December 9, 2004, at 02:47 PM, Edward Peschko wrote:
> >I've got a very frustrating bug with gcc 3.4.3 on solaris 5.8 - I'm
> >hesitant even
> >to put it in the bug database because it is IS so intermittant
>
> I'll assume that you built the compiler correctly... if not,
> rebuild/reinstall...
>
> The compiler and binutils should have the same prefix, and the
> compiler, when built, should use the --with-gnu-as=bla option, or
> however it is spelled.
>
> The compiler usually isn't intermittent, so this would tend to indicate
> a problem in your automounter, your filesystem... try a local
> filesystem...
>
> Run a trace with strace/ktrace/trace and see what the system calls that
> try and open ../as do and what they return. If you put in a shell
> script into the same directory that has cc1 called as, and have it exec
> /bla/bla/as "$@", I thinking it should never escape back to
> /usr/ccs/bin.
ok... I figured out what it was (it was me being too smart for my own good).
A long convoluted story, but even though /usr/ccs and gcc were locally
available, the gnu 'as' was not available for small periods of time,
and it looks like gcc runs back to /usr/ccs/bin/as by default.
Although, one could argue that - if you compile with --with-gnu-as=...
you should get a *fatal error* if that gnu as is not available, not
an attempt to use sun's version...
Ed