This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Solaris 2.7 compilation of binutils-2.10 with Workshop compilers fails
- To: Bob Deblier <bob at virtualunlimited dot com>
- Subject: Re: Solaris 2.7 compilation of binutils-2.10 with Workshop compilers fails
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 18 Jul 2000 14:57:28 -0300
- Cc: binutils at sourceware dot cygnus dot com
- Organization: GCC Team, Red Hat
- References: <3974500A.CFF171A4@virtual-unlimited.com>
On Jul 18, 2000, Bob Deblier <bob@virtualunlimited.com> wrote:
> ld: fatal: file libbfd-2.10.so: open failed: No such file or directory
Yup, it's a bug in libtool, for which I posted a patch quite a long
time ago. Unfortunately, it didn't make it to the release (in fact,
nobody ever commented on it :-(, so it's not in the binutils CVS tree
either. Here's the patch again, for reference:
Index: ChangeLog
from Alexandre Oliva <aoliva@cygnus.com>
* ltconfig (with_gnu_ld): Check whether the compiler actually uses
GNU ld.
Index: ltconfig
===================================================================
RCS file: /cvs/src/src/ltconfig,v
retrieving revision 1.2
diff -u -r1.2 ltconfig
--- ltconfig 2000/02/27 16:46:19 1.2
+++ ltconfig 2000/04/03 05:25:03
@@ -1,7 +1,7 @@
#! /bin/sh
# ltconfig - Create a system-specific libtool.
-# Copyright (C) 1996-1999 Free Software Foundation, Inc.
+# Copyright (C) 1996-2000 Free Software Foundation, Inc.
# Originally by Gordon Matzigkeit <gord@gnu.ai.mit.edu>, 1996
#
# This file is free software; you can redistribute it and/or modify it
@@ -170,7 +170,7 @@
PROGRAM=ltconfig
PACKAGE=libtool
VERSION=1.3.4
-TIMESTAMP=" (1.385.2.196 1999/12/07 21:47:57)"
+TIMESTAMP=" (1.385.2.196 1999/12/07 21:47:57, modified)"
ac_compile='${CC-cc} -c $CFLAGS $CPPFLAGS conftest.$ac_ext 1>&5'
ac_link='${CC-cc} -o conftest $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS 1>&5'
rm="rm -f"
@@ -1058,6 +1058,27 @@
with_gnu_ld=no
fi
echo "$ac_t$with_gnu_ld" 1>&6
+
+if test "$with_gnu_ld" = yes && test -n "$wl"; then
+ echo $ac_n "checking if the compiler ($CC) uses GNU ld... $ac_c" 1>&6
+ # Check whether this is the linker used by CC, but only if we have
+ # -Wl, or equivalent, otherwise `-v' may be interpreted by the
+ # compiler.
+ "$LD" -v 2>&1 < /dev/null | egrep '(GNU|with BFD)' > conftest.ld
+ rm -f conftest.c
+ echo 'int main() {}' > conftest.c
+ ${CC-cc} -o conftest $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS ${wl}-v 2>&1 |
+ egrep '(GNU|with BFD)' > conftest.ld2
+ if cmp -s conftest.ld conftest.ld2; then
+ with_gnu_ld=yes
+ else
+ with_gnu_ld=no
+ fi
+ echo "$ac_t$with_gnu_ld" 1>&6
+else
+ # Assume the worst
+ with_gnu_ld=no
+fi
# See if the linker supports building shared libraries.
echo $ac_n "checking whether the linker ($LD) supports shared libraries... $ac_c" 1>&6
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me