Re: GCC3.4

From: Jason Lixfeld (jason+lists.freebsd_at_lixfeld.ca)
Date: 04/30/04

  • Next message: Sebastien Raveau: "[ti(4)] firmware source"
    Date: Fri, 30 Apr 2004 10:13:56 -0400
    To: "J.D. Bronson" <jbronson@wixb.com>
    
    

    On Apr 30, 2004, at 9:55 AM, J.D. Bronson wrote:

    > At 08:50 AM 04/30/2004, you wrote:
    >> On Apr 30, 2004, at 3:09 AM, Kris Kennaway wrote:
    >>
    >>> On Fri, Apr 30, 2004 at 02:15:22AM -0400, Jason Lixfeld wrote:
    >>>> I've just installed gcc3.4 to, among other things take advantange of
    >>>> the -march=opteron options. I'm in quite a bit of a conundrum here
    >>>> because I've installed, changed the order in $PATH to look in
    >>>> /usr/local/bin before /usr/bin for gcc, cc etc but when I run a make
    >>>> buildworld it fails saying it doen't recognize the -march=opterion
    >>>> option. This means that the old system version of gcc is still
    >>>> being
    >>>> referenced somehow, even though I've set the paths:
    >>>
    >>> This is intentional (the system compiler is rebuilt as part of the
    >>> buildworld process, and thereafter used explicitly).
    >>>
    >>> You can't compile world with a compiler that is not the system
    >>> compiler, because it would fail with errors. If you must have a
    >>> world
    >>> compiled with gcc 3.x, you'll have to use the FreeBSD 5.x branch,
    >>> which uses gcc 3.x as the system compiler.
    >>
    >> This is a 5.2.1 system but it uses 3.3.3, not 3.4. so I guess I'll
    >> have to wait then until 3.4 is the system compiler.
    >>
    >>> Kris
    >
    > One thing I do on 5.2.1 is compile gcc 3.4 but use
    > --program-suffix=3

    I removed the program suffix all together. I was using the default one
    and making symlinks to gcc in /usr/local/bin because everything uses
    gcc to compile anyway. I'm going to go on the assumption that based on
    Kris' response, the programs that need to use the system gcc will be
    smart enough to hard code the path.

    How do you do tell things to use gcc3 instead of gcc? export a
    variable before make which tells make which compiler to use?

    > This way, I have gcc for the kernal, but gcc3 for access to gcc3.4
    > without
    > clobbering the freebsd version...

    My big problem is that I need to remember to comment out the options in
    make.conf if I'm going to be doing something that needs the system
    compiler.

    > -JDB

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: Sebastien Raveau: "[ti(4)] firmware source"

    Relevant Pages

    • Re: Whats the story with the "end of XP"?
      ... Support gives them access to the larger body ... The same compiler suite may be "best" in both ... In the case of ByteCraft compilers, you are truly expert in your field, you work closely and rapidly with customers if there are any issues, and you have top class testing and quality control. ... understanding the inner workings of a relatively simple compiler like GCC ...
      (comp.arch.embedded)
    • [RFC][PATCH-2.6] Clean up and merge compiler-*.h
      ... the kernel headers in include/linux to include/linux-abi. ... * Common definitions for all gcc versions go here. ... -/* Some compiler specific definitions are overwritten here ...
      (Linux-Kernel)
    • Re: LPC900/80C51 Compiler Toolchain
      ... >> supported by GCC, and so they invest. ... > if they already have their in-house compiler. ... one of the main companies in the Symbian consortium ... vendor to provide a good compiler for Atmel AVRs and eventually became ...
      (comp.arch.embedded)
    • Newbie packages question
      ... checking for gcc... ... checking for C compiler default output file name... ... checking if the linker is GNU ld... ... checking how to recognise dependent libraries... ...
      (Debian-User)
    • Lib X11 compile problem /Xlib.h:3573: error: syntax error before "_X_SENTINEL"
      ... checking for gcc... ... checking for C compiler default output file name... ... checking how to recognise dependent libraries... ...
      (comp.os.linux.x)