Hello Everyone,
I have an automake target that looks like this:
noinst_LTLIBRARIES = liblocate_paths.la
liblocate_paths_la_SOURCES = \
locate_paths.c \
locate_paths.h
liblocate_paths_la_LIBADD = -L @RPM_PREFIX@/lib -lrpm
Which generates the following libtool command
/bin/sh
b_search_path"; do
# Search the libtool library
lib="$searchdir/lib${name}.la"
if test -f "$lib"; then
=
Michael Bletzinger wrote:
>
> Hello Everyone,
>
> I have an au
The multi-language-branch does not have this problem. I'll go ahead and
use this baseline for now.
Michael
Michael Bletzinger wrote:
>
> Hello,
> I found a couple of problems that were causing this. The first is that
> ltmain.sh does not like a space betwe
't violate some design paradigm that would
prevent my patches from becoming accepted?
Thanks in Advance
Michael
----------
Michael Bletzinger Software Developer, Alliance Computational
[EMAIL PROTECTED] Environment &am
what I think happened.
>
At least on solaris and linux if you build gcc with the --enable-shared
flag then all of the run-time libraries will be built as shared and
static. This flag is disabled by default.
Michael
--
---
stdc++ then you need to eliminate all calls to it including the "<<"
and ">>" operators. Another option you might to try is listing
libstdc++.a as an object when you are creating your library.
My2Cworth
Michael
--
all of the libtool configuration pieces are compatible.
Michael
--
------
Michael Bletzinger Software Developer, Alliance Computational
[EMAIL PROTECTED] Environment & Security
217 265 5137NCSA
trying to install the CVS version, I
> think a prominent notice in the install instruction (or even a test in
> "bootstrap") would be a great enhancement.
>
> Regards, and thanks a lot for bringing us libtool!
>
> Bernar
