More gcc80 adjustments.

Nothing spectacular.

Taken-from: zrj

Set gcc50 as the primary compiler, gcc47 as secondary

Per request, rather than define NO_GCC47 to prevent the building of the
secondary compiler, the new variable is called NO_ALTCOMPILER. This
wil

Set gcc50 as the primary compiler, gcc47 as secondary

Per request, rather than define NO_GCC47 to prevent the building of the
secondary compiler, the new variable is called NO_ALTCOMPILER. This
will avoid some disruption in the future where the actual version is not
important, only the desire to avoid the secondary compiler.

show more ...

customcc: Improve wrapper script efficiency and capabilities

The wrapper script had some deficies, such as:
* awk called every invocation
* cc and gcc treated the same
* c++ and g++ treated the s

customcc: Improve wrapper script efficiency and capabilities

The wrapper script had some deficies, such as:
* awk called every invocation
* cc and gcc treated the same
* c++ and g++ treated the same
* evals for variables not used
* every invocation of c++ or g++ called cc -dumpmachine
* g++ hardcoded to dports include scheme
* no support for "CC" or "gcov" (both defined by base compilers)

The update addresses these by:
* awk eliminated by pushing INCOPT definition to defaults/compilers.conf
* cc -dumpmachine eliminated during creation of defaults/compilers.conf
It was only used for dports gcc, so with the assumption that the dports
compiler matches the uname information (a decent assumption), this
was predefined, yet overridable by /etc/compilers.conf
* cc is treated separately from gcc
* CC and c++ are treated the same but separately from g++
* by wrapper default, gcc and g++ refer to base gcc4.7, but the default
compilers.conf sets them to the same as the specified dports gcc
* Support for clang, clang++, clang-cpp, CC, and gcov was added
* Support for base clang, clang++, and clang-cpp was added in
anticipation of bringing clang into base.
* variables are only evaluated if used.
* supports the ability to have gcc, g++, clang, clang++ point to base
compilers while cc, c++, CC point to custom compiler. However, the
custom compiler can also point to any combination of cc, gcc, c++, and
g++ and that's controllable by compilers.conf.

The /etc/defaults/compilers.conf file was augmented and support for
clang35 from dports added. man 5 compilers.conf was edited accordingly
with placeholders for <version>_CLANG, <version>_CLANGCXX and
<version>_CLANGCPP which aren't applicable until clang comes into base.

show more ...

Adjust the cc wrapper script and compilers.conf to dports.

Provide defaults for various GCCs for now.

customcc/compilers.conf: Some adjustments and simplifications.

* pkgsrc's clang no longer needs special handling for C++ compilation.

* Use gcc44's cpp, gcc41 is gone.

* -dumpversion is now unders

customcc/compilers.conf: Some adjustments and simplifications.

* pkgsrc's clang no longer needs special handling for C++ compilation.

* Use gcc44's cpp, gcc41 is gone.

* -dumpversion is now understool by both pkgsrc's and SVN trunk's
clang, so no special handling needed for that either.

Based on an older patch I did with Juan Francisco a year ago.

Reported-by: Juan Francisco Cantero Hurtado <iam@juanfra.info>
Joris Giovannangeli <joris@giovannangeli.fr>
Tested-by: Joris Giovannangeli <joris@giovannangeli.fr>
Dragonfly-bug: <http://bugs.dragonflybsd.org/issues/2205>

show more ...

Switch on gcc47 and switch off gcc41

Replace GCC 4.1 with GCC 4.7. The primary compiler remains GCC 4.4
and the source and makefiles for GCC 4.1 remain intact so it can be
brought back if necessary

Switch on gcc47 and switch off gcc41

Replace GCC 4.1 with GCC 4.7. The primary compiler remains GCC 4.4
and the source and makefiles for GCC 4.1 remain intact so it can be
brought back if necessary. All references to GCC 4.1 in documentation
where updated to reflect version 4.7.

A full world build is probably required after this point.

show more ...

customcc: Fix the setup of the /usr/include path to use.

With the recent O_DIRECTORY addition, this apparent bug in the script was
exposed. Using -isysroot/-isystem doesn't seem to cut it for what w

customcc: Fix the setup of the /usr/include path to use.

With the recent O_DIRECTORY addition, this apparent bug in the script was
exposed. Using -isysroot/-isystem doesn't seem to cut it for what we want
here (which is to completely override the /usr/include path).

I didn't verify in 100% detail, but all evidence looks like the reason is
that when -I is present on the command line, the paths of the headers
which are included by headers from this directory are not prefixed with
-isysroot's argument.

So for now, use -iprefix and -iwithbeforeprefix for /usr/include, which
seem to do what we want.

While here, add our copyright.

Reported-by: marino

show more ...

CCVER: Add /usr/pkgsrc/lang/gcc-aux as 'gcc47'

