ports/160312: Can't compile devel/glib20 with gcc 4.6

[b. f.]

The following reply was made to PR ports/160312; it has been noted by GNATS.

From: "b. f." <bf1783 at googlemail.com>
To: Pavel Timofeev <timp87 at gmail.com>
Cc: bug-followup at freebsd.org
Subject: Re: ports/160312: Can't compile devel/glib20 with gcc 4.6
Date: Wed, 31 Aug 2011 07:11:45 +0000

 On 8/31/11, Pavel Timofeev <timp87 at gmail.com> wrote:
 > Sorry, in the future I'll search info in maillists in the first place.
 > PR need to close.
 
 That would help, although sometimes the answers are a bit hard to
 find.  Sorry that you tripped over this, it's one of the outstanding
 problems with using alternative compilers and toolchains in ports.
 Maybe you should send a note to the author of:
 
 http://www.freebsd.org/doc/en_US.ISO8859-1/articles/custom-gcc/index.html
 
 and ask him to mention this and other build tools that cache compiler
 information, and so may cause build failures.
 
 b.
 
 >
 > 2011/8/31 b. f. <bf1783 at googlemail.com>
 >
 >> > /usr/bin/ld: unrecognized option '-Bsymbolic-functions'
 >> > /usr/bin/ld: use the --help option for usage information
 >> > gmake[4]: *** [libglib-2.0.la] Error 1
 >> > gmake[4]: Leaving directory
 >> `/usr/ports/devel/glib20/work/glib-2.28.8/glib'
 >> > gmake[3]: *** [all-recursive] Error 1
 >> > gmake[3]: Leaving directory
 >> `/usr/ports/devel/glib20/work/glib-2.28.8/glib'
 >> > gmake[2]: *** [all] Error 2
 >> > gmake[2]: Leaving directory
 >> `/usr/ports/devel/glib20/work/glib-2.28.8/glib'
 >> > gmake[1]: *** [all-recursive] Error 1
 >> > gmake[1]: Leaving directory `/usr/ports/devel/glib20/work/glib-2.28.8'
 >> > gmake: *** [all] Error 2
 >> > *** Error code 1
 >> >
 >> > Stop in /usr/ports/devel/glib20.
 >> > *** Error code 1
 >>
 >> This is a known problem when using multiple compilers and toolchains
 >> together with devel/libtool, which caches and uses information about
 >> the compiler and toolchain that it was built with.  If you want to use
 >> an alternative compiler and toolchain to build a port that uses
 >> devel/libtool, you must rebuild devel/libtool with your alternative
 >> compiler and toolchain before building your port.  And you cannot
 >> simply set USE_GCC for your rebuild of devel/libtool, because that
 >> will introduce circular dependencies in your package database.  So you
 >> must set CC, CXX, CFLAGS, and LDFLAGS individually, as in
 >> ports/Mk/bsd.gcc.mk.  This has been discussed numerous times over the
 >> past few years on the lists and in the forums, and is the subject of
 >> some open PRs.
 >>
 >> b.
 >>
 >