caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Erick Matsen <matsen@berkeley.edu>
To: "Stéphane Glondu" <steph@glondu.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] problem with LACAML and static linking
Date: Wed, 28 Jan 2009 10:50:29 -0800	[thread overview]
Message-ID: <243054520901281050n31220e98q4d9c37237e38c637@mail.gmail.com> (raw)
In-Reply-To: <4980A8B1.6030305@glondu.net>

Hm, unfortunately not the first one.

>> /usr/lib/libblas.a(xerbla.o): In function `xerbla_':
>> (.text+0x0): multiple definition of `xerbla_'
>> /usr/lib/liblapack.a(xerbla.o):(.text+0x0): first defined here

It doesn't link...


Thanks,

Erick


On Wed, Jan 28, 2009 at 10:49 AM, Stéphane Glondu <steph@glondu.net> wrote:
> Erick Matsen a écrit :
>> [...]
>> /usr/lib/libblas.a(xerbla.o): In function `xerbla_':
>> (.text+0x0): multiple definition of `xerbla_'
>> /usr/lib/liblapack.a(xerbla.o):(.text+0x0): first defined here
>> /usr/lib/ocaml/3.10.2/libasmrun.a(unix.o): In function `caml_dlopen':
>> (.text+0x223): warning: Using 'dlopen' in statically linked
>> applications requires at runtime the shared libraries from the glibc
>> version used for linking
>> /usr/lib/ocaml/3.10.2/libunix.a(getgr.o): In function `unix_getgrgid':
>> ... similar messages ....
>> [...]
>
> These are warnings, aren't they? Doesn't your program run if you ignore
> them? The warnings concern ocaml runtime, so I guess you cannot do much
> about it...
>
>
> Cheers,
>
> --
> Stéphane
>
>


  reply	other threads:[~2009-01-28 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28  6:48 Erick Matsen
2009-01-28  7:20 ` [Caml-list] " Stéphane Glondu
2009-01-28 17:17   ` Erick Matsen
2009-01-28 17:33     ` Mauricio Fernandez
2009-01-28 17:56       ` Erick Matsen
2009-01-28 18:49         ` Stéphane Glondu
2009-01-28 18:50           ` Erick Matsen [this message]
2009-01-28 19:05             ` Stéphane Glondu
2009-01-28 19:24               ` Markus Mottl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=243054520901281050n31220e98q4d9c37237e38c637@mail.gmail.com \
    --to=matsen@berkeley.edu \
    --cc=caml-list@inria.fr \
    --cc=steph@glondu.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).