Re: Error compiling buildworld

On Sat, Mar 22, 2008 at 3:42 PM, Jeremy Chadwick <koitsu@xxxxxxxxxxx> wrote:
> My make.conf flags:
> CPUTYPE?=prescott
> CFLAGS= -O -pipe
> COPTFLAGS= -O -pipe
> CC=/usr/local/libexec/ccache/world-cc
> CXX=/usr/local/libexec/ccache/world-c++
> (I try with and without ccache).
I'm willing to bet that the compiler tinkering you've done is causing
said problem. It would indicate whatever compiler is being used
("world-cc") is acting as if it doesn't understand the compiler flag
specified. I can assure you that gcc does support this option.

It is the gcc of the system! How is possible that gcc from fbsd 7.0
doesn't understand a compiler flag from fbsd 7.0 sources? Excuse, but
I'm a bit newbie...

It would be useful to see see the buildworld output with CXXFLAGS,
COPTFLAGS, CC, and CXX disabled in your make.conf. I realise you said
"I get the same error without this stuf", but you should've sent *that*
buildworld output. :-)

Is the same output.

Also, you really should be using "?=" operators on those optimisation
flags, in case something else overrides them. Yes, I know what the
documentation in share/examples/etc/make.conf says, but I still
recommend doing what I said.

Hummm... while you, or anybody, could say me anything about this, I
try with the "?=" operator, but if without operators doesn't

Thank you Jeremy.

Have a nice day ;-)

Dijo Confucio:
"Exígete mucho a ti mismo y espera poco de los demás. Así te ahorrarás
freebsd-stable@xxxxxxxxxxx mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

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 ...
  • Re: 10.0-CUR r226986 && ports (general)
    ... configure:3232: checking for gcc ... Configured with: FreeBSD/amd64 system compiler ... configure:5483: checking how to associate runtime and link libraries ... configure: failed program was: ...
  • [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 ...
  • 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 ...
  • Re: [TESTING]: ClangBSD branch needs testing before the import to HEAD
    ... I hate gcc with the burning heat of a million suns. ... been a major liability towards FreeBSD releases in the past. ... While Clang is immature now, it will mature in the near future, ... Any bug analisys now shall start with exchange to verify which compiler ...