Hi clever friends
I have a big big problem and I must find how to solve it, otherwise
my boss will not be very kind to me;-((
I've installed a lot of packages (BLAS, LAPACK, FFTW, GUILE, LIBCTL)
needed by the program MPB (calculation of photonic bandgap
structures) created by Massachusset Instit
Here in NetBSD land we aren't that happy using file(1) for
deplibs_check_method...
The reason that pass_all can't be used is that on some platforms linking
in a library of the form libfoo.a can cause problems. So Todd suggested
we use echo with file_magic and patterns that ld(1) uses to match sha
Alexandre Oliva wrote:
>
> On Mar 19, 2001, Michael Matz <[EMAIL PROTECTED]> wrote:
>
> > Bad. A real cool way around that would be, if libtool itself built (when
> > -module is given) both, the library and the module (which should be
> > possible, as the -module command line should include all
On Mar 23, 2001, Maria Chiara Ubaldi <[EMAIL PROTECTED]> wrote:
> ERROR In procedure dynamic-link:
> ERROR File not found
Not without a lot of additional information. For example, on which
platform is that? Where is the error coming from? Where does libtool
fit into this picture?
--
Alexand
On Mar 22, 2001, Tom Tromey <[EMAIL PROTECTED]> wrote:
> configure with --enable-shared=libgcc,libgcj to enable just
> those shared libraries.
> However, it turns out that in this same situation, libgcj really needs
> to know whether a shared libgcc is being built.
> Ordinarily I would do this
what commands should be required to be passed in to a build to make a shared
object? Sorry if this is a bit 101, bit I want to verify that a project is
passing in the correct command line before I go into too much more effort on
it.
Thanks.
david
__
On Mar 23, 2001, "David Reid" <[EMAIL PROTECTED]> wrote:
> what commands should be required to be passed in to a build to make
> a shared object?
libtool --mode=link $CC $CFLAGS $LDFLAGS objnames.lo -o libname.la $LIBS
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
R
