checking whether to build static libraries... no checking whether ln -s works... yes ./configure: line 13244: syntax error near unexpected token `-Wparentheses,' ./configure: line 13244: `AX_CHECK_COMPILE_FLAG(-Wparentheses, DEFAULT_CFLAGS="$DEFAULT_CFLAGS -Wparentheses")' !!! Please attach the following file when seeking support: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-20210131-101856 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.2.0 * Python 3.8.7 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-1.48.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.272_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Mon Feb 1 04:47:49 UTC 2021 emerge -qpvO www-client/httrack [ebuild N ] www-client/httrack-3.49.2-r2 USE="-libressl -static-libs"
Created attachment 685389 [details] emerge-info.txt
Created attachment 685392 [details] emerge-history.txt
Created attachment 685395 [details] environment
Created attachment 685398 [details] etc.portage.tar.bz2
Created attachment 685401 [details] logs.tar.bz2
Created attachment 685404 [details] temp.tar.bz2
Created attachment 685407 [details] www-client:httrack-3.49.2-r2:20210201-062026.log
I have tried with both Bash and Dash for a system shell, no error like that: [..] checking whether ln -s works... yes checking whether C compiler accepts -Wparentheses... yes <-- checking whether C compiler accepts -Winit-self... yes [..] And the line in file configure looks sane too. My guess is that either the breakage is outside of httrack and hasn't hit my system yet or you have something crazy like memory corruption from broken hardware, even though that probably sounds crazy and super unlikely. How should we proceed? I definitely need some ideas or help here. Thanks and best, Sebastian
Does CFLAGS="-O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16" in make.conf (pls see attached etc.portage,tar.bz2) force it ?
(In reply to Toralf Förster from comment #9) > Does > > CFLAGS="-O2 -pipe -march=native -fno-diagnostics-color > -falign-functions=32:25:16" > > in make.conf (pls see attached etc.portage,tar.bz2) force it ? No, just tried.