Hi,
I know this topic has been discussed on the mailing list before, but
I've not been able to pick out all of the relevant pieces of information
to solve the problem for my particular situation. Hopefully, someone on
the list can help.
My platform is ppc64 SLES 10 SP1, libtool version 1.5.2
Peter O'Gorman wrote:
Maynard Johnson wrote:
Hi,
I know this topic has been discussed on the mailing list before, but
I've not been able to pick out all of the relevant pieces of information
to solve the problem for my particular situation. Hopefully, someone on
the list can
Peter O'Gorman wrote:
Maynard Johnson wrote:
Peter O'Gorman wrote:
Maynard Johnson wrote:
Hi,
I know this topic has been discussed on the mailing list before, but
I've not been able to pick out all of the relevant pieces of information
to solve the problem fo
Peter O'Gorman wrote:
Maynard Johnson wrote:
#> ./libtool --version
ltmain.sh (GNU libtool) 1.5.24 (1.1220.2.455 2007/06/24 02:13:29)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warra
Peter O'Gorman wrote:
Maynard Johnson wrote:
Peter O'Gorman wrote:
Maynard Johnson wrote:
#> ./libtool --version
ltmain.sh (GNU libtool) 1.5.24 (1.1220.2.455 2007/06/24 02:13:29)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free soft
Peter O'Gorman wrote:
Hi Maynard,
I was hoping that your problems would all be gone :)
That certainly helped! We're getting further than before, but now
failing when building a C++ library as follows:
/bin/sh ../../libtool --tag=CXX --mode=link g++ -m64 -o
libjvmpi_opro
Peter O'Gorman wrote:
Maynard Johnson wrote:
Peter O'Gorman wrote:
Hi Maynard,
I was hoping that your problems would all be gone :)
That certainly helped! We're getting further than before, but now
failing when building a C++ library as follows:
--automake'.
3. Edit configure.in and add "AC_PROG_LIBTOOL" (I added it at line 19).
4. Run './autogen.sh'.
5. Run './configure --with-kernel-support --with-binutils=/usr'
6. Run 'make'. You should see the error.
I'm using lib
Peter O'Gorman wrote:
> Maynard Johnson wrote:
>
>> Hello,
>> We recently released OProfile 0.9.4, which for the first time includes
>> some libraries that must be installed along with the usual OProfile
>> tools. We introduced the use of libtool in our pro
at
collect2: ld returned 1 exit status
+
On this ppc64 system I'm developing on, the 64-bit BFD library is located in
/usr/lib64, but as you can see from above, the gcc command is specifying
/usr/lib/libbfd.so, which is the 32-bit library.
Any idea what could be the problem?
Maynard Johnson wrote:
> Hi, Peter,
> I posted to this list last winter regarding some problems I was having
> integrating libtool into a project (the oprofile project) -- in particular,
> building 64-bit on a bi-arch system (IBM POWER5). You helped with some usage
> problems an
figure out it needed to add the -lz. Is it
a bug that it can't figure this out when it should link with the default
/usr/lib64/libbfd.a?
Sorry for the length of this message. Thanks in advance for any help.
Regards,
-Maynard Johnson
___
http://lists.gnu.org/mailman/listinfo/libtool
Maynard Johnson wrote:
> Hello, Peter,
> I've run into another problem with building the oprofile project that seems
> like
> it might be an issue with libtool. Recent versions of binutils have made
> libbfd
I forgot to mention that the libtool version being used in my
ly happens when
the libraries in question are in their default install locations.
Thanks.
-Maynard
Maynard Johnson wrote:
Hello, Peter,
I've run into another problem with building the oprofile project that
seems like it might be an issue with libtool. Recent versions of
binutils have m
14 matches
Mail list logo
