From: "François Bissey" <frp.bissey@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Emerge singular-3.1.6::sage-on-gentoo fails on gentoo-3.16.5 gcc 4.8.3 with graphite and lto
Date: Mon, 17 Nov 2014 23:51:14 +1300 [thread overview]
Message-ID: <6C21A09D-70D7-4A8C-9A09-859256F40D7D@slingshot.co.nz> (raw)
In-Reply-To: <CAGNNSABjyfdH7yik+cqbhVg=ors62=szuUJiCsv4v47izHX4wg@mail.gmail.com>
I pushed a singular-3.1.6-r1 which I think would solve your issue based on similar
report upstream (although probably from a different origin). Can you test it?
If it works I will probably need to fix libsingular in the way before you can merge sage
properly.
François
> On 17/11/2014, at 23:09, Jeramia Poland <jeramia.poland@gmail.com> wrote:
>
> Okay, thanks for replying and taking a look. I was stumped and I was considering doing something foolish like installing CentOS.
>
> Jeramia
>
> On Mon, Nov 17, 2014 at 3:17 PM, François Bissey <frp.bissey@gmail.com> wrote:
> I probably need to patch the hard coded bit like sage upstream did. I spent most of the day
> on the bump 6.4/6.5.beta0 I shall do something about singular next before I finish the annoying bits
> on 6.5.beta0
>
> François
> > On 17/11/2014, at 22:40, Jeramia Poland <jeramia.poland@gmail.com> wrote:
> >
> > I attempted to emerge with -fimplicit-template (I added to the existing) but it didn't work. Spitefully, it seems to have continued to use -fno-implicit-template.
> >
> > Jeramia
> >
> > On Sat, Nov 15, 2014 at 5:03 PM, François Bissey <frp.bissey@gmail.com> wrote:
> > If you read that trac ticket symbols defined in ntl change depending on the version
> > of gcc. It is all about how you deal with c++ templates by default. The options
> > you are using are no doubt part f the mix. Although graphite is unlikely to
> > be the problem here, more likely lto.
> >
> > You could try to emerge singular with CXXFLAGS=-fimplicit-template
> > not sure that will work without a patch.
> >
> > François
> > > On 16/11/2014, at 00:18, Jeramia Poland <jeramia.poland@gmail.com> wrote:
> > >
> > > I have ntl-6.1.0 installed. I can wait til Monday; I'm surprised it might be an actual issue and not something I've done to myself.
> > >
> > > Jeramia
> > >
> > > On Sat, Nov 15, 2014 at 4:42 AM, François Bissey <frp.bissey@gmail.com> wrote:
> > > It looks very similar to http://trac.sagemath.org/ticket/16882#comment:29.
> > > Which version of ntl have you emerged? you should keep clear of the latest
> > > version of ntl.
> > >
> > > I cannot do much in terms of fix until Monday. My main dev machine is at
> > > work and it looks like we had another power cut and it is now off.
> > >
> > > François
> > >
> >
> >
> >
>
>
>
next prev parent reply other threads:[~2014-11-17 10:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 15:50 [gentoo-science] Emerge singular-3.1.6::sage-on-gentoo fails on gentoo-3.16.5 gcc 4.8.3 with graphite and lto Jeramia Poland
2014-11-14 23:12 ` François Bissey
2014-11-15 11:18 ` Jeramia Poland
2014-11-15 11:33 ` François Bissey
2014-11-17 9:40 ` Jeramia Poland
2014-11-17 9:47 ` François Bissey
2014-11-17 10:09 ` Jeramia Poland
2014-11-17 10:51 ` François Bissey [this message]
2014-11-17 12:43 ` Jeramia Poland
2014-11-17 17:55 ` François Bissey
2014-11-17 20:50 ` 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=6C21A09D-70D7-4A8C-9A09-859256F40D7D@slingshot.co.nz \
--to=frp.bissey@gmail.com \
--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