Re: Ports with hardcoded "gcc", "g++"

Updated list, 2017-03-08: lang/jruby lang/nim x11/p5-Wx -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: Ports with hardcoded "gcc", "g++"

Updated list, 2017-03-05: devel/boost java/jna lang/jruby lang/nim net/pidgin x11/p5-Wx -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: Ports with hardcoded "gcc", "g++"

Updated list, 2017-03-04: devel/boost devel/jdk/1.7 emulators/virtualjaguar graphics/ipe lang/nim misc/rocrail net/pidgin productivity/wyrd x11/p5-Wx -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: Ports with hardcoded "gcc", "g++"

On Thu, Mar 02, 2017 at 01:11:05PM +, Christian Weisgerber wrote: > Updated list: > > archivers/hs-zlib Matthias Kilian > databases/hs-postgresql-libpq David Schaefer > devel/boost Brad Smith > devel/cil

Re: Ports with hardcoded "gcc", "g++"

Solène Rapenne writes: > Le 2017-02-26 16:00, Christian Weisgerber a écrit : >> Here is a first batch of ports that fail to build without "gcc" or >> "g++" being present. More will come to light eventually. At the >> moment, failing dependencies prevent about a third of the

Re: ghc.port.mk (was: Ports with hardcoded "gcc", "g++")

On Thu, Mar 02, 2017 at 10:03:29PM +0100, Karel Gardas wrote: > On Thu, Mar 2, 2017 at 9:23 PM, Matthias Kilian > wrote: > > Also, I've no idea wether --with-clang=${CC} will work after the > > switch to clang. On the other hand, the diff is just a workaround, > > >

Re: ghc.port.mk (was: Ports with hardcoded "gcc", "g++")

On Thu, Mar 2, 2017 at 11:35 PM, Matthias Kilian wrote: > On Thu, Mar 02, 2017 at 09:23:25PM +0100, Matthias Kilian wrote: >> Running an update bulk build with the diff below now for ghc-7.10.3, >> to see wether it helps... however, all the hs-ports in my tree are still >>

Re: Ports with hardcoded "gcc", "g++"

On Thu, Mar 02, 2017 at 08:44:39PM +0100, Christian Weisgerber wrote: > Juan Francisco Cantero Hurtado: > > > > ===> Building for nim-0.16.0p0 > > > cd /usr/obj/nim-0.16.0/nim-0.16.0 && /usr/bin/env -i CC="gcc" > > > LINKER="gcc" CFLA > > > GS="-O2 -pipe " sh build.sh > > > gcc -O2 -pipe -w

Re: ghc.port.mk (was: Ports with hardcoded "gcc", "g++")

On Thu, Mar 02, 2017 at 09:23:25PM +0100, Matthias Kilian wrote: > Running an update bulk build with the diff below now for ghc-7.10.3, > to see wether it helps... however, all the hs-ports in my tree are still > updated for ghc-8.0.1, so I've no idea wether I'll see anything useful. > > Also,

Re: ghc.port.mk (was: Ports with hardcoded "gcc", "g++")

On 2017/03/02 22:03, Karel Gardas wrote: > On Thu, Mar 2, 2017 at 9:23 PM, Matthias Kilian > wrote: > > Also, I've no idea wether --with-clang=${CC} will work after the > > switch to clang. On the other hand, the diff is just a workaround, > > > +MODGHC_SETUP_CONF_ARGS

Re: ghc.port.mk (was: Ports with hardcoded "gcc", "g++")

On Thu, Mar 2, 2017 at 9:23 PM, Matthias Kilian wrote: > Also, I've no idea wether --with-clang=${CC} will work after the > switch to clang. On the other hand, the diff is just a workaround, > +MODGHC_SETUP_CONF_ARGS += --with-gcc=${CC} --with-clang=${CC} Hi Kili,

ghc.port.mk (was: Ports with hardcoded "gcc", "g++")

Hi, On Thu, Mar 02, 2017 at 01:11:05PM +, Christian Weisgerber wrote: > Updated list: > > archivers/hs-zlib Matthias Kilian > databases/hs-postgresql-libpq David Schaefer [...] Running an update bulk build with the diff below now for ghc-7.10.3, to

Re: Ports with hardcoded "gcc", "g++"

Juan Francisco Cantero Hurtado: > > ===> Building for nim-0.16.0p0 > > cd /usr/obj/nim-0.16.0/nim-0.16.0 && /usr/bin/env -i CC="gcc" LINKER="gcc" > > CFLA > > GS="-O2 -pipe " sh build.sh > > gcc -O2 -pipe -w -fno-strict-aliasing -Ic_code -c c_code/3_2/compiler_nim.c > > -o c > >

Re: Ports with hardcoded "gcc", "g++"

On Thu, Mar 02, 2017 at 04:33:40PM +0100, Christian Weisgerber wrote: > Juan Francisco Cantero Hurtado: > > > > I changed the variable to NIM_CC. OK? > > > > And now with "elif" -> "else" fixed. > > There is still confusion about CC and NIM_CC: > > ===> Building for nim-0.16.0p0 > cd

Re: Ports with hardcoded "gcc", "g++"