There are two gcc-4.7.x packages in pkgsrc that will build gcc 4.7-based
compilers on Dragonfly. One is located at lang/gcc47 and the other is
located

CCVER: Add /usr/pkgsrc/lang/gcc-aux as 'gcc47'

There are two gcc-4.7.x packages in pkgsrc that will build gcc 4.7-based
compilers on Dragonfly. One is located at lang/gcc47 and the other is
located at lang/gcc-aux. Both have been patched by myself, but gcc-aux
seems to work better, especially with regards to link-time optimization.

Consequently, a new valid value for CCVER has been created, "gcc47", which
references lang/gcc-aux while building world and kernel. Both will
compile, and the produced kernel will boot, but there are some network
issues. Consequently, CCVER=gcc47 should only be used by developers who
have the express intent to fix any issues the arise from compiling
DragonFly sources with the latest GCC compiler. Normal users looking
for non-base GCC compilers should stick with CCVER=gcc46 for now.

show more ...

custom cc script: Use gcc46's c++ library instead of base

There will be a slight performance hit with having to make two calls to
gnatc++ before every real call in order to use gnat-aux's c++ librar

custom cc script: Use gcc46's c++ library instead of base

There will be a slight performance hit with having to make two calls to
gnatc++ before every real call in order to use gnat-aux's c++ library
rather than the base systems gcc 4.4 c++ library. The alternative is
hardcoding these values as a function of arch which is less appealing.

show more ...

custom cc script: Fix "Unterminated quoted string" error

When updating gcc46 to handle c++ by default, the old quotation mark
was accidently left in place, causing a world build breakage at
include/

custom cc script: Fix "Unterminated quoted string" error

When updating gcc46 to handle c++ by default, the old quotation mark
was accidently left in place, causing a world build breakage at
include/rpc.

show more ...

custom cc script: add c++ support for gcc46 compiler

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.

clang: -nostdclanginc was renamed -nobuiltininc.

While here, clean up a bit.

libexec/customcc: Set up the include paths a bit better.

Only use /usr/include and /usr/libdata/gcc41 prefixed by
${USRDATA_PREFIX}. This requires r83302 of LLVM/clang or
higher for the -nostdclangi

libexec/customcc: Set up the include paths a bit better.

Only use /usr/include and /usr/libdata/gcc41 prefixed by
${USRDATA_PREFIX}. This requires r83302 of LLVM/clang or
higher for the -nostdclanginc option.

While here, remove an 'else' I put in for debugging purposes
which is now useless.

show more ...

Add a wrapper script to allow "foreign" compilers into our build system.

With this commit, all CCVER values not associated with a compiler in
base will be relegated to the wrapper script which then

Add a wrapper script to allow "foreign" compilers into our build system.

With this commit, all CCVER values not associated with a compiler in
base will be relegated to the wrapper script which then (in conjunction
with the compilers.conf file) determines which non-base compiler to
use.

So far, defaults for clang (built from SVN) and pkgsrc/wip/gcc44 are
provided.

For more info see the compilers.conf(5) manual page and my mail on
kernel@:

http://leaf.dragonflybsd.org/mailarchive/kernel/2009-06/msg00013.html

show more ...

Add 'gcc46' as a CCVER value (using /usr/pkgsrc/lang/gnat-aux).

So far I've tested building and running our kernel (which both works).

World hasn't been tested and would fail using default values,

Add 'gcc46' as a CCVER value (using /usr/pkgsrc/lang/gnat-aux).

So far I've tested building and running our kernel (which both works).

World hasn't been tested and would fail using default values, since
gnat-aux so far only supports C and Ada.

Many thanks to John Marino <john@marino.st> who did and maintains the
lang/gnat-aux package.

show more ...

More work on CCVER=clangsvn.

* Remove /usr/libdata/gcc41 from the include path. It is not needed.

* Use gcc 4.4's C++ headers instead of gcc 4.1's. This fixes building of
devd(8) and likely of ot

More work on CCVER=clangsvn.

* Remove /usr/libdata/gcc41 from the include path. It is not needed.

* Use gcc 4.4's C++ headers instead of gcc 4.1's. This fixes building of
devd(8) and likely of other C++ stuff too.

show more ...

Add support for $CCVER="clangsvn"

This is for clang/llvm installed from SVN trunk to /usr/local
(which is its default location).

Adjust the compiler wrapper script to use pkgsrc's clang for CCVER=clang.

* Move the definitions for the SVN version to 'clangsvn'.

* Expand the compilers.conf(5) manual page a bit and give more (b

Adjust the compiler wrapper script to use pkgsrc's clang for CCVER=clang.

* Move the definitions for the SVN version to 'clangsvn'.

* Expand the compilers.conf(5) manual page a bit and give more (better)
examples.

Thanks to Jim Chapman <cchapman8@cogeco.ca> for help with testing.

show more ...