On 4/30/14, 4:53 AM, Jack Howarth wrote:
> Remi,
>         I'll need to see a full build log and your list of installed
> fink packages to say more. Also have you tried moving aside /usr/local
> and /opt/local as well as limiting your .bashrc or .cshrc to just
> sourcing init.(c)sh? I still haven't seen any additional reports of this
> issue from any other users.
>            Jack
>
> On Wednesday, April 30, 2014, Remi Mommsen <[email protected]
> <mailto:[email protected]>> wrote:
>
>     Hi Jack,
>
>     On 29 Apr 2014, at 16:31, Jack Howarth <[email protected]
>     <javascript:;>> wrote:
>     Hi Jack,
>
>     it looks all fine to me:
>
>     $ which gcc
>     /usr/bin/gcc
>     $ gcc -v
>     Configured with:
>     --prefix=/Applications/Xcode.app/Contents/Developer/usr
>     --with-gxx-include-dir=/usr/include/c++/4.2.1
>     Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
>     Target: x86_64-apple-darwin13.1.0
>     Thread model: posix
>     $ which g++
>     /usr/bin/g++
>     $ g++ --version
>     Configured with:
>     --prefix=/Applications/Xcode.app/Contents/Developer/usr
>     --with-gxx-include-dir=/usr/include/c++/4.2.1
>     Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
>     Target: x86_64-apple-darwin13.1.0
>     Thread model: posix
>
>
>     The same when running within the gcc49 fink package:
>
>     + which gcc
>     /opt/fink/var/lib/fink/path-prefix-clang/gcc
>       gcc -v
>     + gcc -v
>     Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
>     Target: x86_64-apple-darwin13.1.0
>     Thread model: posix
>     clang: warning: argument unused during compilation:
>     '-Wno-error=unused-command-line-argument-hard-error-in-future'
>       which g++
>     + which g++
>     /opt/fink/var/lib/fink/path-prefix-libcxx/g++
>       g++ -v
>     + g++ -v
>     Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
>     Target: x86_64-apple-darwin13.1.0
>     Thread model: posix
>
>     Remi
>
>
>
>
>

It might be worth making sure that your libmpfr4 and gmp5 are locally 
built on the machine which is having problems rather than installing 
them from the binary distribution ('apt-cache policy <packagename>' is 
helpful here to verify where they're from), since those packages do some 
CPU tuning in their builds.

I've had problems with gcc4N before when using binaries of libmpfr4 and 
gmp5 which were built on a newer machine architecture than I had--they 
were built on a PowerPC G5 while I was on a G4.

-- 
Alexander Hansen, Ph.D.
Fink User Liaison
My package updates: http://finkakh.wordpress.com/

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Fink-users mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to