[LLVMdev] Just got bitten by accidentally using the wrong gcc

Joachim Durchholz jo at durchholz.org
Fri Mar 21 03:54:01 PDT 2008


Am Freitag, den 21.03.2008, 15:17 +0800 schrieb Dominic Hamon:
> Joachim Durchholz wrote:
> > Am Donnerstag, den 20.03.2008, 15:44 -0700 schrieb Tanya M. Lattner:
> >   
> >> Its not just a matter of checking major/minor versions. It also depends on 
> >> the target and in some cases the OS.
> >> http://llvm.org/docs/GettingStarted.html#brokengcc
> >>
> >> So for example, GCC 3.3.3 on Suse or GCC 3.4.0 on linux/x86 
> >> (32-bit) has issues. Is it easy to check these kinds of things?
> >>     
> >
> > uname identifies arch.
> >
> > /etc/lsb-release identifies Linux distribution; I'm not sure how to
> > identify Apple and Cygwin.
> >
> >   
> uname on Apple (at least in a Terminal) returns 'Darwin'.

Ah, right. It should be
  uname -m
  uname -p
  uname -i

uname without an option is the same as uname -s, which is the name of
the kernel ("Linux" for me).

BTW ./configure already gathers that information (indeed via these uname
calls).

Regards,
Jo




More information about the llvm-dev mailing list