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: Fri, 12 Nov 2010 09:22:53 +1300 [thread overview]
Message-ID: <201011120922.53204.f.r.bissey@massey.ac.nz> (raw)
In-Reply-To: <20101111191125.GQ5225@denkmatte.mittag-leffler.se>
> Hi,
>
> On 09:41 Wed 10 Nov , Christopher Schwan wrote:
> > I followed the instructions listed in number 6 of the following page:
> > http://www.gentoo.org/proj/en/hardened/gnu-stack.xml . However, the fix
> > is incomplete (some architectures still have executable stacks) and I
> > had some problems with BASH:
> >
> > for i in $(find . -type f -name '*.asm') ; do
> >
> > echo $i >/dev/null
> > cat >> $i <<-EOF
> >
> > #if defined(__linux__) && defined(__ELF__)
> > .section .note.GNU-stack,"",%progbits
> > #endif
> >
> > EOF
> >
> > done
> >
> > If I remove the line with "echo" (which *should* be completely useless),
> > the cat command does not patch files - WHY ?! Also, mpir seemed to have
> > dropped yasm beginning with mpir-2.1 (?), so I think at least one loop
> > in mpir's ebuild is superfluous.
>
> I will look into this. What is the state for ppc and prefix ? In
> short: What keywords should we have on mpir? I can only test ~amd64 and
> ~x86.
>
Does work on ppc, I have emerged it regularly on my test machine.
We have stopped caring about using mpir in sage for now, so I don't think
Christopher tested it on prefix.
As for the echo stuff we had a chat with xarty the other day and they don't
seem to be necessary anymore. We suspect it was a bash (old version) problem.
As for your question for the executable stack flag, we don't really know, but
sage basically added it to LDFLAGS and we could try to do the same thing.
Francois
next prev parent reply other threads:[~2010-11-11 20:23 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
2010-11-10 8:41 ` Christopher Schwan
2010-11-11 19:11 ` Thomas Kahle
2010-11-11 20:22 ` François Bissey [this message]
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=201011120922.53204.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