Jack wrote:
> I now get this error trying to emerge two different packages:
> libofx-0.10.7 and gnupg (both 2.2.39 and 2.3.6). It might also be the
> same problem for a few bugs on b.g.o found by searching on "cannot
> create exectuables."
>
> The relevant lines from build.log are
>
> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
> checking whether the C compiler works... no
> configure: error: in
> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
>
> and from config.log:
>
> Thread model: posix
> Supported LTO compression algorithms: zlib
> gcc version 11.3.0 (Gentoo 11.3.0 p4)
> configure:2952: $? = 0
> configure:2941: x86_64-pc-linux-gnu-gcc -V >&5
> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option '-V'
> x86_64-pc-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> configure:2952: $? = 1
> configure:2941: x86_64-pc-linux-gnu-gcc -qversion >&5
> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option
> '-qversion'; did you mean '--version'?
> x86_64-pc-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> configure:2952: $? = 1
> configure:2972: checking whether the C compiler works
> configure:2994: x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -og
> -ggdb -Wl,-O1 -Wl,--as-needed conftest.c >&5
> configure:2998: $? = 0
> configure:3036: result: no
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "libofx"
> | #define PACKAGE_TARNAME "libofx"
> | #define PACKAGE_VERSION "0.10.7"
> | #define PACKAGE_STRING "libofx 0.10.7"
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE_URL ""
> | /* end confdefs.h. */
> |
> | int
> | main ()
> | {
> |
> | ;
> | return 0;
> | }
> configure:3041: error: in
> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
> configure:3043: error: C compiler cannot create executables
> See `config.log' for more details
>
> The thing I find curious is that it appears to me that the output of
> the test compile is a file called "g" which I don't recall ever
> seeing, and so I wonder if the problem is that something has changed
> with gcc defaults and configure does not yet recognize that change. I
> also don't know the significance of the two "fatal error: no input
> files".
>
> The fact that this happens with two unrelated packages suggests that
> it's not specific to either of them, but something in my system or
> configuration.
>
> Any thoughts or suggestions?
>
> Jack
>
>
>
I ran into this ages ago. I think the fix was to reset which compiler
it is set to use. I used to keep two installed, in case one would fail
or some package couldn't build with a newer version yet. If I recall
correctly, I would list the available options with gcc-config -l and
then if two are available, set to older one and then change back or if
only one is installed, just set it to the one you have. It's been a
good while and it could be that the cause of the problem has changed but
I don't think it will hurt anything to try this. I think some settings
gets messed up and resetting it fixes it.
Hope that helps. If not, clueless. :/
Dale
:-) :-)
