public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: v_2e@ukr.net
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] undefined symbol: dgetri_  --  again.
Date: Tue, 12 Oct 2010 11:40:28 +0300	[thread overview]
Message-ID: <20101012114028.c1bbd8eb.v_2e@ukr.net> (raw)
In-Reply-To: <201010122128.55523.f.r.bissey@massey.ac.nz>

On Tue, 12 Oct 2010 21:28:55 +1300
François Bissey <f.r.bissey@massey.ac.nz> wrote:

> Yes you have the typical configuration that was leading to trouble and
> that we have dealt with. If you are using the latest linbox ebuild from the
> overlay and it still doesn't work, send us the output of 
> ldd /usr/lib64/liblinboxsage.so
  I'm using the
'/var/lib/layman/sage-on-gentoo/sci-libs/linbox/linbox-1.1.6-r3.ebuild'
from yesterday-synced layman 'sage-on-gentoo' overlay.

ldd /usr/lib64/liblinboxsage.so gives the following:

	linux-vdso.so.1 =>  (0x00007fffd2f75000)
	libntl-5.5.2.so => /usr/lib/libntl-5.5.2.so (0x00007ff6a00a6000)
	liblinbox.so.0 => /usr/lib/liblinbox.so.0 (0x00007ff69fe95000)
	libblas.so.0 => /usr/lib/libblas.so.0 (0x00007ff69fc72000)
	libgmp.so.10 => /usr/lib/libgmp.so.10 (0x00007ff69fa03000)
	libgivaro.so.0 => /usr/lib/libgivaro.so.0 (0x00007ff69f7b2000)
	libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/libstdc
++.so.6 (0x00007ff69f49e000) libm.so.6 => /lib/libm.so.6
(0x00007ff69f21d000) libc.so.6 => /lib/libc.so.6 (0x00007ff69eeb7000)
	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007ff69ec9f000)
	libgmp.so.3 => /usr/lib/libgmp.so.3 (0x00007ff69ea48000)
	libgf2x.so.1 => /usr/lib/libgf2x.so.1 (0x00007ff69e83a000)
	libgfortran.so.3
=> /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/libgfortran.so.3
(0x00007ff69e54b000) libatlas.so.0 => /usr/lib/libatlas.so.0
(0x00007ff69df07000) /lib64/ld-linux-x86-64.so.2 (0x00007ff6a0889000)

> And also how recently you have synced the main tree, has the last fix
> required an eclass bug to be fixed.
  I have synced the main tree yesterday, just before updating Sage and
the packages it depends on.
  I'm not sure I understand you right about 'has the last fix required
an eclass bug to be fixed'.
> 
> Francois

Vladimir
----- 
 <v_2e@ukr.net>



  reply	other threads:[~2010-10-12  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12  8:07 [gentoo-science] undefined symbol: dgetri_ -- again v_2e
2010-10-12  8:11 ` François Bissey
2010-10-12  8:20   ` v_2e
2010-10-12  8:28     ` François Bissey
2010-10-12  8:40       ` v_2e [this message]
2010-10-12  8:52         ` François Bissey
2010-10-12  9:32           ` v_2e
2010-10-12 10:02             ` François Bissey

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=20101012114028.c1bbd8eb.v_2e@ukr.net \
    --to=v_2e@ukr.net \
    --cc=gentoo-science@lists.gentoo.org \
    /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