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]

Re: Serious Solaris problem (effects egcs-1.2)



  In message <199904270657.XAA13606@adsl-206-170-148-33.dsl.snfc21.pacbell.net>
  > I've always found it confusing, and apparently so have some others,
  > that GCC doesn't search the user's path for as.  Well, actually, it
  > does on some platforms and not on others.
Not 100% correct.

First it searches internal paths.  If no assembler is found, then it checks
the user's path.

Some ports have defined specific directories for the compiler's internal search
paths, for example /usr/ccs/bin.

  > still seems to me that it would be simpler to search the path.  Then,
  > the autoconf checks would work as well as any autoconf check; they all
  > assume that the end-users's environment will be reasonably similar to
  > the configurer's environment.  
I think we both agree that we need more consistency.  The question is how to
get it.  Do we avoid doing a feature test on an assembler the compiler will not
find?  Or do we tell the compiler where to find the assembler we used for the
feature test?

I'd lean towards the first, but I see advantages and disadvantages for both.

jeff


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