Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Feb 2012 13:00:09 GMT
From:      Matthias Andree <mandree@FreeBSD.org>
To:        gnome@FreeBSD.org
Subject:   Re: ports/161494: devel/anjuta: gmake[3]: Entering directory `/usr/ports/devel/anjuta/work/anjuta-2.32.1.1/plugins/python-loader&#39;  CC     plugin.lo cc1: error: invalid option argument &#39; -OPT:Olimit=0&#39; gmake[3]: *** [plugin.lo] Error 1
Message-ID:  <201202261300.q1QD09oV027857@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/161494; it has been noted by GNATS.

From: Matthias Andree <mandree@FreeBSD.org>
To: bug-followup@FreeBSD.org, ohartman@zedat.fu-berlin.de
Cc:  
Subject: Re: ports/161494: devel/anjuta: gmake[3]: Entering directory `/usr/ports/devel/anjuta/work/anjuta-2.32.1.1/plugins/python-loader&#39;
   CC     plugin.lo cc1: error: invalid option argument &#39;-OPT:Olimit=0&#39;
 gmake[3]: *** [plugin.lo] Error 1
Date: Sun, 26 Feb 2012 13:51:37 +0100

 (Note I'm not a member of the gnome@ team.)
 
 While I can reproduce the build failure with clang (possibly related to
 the "not portable" warnings your're seeing), building anjuta with gcc
 works fine for me.
 
 Can you post the command lines and relevant configuration files (like
 make.conf) that you've used to attempt a build with GCC? Chances are you
 haven't thoroughly switched to GCC.  For me, using portmaster's -m
 option wouldn't work.
 
 Note that you can pass V=1 as make argument to get the full compiler
 command lines, rather than the short "CC" "CCLD" lines, to see what's
 actually happening.
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202261300.q1QD09oV027857>