From: JC D <mail2jcdx@yahoo.de>
To: "gentoo-science@lists.gentoo.org" <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] Question before setting up sage-on-gentoo
Date: Thu, 29 Jan 2015 14:21:01 +0000 (UTC) [thread overview]
Message-ID: <1703897860.2590229.1422541261802.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <57925423-CB69-44D2-9B3E-EBB834289B00@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]
Hi,here are the first results. It did not work so far because I found my gcc-4.7.3 on gentoo_prefix (Mac OS 10.10) is broken. emerge gcc works and installs but if I try to compile a simple hello.cpp I get a segmentation fault 11. I am using the new binutils-apple-6.1. So far it seems that I can not get a newer gcc and thus also no llvm or any other package that asks for a more recent gcc. Right now I get a working basic system but almost all "higher" application fail to build one or the other way.
Now I try to get llvm/clang working. For the compilation I am going to use the native llvm-gcc and llvm-g++ from Mac.
I set up a package.env for llvm with:sys-devel/llvm llvm.conf
llvm.conf contains:CC=/usr/bin/llvm-gcc
CXX=/usr/bin/llvm-g++
The compilation works but there is an error when writing the llvm files to the right path. Here are emerge --infoshow at bpaste
| |
| | | | | | | |
| show at bpastePortage 2.2.14-prefix (python 3.3.3-final-0, prefix/darwin/macos/10.10/x64, gcc-4.2.1, unavailable, 14.1.0 x86_64)==================================... |
| |
| Auf bpaste.net anzeigen | Vorschau nach Yahoo |
| |
| |
and the log file https://bpaste.net/show/62a0d5b0d4f4
I will experiment further ...
François Bissey <frp.bissey@gmail.com> schrieb am 18:45 Montag, 26.Januar 2015:
Hi,
Well that would be an interesting experiment. You may have to limit yourself
to gcc 4.7.x, I haven’t been able to get 4.8 to compile and I think that the old
binutils is too blame. For env you could set CC CXX F77 and FC with the
appropriate x86_64-apple-darwin14-{gcc,g++,gfortran}-4.7.3 value.
I would be interested in your experience if you decide to go ahead.
François
> On 27/01/2015, at 02:42, JC D <mail2jcdx@yahoo.de> wrote:
>
> Hi!
> I want to install sage-on-gentoo using gentoo_prefix on a Mac OS 10.10.
> My first try was not successful and it seems it was related to the "kind of outdated" gcc-apple compiler that is originally used in gentoo_prefix on Mac.
> I have a question: Would it be possible to install a more recent gcc such as gcc-4.8 (as soon as it is unmasked) and then build the whole sage-on-gentoo with this compiler, but keeping the rest untouched?
> And how could I do this? Would it be possible to set up layman using the gcc-4.8 for everything in the overlay or could I use /etc/portage/env for that?
> Best regards from a newbie
>
[-- Attachment #2: Type: text/html, Size: 12840 bytes --]
next prev parent reply other threads:[~2015-01-29 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 13:42 [gentoo-science] Question before setting up sage-on-gentoo JC D
2015-01-26 17:44 ` François Bissey
2015-01-29 14:21 ` JC D [this message]
2015-01-29 19:09 ` François Bissey
2015-01-30 0:04 ` [gentoo-science] clang on Mac OS X (Was: Question before setting up sage-on-gentoo) heroxbd
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=1703897860.2590229.1422541261802.JavaMail.yahoo@mail.yahoo.com \
--to=mail2jcdx@yahoo.de \
--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