Le 2017-02-26 16:00, Christian Weisgerber a écrit : Here is a first batch of ports that fail to build without "gcc" or "g++" being present. More will come to light eventually. At the moment, failing dependencies prevent about a third of the ports tree from being built. devel/premake4 hello

Re: Ports with hardcoded "gcc", "g++"

Juan Francisco Cantero Hurtado: > > I changed the variable to NIM_CC. OK? > > And now with "elif" -> "else" fixed. There is still confusion about CC and NIM_CC: ===> Building for nim-0.16.0p0 cd /usr/obj/nim-0.16.0/nim-0.16.0 && /usr/bin/env -i CC="gcc" LINKER="gcc" CFLA GS="-O2 -pipe " sh

Re: Ports with hardcoded "gcc", "g++"

Updated list: archivers/hs-zlib Matthias Kilian databases/hs-postgresql-libpq David Schaefer devel/boost Brad Smith devel/cil The OpenBSD ports mailing-list devel/hs-bytestring-mmap

Re: Ports with hardcoded "gcc", "g++"

On Thu, Mar 02, 2017 at 12:46:58AM +0100, Juan Francisco Cantero Hurtado wrote: > On Wed, Mar 01, 2017 at 11:36:52PM +0100, Juan Francisco Cantero Hurtado > wrote: > > On Wed, Mar 01, 2017 at 11:09:03PM +0100, Christian Weisgerber wrote: > > > Juan Francisco Cantero Hurtado: > > > > > > > They

Re: Ports with hardcoded "gcc", "g++"

On Wed, Mar 01, 2017 at 11:36:52PM +0100, Juan Francisco Cantero Hurtado wrote: > On Wed, Mar 01, 2017 at 11:09:03PM +0100, Christian Weisgerber wrote: > > Juan Francisco Cantero Hurtado: > > > > > They have a simple option to change the compilers but we need a variable > > > with the realname of

Re: Ports with hardcoded "gcc", "g++"

On Wed, Mar 01, 2017 at 11:09:03PM +0100, Christian Weisgerber wrote: > Juan Francisco Cantero Hurtado: > > > They have a simple option to change the compilers but we need a variable > > with the realname of the compiler, i.e. clang or gcc. > > > > You can use "nim c -cc:clang" or "nim c

Re: Ports with hardcoded "gcc", "g++"

On Wed, Mar 01, 2017 at 08:41:17PM +, Stuart Henderson wrote: > On 2017/03/01 21:15, Juan Francisco Cantero Hurtado wrote: > > On Wed, Mar 01, 2017 at 05:45:32PM +, Stuart Henderson wrote: > > > On 2017/03/01 17:10, Juan Francisco Cantero Hurtado wrote: > > > > On Tue, Feb 28, 2017 at

Re: Ports with hardcoded "gcc", "g++"

Juan Francisco Cantero Hurtado: > They have a simple option to change the compilers but we need a variable > with the realname of the compiler, i.e. clang or gcc. > > You can use "nim c -cc:clang" or "nim c -cc:gcc" (the default) or "nim c > -cc:egcc". All of them are the name of the profile,

Re: Ports with hardcoded "gcc", "g++"

On Wed, Mar 1, 2017, at 17:47, Amit Kulkarni wrote: > I meant to say the .a file is missing for libQtWebkit > > Thanks > Found the cause and fixed it. Attached patch makes it build correctly without g++/gcc. Thanks again Stuart and Amit for the hints. Frank Index: Makefile

Re: Ports with hardcoded "gcc", "g++"

On 2017/03/01 21:15, Juan Francisco Cantero Hurtado wrote: > On Wed, Mar 01, 2017 at 05:45:32PM +, Stuart Henderson wrote: > > On 2017/03/01 17:10, Juan Francisco Cantero Hurtado wrote: > > > On Tue, Feb 28, 2017 at 07:11:48PM +0100, Juan Francisco Cantero Hurtado > > > wrote: > > > > On Tue,

Re: Ports with hardcoded "gcc", "g++"

On Wed, Mar 01, 2017 at 05:45:32PM +, Stuart Henderson wrote: > On 2017/03/01 17:10, Juan Francisco Cantero Hurtado wrote: > > On Tue, Feb 28, 2017 at 07:11:48PM +0100, Juan Francisco Cantero Hurtado > > wrote: > > > On Tue, Feb 28, 2017 at 01:03:38PM +, Christian Weisgerber wrote: > > >

Re: Ports with hardcoded "gcc", "g++"

On 2017/03/01 17:10, Juan Francisco Cantero Hurtado wrote: > On Tue, Feb 28, 2017 at 07:11:48PM +0100, Juan Francisco Cantero Hurtado > wrote: > > On Tue, Feb 28, 2017 at 01:03:38PM +, Christian Weisgerber wrote: > > > The fixes that have been committed have unlocked additional parts > > > of

Re: Ports with hardcoded "gcc", "g++"

On Tue, Feb 28, 2017 at 07:11:48PM +0100, Juan Francisco Cantero Hurtado wrote: > On Tue, Feb 28, 2017 at 01:03:38PM +, Christian Weisgerber wrote: > > The fixes that have been committed have unlocked additional parts > > of the ports tree, revealing new build failures. Here is an updated > >

