Date: Wed, 5 Jun 2019 22:41:08 +1200 From: Jonathan Chen <jonc@chen.org.nz> To: mandree@freebsd.org Cc: freebsd-ports@freebsd.org Subject: misc/e2fsprogs-libuuid build failures Message-ID: <CAJuc1zPie=zuf_u0x=R6t_tMY%2BTJOKWC6BMpbimn%2BTi_u%2Ba5xw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi,
I'm currently seeing build failures for misc/e2fsprogs-libuuid on
12-STABLE/amd64 (r347607) in the "configure" phase:
===> Configuring for e2fsprogs-libuuid-1.45.2
configure: loading site script /xports/Templates/config.site
Generating configuration file for e2fsprogs version 1.45.2
Release date is May, 2019
checking build system type... amd64-portbld-freebsd12.0
checking host system type... amd64-portbld-freebsd12.0
checking for gcc... cc
checking whether the C compiler works... no
configure: error: in `/construction/xports/misc/e2fsprogs-libuuid/work/e2fsprogs
-1.45.2':
configure: error: C compiler cannot create executables
See `config.log' for more details
The relevant part from 'config.log' contains:
configure:3325: cc -O2 -pipe -fstack-protector-strong
-fno-strict-aliasing -std=gnu99
-I/construction/xports/misc/e2fsprogs-libuuid/work/e2fsprogs-1.45.2/lib
-I/usr/local/include -fstack-protector-strong -fuse-ld=bfd conftest.c >&5
/usr/lib/crt1.o: file not recognized: File format not recognized
cc: error: linker command failed with exit code 1 (use -v to see invocation)
configure:3329: $? = 1
configure:3367: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
The "-fuse-ld=bfd" looks suspicious?
Cheers.
--
Jonathan Chen <jonc@chen.org.nz>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJuc1zPie=zuf_u0x=R6t_tMY%2BTJOKWC6BMpbimn%2BTi_u%2Ba5xw>