public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo] polybori && amd64
Date: Fri, 20 Aug 2010 09:10:06 -0500	[thread overview]
Message-ID: <1282313417.19920.0@pavilion64> (raw)
In-Reply-To: <201008201006.54121.cschwan@students.uni-mainz.de> (from cschwan@students.uni-mainz.de on Fri Aug 20 03:06:53 2010)

[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]

Hi Christopher,

On 08/20/2010 03:06:53 AM, Christopher Schwan wrote:
> Hi Steve,
> 
> On Thursday 19 August 2010 19:32:23 Steven Trogdon wrote:
>> On 08/19/2010 03:04:54 AM, Christopher Schwan wrote:
>> > Hi,
>> >
>> > On Thursday 19 August 2010 08:14:08 Steven Trogdon wrote:
>> >> Hello,
>> >>
>> >> Both polybori-0.6.4-r1 and polybori-0.6.5 fail to build here on amd64
>> >> for the same reason. The important snippet is:
>> >>
>> >> rm: cannot remove
>> >> `/var/tmp/portage/sci-mathematics/polybori-0.6.4-r1/image//usr/lib64/lib
>> >> *.s o*': No such file or directory
>> >>
>> >>   * ERROR: sci-mathematics/polybori-0.6.4-r1 failed:
>> >>   *   failed to remove shared objects
>> >>   *
>> >>   * Call stack:
>> >>   *     ebuild.sh, line  54:  Called src_install
>> >>   *   environment, line 5124:  Called die
>> >>   * The specific snippet of code:
>> >>   *       rm "${ED}"/usr/$(get_libdir)/lib*.so* || die "failed to remove
>> >>
>> >> shared objects"
>> >>
>> >>   *
>> >>
>> >> Under the /image directory polybori installs the libs under /usr/lib
>> >> instead of /usr/lib64. This seemed to be an issue previously with
>> >> polybori.
>> >
>> > Fixed in overlay - I will try to find find out how to install to lib64 on
>> > amd64.
>> 
>> With the present commit I get multilib-strict failures. I forgot about
>> this! I put the following:
>> 
>>      sed -i "s:DevelInstPath('lib'):DevelInstPath('$(get_libdir)'):g" \
>>          	SConstruct || die "sed failed"
>> 
>> in src_prepare and libs are installed under /usr/lib64 on amd64 and under
>> /usr/lib on my 32bit chroot. I'm not sure if this is the "correct" way to
>> fix things but maybe it'll give some direction.
> 
> Thank you for your info! I will update polybori later this day (I currently  
> do
> not have access to an amd64 machine) and see if its possible to fix this  
> issue
> with an command line argument (that would be the correct way).
> 
> Besides polybori, do you have any other multilib-strict failures for sage-
> related ebuilds ?
> 

I haven't seen other ebuilds recently with this problem. I looked at adjusting  
the PARAMS variable but could find nothing to pass to scons that would do the  
job. I could have missed something.

>> 
>> >> Steve
>> >
>> > Christopher
>> 
>> Steve
> 
> Christopher
> 

Steve

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-08-20 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19  6:14 [gentoo-science] [sage-on-gentoo] polybori && amd64 Steven Trogdon
2010-08-19  8:04 ` Christopher Schwan
2010-08-19 17:32   ` Steven Trogdon
2010-08-20  8:06     ` Christopher Schwan
2010-08-20 14:10       ` Steven Trogdon [this message]

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=1282313417.19920.0@pavilion64 \
    --to=strogdon@d.umn.edu \
    --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