Date: Tue, 28 Apr 2015 17:47:12 +0200 From: John Marino <freebsd.contact@marino.st> To: Tijl Coosemans <tijl@FreeBSD.org> Cc: John Marino <marino@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r384894 - head/lang/gcc5-aux Message-ID: <553FAB80.1040300@marino.st> In-Reply-To: <20150428173654.2baa2951@kalimero.tijl.coosemans.org> References: <201504281216.t3SCGYSp044760@svn.freebsd.org> <20150428165407.1bb95495@kalimero.tijl.coosemans.org> <553FA06F.8000602@marino.st> <20150428171258.4668b0ab@kalimero.tijl.coosemans.org> <553FA574.3010503@marino.st> <20150428173654.2baa2951@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/28/2015 17:36, Tijl Coosemans wrote: > On Tue, 28 Apr 2015 17:21:24 +0200 John Marino <freebsd.contact@marino.st> wrote: > Yes, the CPPFLAGS you left only affects the first configure script and > that script doesn't pass CPPFLAGS/LIBS to the Makefile it creates. That > Makefile then runs multiple other configure scripts during build phase. > The only way I found to pass CPPFLAGS/LIBS to these other configure > scripts was *_configargs. I believe you, but that sounds like the gcc build system is broken then. > >> From your answer, I infer it wasn't linking with libiconv before your >> commit? > > It was when libiconv happened to be installed, but with my commit > libiconv is always installed as a build dependency on FreeBSD 10 > (because the iconv.h header on FreeBSD 10 is broken). Maybe NLS is too much a pain to support. Is there a reason that the lang/gccX don't support it? I only threw it in because it seemed to work, but it is starting to be too much trouble, especially if it's not standard for ports compiler to support it. > Hmm, can you do a build with only 1 make job? I have a new commit brewing that changes a few things: 1. new bootstrap for DragonFly 2. new option to build all 3 stages (currently the standard) 3. new standard behavior to build only one stage, but without libcc1 being produce which is the reason this wasn't set yet. I was going to make new bootstraps for FreeBSD but now I don't think it's necessary. I'm testing the build on FreeBSD 10 and FreeBSD 8 right now. (10 just passed). I can try to build with one job after that but it seems to me the issue is putting -L argument in args instead of LDFLAGS. I thought LIBS was limited to libraries and wasn't supposed to carry flags but the whole LIBS thing has never been really clear to me either. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?553FAB80.1040300>