public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: "François Bissey" <f.r.bissey@massey.ac.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci-libs/mpir for the main tree
Date: Tue, 9 Nov 2010 21:19:54 +1300	[thread overview]
Message-ID: <201011092119.54408.f.r.bissey@massey.ac.nz> (raw)
In-Reply-To: <20101108234212.GN1906@denkmatte.mittag-leffler.se>

> Hi,
> 
> my next migration victim will be mpir, the friendly clone of gmp.  The
> current ebuild is the same in sage-on-gentoo and science.  It has this
> assembler stuff in it that I don't understand.  Who did this? What is
> the latest here, can we remove the fat TODO-banner (or DO it?).
> 
> Any other hints/objections?  (Yes, I know that there is a bump
> waiting...)
> 
Hi Thomas,

Christopher did it. mpir like gmp suffer from executable stacks.
There are talk on sage-devel which is very close to mpir upstream
to take a different approach: using an m4 macro and a linker flag
to remove them -Wl,-z,noexecstack. 
The motivation to fix this is fedora 14 which doesn't allow executable stacks 
by default.
I think the warning could be removed for now but the ebuild will probably
need a little TLC in the near future.

Francois



  reply	other threads:[~2010-11-09  9:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 23:42 [gentoo-science] sci-libs/mpir for the main tree Thomas Kahle
2010-11-09  8:19 ` François Bissey [this message]
2010-11-10  8:41   ` Christopher Schwan
2010-11-11 19:11     ` Thomas Kahle
2010-11-11 20:22       ` François Bissey
2010-11-11 20:30         ` François Bissey
2010-11-11 19:35     ` Thomas Kahle
2010-12-17 13:00   ` Thomas Kahle
2010-12-17 13:22     ` Christopher Schwan
2010-12-17 13:55       ` Thomas Kahle
2010-12-17 14:16         ` Christopher Schwan
2010-12-17 15:03           ` Thomas Kahle

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=201011092119.54408.f.r.bissey@massey.ac.nz \
    --to=f.r.bissey@massey.ac.nz \
    --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