Re: Ports with hardcoded "gcc", "g++"

On Wed, Mar 1, 2017 at 10:44 AM, Amit Kulkarni wrote: > On Wed, Mar 1, 2017 at 10:10 AM, Frank Groeneveld > wrote: >> On Wed, Mar 1, 2017, at 15:14, Stuart Henderson wrote: >>> Oops, I forgot to re-run update-patches and had an old one. However >>>

Re: Ports with hardcoded "gcc", "g++"

On Wed, Mar 1, 2017 at 10:10 AM, Frank Groeneveld wrote: > On Wed, Mar 1, 2017, at 15:14, Stuart Henderson wrote: >> Oops, I forgot to re-run update-patches and had an old one. However >> unfortunately >> not enough as linking fails. >> > > Thanks, that gets us a lot

Re: Ports with hardcoded "gcc", "g++"

On Wed, Mar 1, 2017, at 15:14, Stuart Henderson wrote: > Oops, I forgot to re-run update-patches and had an old one. However > unfortunately > not enough as linking fails. > Thanks, that gets us a lot further indeed. The complete QT build finished and now only the final linking step fails

Re: Ports with hardcoded "gcc", "g++"

On 2017/03/01 12:12, Stuart Henderson wrote: > On 2017/03/01 11:02, Frank Groeneveld wrote: > > On Tue, Feb 28, 2017, at 14:03, Christian Weisgerber wrote: > > > textproc/wkhtmltopdf Frank Groeneveld > > > > I've been trying to fix textporc/wkhtmltopdf in the last few

Re: Ports with hardcoded "gcc", "g++"

On 2017/03/01 11:02, Frank Groeneveld wrote: > On Tue, Feb 28, 2017, at 14:03, Christian Weisgerber wrote: > > textproc/wkhtmltopdf Frank Groeneveld > > I've been trying to fix textporc/wkhtmltopdf in the last few days, but > can't seem to make qmake use the correct

Re: Ports with hardcoded "gcc", "g++"

On Tue, Feb 28, 2017, at 14:03, Christian Weisgerber wrote: > textproc/wkhtmltopdf Frank Groeneveld I've been trying to fix textporc/wkhtmltopdf in the last few days, but can't seem to make qmake use the correct compiler. The do-configure step of this port configures

Re: Ports with hardcoded "gcc", "g++"

> The fixes that have been committed have unlocked additional parts > of the ports tree, revealing new build failures. Here is an updated > list. I've added the MAINTAINERs .. > plan9/devdrawserver Gleydson Soares fixed.

Re: Ports with hardcoded "gcc", "g++"

On Tue, Feb 28, 2017 at 01:03:38PM +, Christian Weisgerber wrote: > The fixes that have been committed have unlocked additional parts > of the ports tree, revealing new build failures. Here is an updated > list. I've added the MAINTAINERs. > > lang/nimThe OpenBSD ports

Re: Ports with hardcoded "gcc", "g++"

The fixes that have been committed have unlocked additional parts of the ports tree, revealing new build failures. Here is an updated list. I've added the MAINTAINERs. archivers/hs-zlib Matthias Kilian audio/gogglesmm The OpenBSD ports mailing-list

Re: Ports with hardcoded "gcc", "g++"

> plan9/plan9port fixed.

Re: Ports with hardcoded "gcc", "g++"

Hi, On Mon, Feb 27, 2017 at 09:06:22PM +0100, Jeremie Courreges-Anglas wrote: > TODO > [...] > >> lang/ghc This one is weird. It has "autodetection", but just setting CC="${CC}" doesn't work, so I've added --with-ghc="${CC}", which seems to work (with /usr/bin/gcc and /usr/bin/g++ removed).

Re: Ports with hardcoded "gcc", "g++"

Stuart Henderson writes: > On 2017/02/26 16:00, Christian Weisgerber wrote: >> Ports are supposed to honor the CC and CXX variables. (There are >> some exceptions such as perl and imake ports that pick up a central >> setting.) They are not supposed to have hardcoded

Re: Ports with hardcoded "gcc", "g++"

On 2017/02/26 16:00, Christian Weisgerber wrote: > Ports are supposed to honor the CC and CXX variables. (There are > some exceptions such as perl and imake ports that pick up a central > setting.) They are not supposed to have hardcoded compiler names. > In particular they should not call "gcc"

Re: Ports with hardcoded "gcc", "g++"

On Sun, Feb 26, 2017 at 04:00:16PM +0100, Christian Weisgerber wrote: > Ports are supposed to honor the CC and CXX variables. (There are > some exceptions such as perl and imake ports that pick up a central > setting.) They are not supposed to have hardcoded compiler names. > In particular they

Ports with hardcoded "gcc", "g++"

Ports are supposed to honor the CC and CXX variables. (There are some exceptions such as perl and imake ports that pick up a central setting.) They are not supposed to have hardcoded compiler names. In particular they should not call "gcc" or "g++". Alas, this has never been strictly enfored,