Bug#676730: eflite: FTBFS: ld: cannot find -lsocket
Source: eflite
Version: 0.4.1-4
Severity: serious
Tags: wheezy sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20120609 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> gcc: fatal error: no input files
> compilation terminated.
> configure:2037: $? = 4
> configure:2060: checking for C compiler default output file name
> configure:2087: gcc conftest.c >&5
> configure:2090: $? = 0
> configure:2128: result: a.out
> configure:2145: checking whether the C compiler works
> configure:2155: ./a.out
> configure:2158: $? = 0
> configure:2175: result: yes
> configure:2182: checking whether we are cross compiling
> configure:2184: result: no
> configure:2187: checking for suffix of executables
> configure:2194: gcc -o conftest conftest.c >&5
> configure:2197: $? = 0
> configure:2221: result:
> configure:2227: checking for suffix of object files
> configure:2253: gcc -c conftest.c >&5
> configure:2256: $? = 0
> configure:2279: result: o
> configure:2283: checking whether we are using the GNU C compiler
> configure:2312: gcc -c conftest.c >&5
> configure:2318: $? = 0
> configure:2335: result: yes
> configure:2340: checking whether gcc accepts -g
> configure:2370: gcc -c -g conftest.c >&5
> configure:2376: $? = 0
> configure:2475: result: yes
> configure:2492: checking for gcc option to accept ISO C89
> configure:2566: gcc -c -g -O2 conftest.c >&5
> configure:2572: $? = 0
> configure:2595: result: none needed
> configure:2620: checking for connect in -lsocket
> configure:2655: gcc -o conftest -g -O2 -Wall conftest.c -lsocket >&5
> /usr/bin/ld: cannot find -lsocket
> collect2: error: ld returned 1 exit status
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/09/eflite_0.4.1-4_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Reply to: