[Redirecting this to the <debian-hurd@lists.debian.org> mailing list.]
Hello!
On Tue, Apr 21, 2009 at 07:56:58PM -0500, Justin Haynes wrote:
> Is there any reason why I would be getting the following from a generic
> ./configure script? I've already sent email to the author, Colin Percival,
> about this software, tarsnap, which I'm trying to compile on The Hurd. To
> my knowledge it has never been compiled on The Hurd before.
>
> Also, where would be the best place to ask this type of question? On irc?:
Either on IRC (when someone knowledgeable is around), or on
<bug-hurd@gnu.org>, or on <debian-hurd@lists.debian.org>. As I remeber
something that this was / is a Debian-specific problem, I now chose the
latter one.
> justin@flubber:~/tarsnap/tarsnap-autoconf-1.0.21$ uname -a
> GNU flubber 0.3 GNU-Mach 1.3.99/Hurd-0.3 i386-AT386 GNU
> justin@flubber:~/tarsnap/tarsnap-autoconf-1.0.21$ ./configure
> [...]
> checking for gcc... gcc
> checking for C compiler default output file name...
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
> justin@flubber:~/tarsnap/tarsnap-autoconf-1.0.21$
config.log:
> configure:2908: checking for C compiler default output file name
> configure:2930: gcc conftest.c >&5
> /usr/lib/gcc/i486-gnu/4.3.3/libgcc_s.so: file not recognized: File truncated
> collect2: ld returned 1 exit status
... and indeed:
tschwinge@flubber:~ $ ls -l /usr/lib/gcc/i486-gnu/4.3.3/libgcc_s.so
-rw-r--r-- 1 root root 0 Apr 17 01:14 /usr/lib/gcc/i486-gnu/4.3.3/libgcc_s.so
I remember something that Michael or Samuel fixed this problem, so I
removed the bogus file, reinstalled the gcc-4.3 package, and voilà:
tschwinge@flubber:~ $ ls -l /usr/lib/gcc/i486-gnu/4.3.3/libgcc_s.so
-rw-r--r-- 1 root root 0 Apr 17 01:14 /usr/lib/gcc/i486-gnu/4.3.3/libgcc_s.so
Uh.
OK, brute force:
tschwinge@flubber:~ $ sudo ln -sf /lib/libgcc_s.so.1 /usr/lib/gcc/i486-gnu/4.3.3/libgcc_s.so
Please try again now.
Regards,
Thomas
Attachment:
signature.asc
Description: Digital signature