On Fri, Sep 4, 2009 at 1:11 PM, Dr. David Kirkby<[email protected]> wrote:
>
> Minh Nguyen wrote:
>> Hi David,
>>
>> On Fri, Sep 4, 2009 at 8:35 PM, Dr. David Kirkby<[email protected]> 
>> wrote:
>>
>> <SNIP>
>>
>>> Even a 32-bit build would not build on bsd for me. I don't know whether
>>> there is anything important in your path, since I notice you have your
>>> own $HOME/usr/bin prepended to the system path, so anything in there
>>>
>>> would be picked up first. I've just copied over some of your settings.
>>
>> I compiled GNU coreutils-7.4 under my home directory on bsd.math and
>> installed the binaries in $HOME/usr/bin. I pre-pend $HOME/usr/bin to
>> my PATH variable so that I would run GNU versions of, e.g. ls, cp, mv,
>> etc. Here's my PATH:
>>
>> [mv...@bsd ~]$ echo $PATH
>> /Users/mvngu/usr:/Users/mvngu/usr/bin:/bin:/sbin:/usr/bin:/usr/sbin:/sw/bin:/usr/local/bin:/usr/texbin
>>
>
> Thank you. I set up your path
>
> echo $PATH
> /Users/mvngu/usr:/Users/mvngu/usr/bin:/bin:/sbin:/usr/bin:/usr/sbin:/sw/bin:/usr/local/bin:/usr/texbin
>
> [kir...@bsd sage-4.1.2.alpha0]$ pwd
> /Users/kirkby/64/sage-4.1.2.alpha0
>
> but get an error installing 'R', so I don't even get as far as ECL.
>
> Any ideas?

Reinstalling the 64-bit fortran spkg will fix that problem.

William

>
>
> checking for long double... yes
> checking size of long double... 16
> checking for size_t... (cached) yes
> checking size of size_t... 8
> checking whether we can compute C Make dependencies... yes, using gcc
> -std=gnu99 -MM
> checking whether gcc -std=gnu99 supports -c -o FILE.lo... yes
> checking how to get verbose linking output from sage_fortran...
> configure: WARNING: cannot determine how to obtain linking information
> from sage_fortran
>
> checking for Fortran 77 libraries of sage_fortran...
> checking how to get verbose linking output from gcc -std=gnu99... rm:
> cannot remove `conftest.dSYM': Is a directory
> -v
> checking for C libraries of gcc -std=gnu99... rm: cannot remove
> `conftest.dSYM': Is a directory
>  -lcrt1.10.5.o -L/Users/kirkby/64/sage-4.1.2.alpha0/local/lib/
> -L/usr/lib/i686-apple-darwin9/4.0.1
> -L/Users/kirkby/64/sage-4.1.2.alpha0/local/lib
> -L/usr/lib/gcc/i686-apple-darwin9/4.0.1/x86_64
> -L/usr/lib/gcc/i686-apple-darwin9/4.0.1
> -L/usr/lib/gcc/i686-apple-darwin9/4.0.1/../../../i686-apple-darwin9/4.0.1
> -L/usr/lib/gcc/i686-apple-darwin9/4.0.1/../../.. -lgcc_s.10.5 -lSystem
> checking for dummy main to link with Fortran 77 libraries... rm: cannot
> remove `conftest.dSYM': Is a directory
> none
> checking for Fortran 77 name-mangling scheme... rm: cannot remove
> `conftest.dSYM': Is a directory
> unknown
> configure: WARNING: unknown Fortran name-mangling scheme
> checking whether sage_fortran appends underscores to external names...
> unknown
> configure: error: cannot use Fortran
> Error configuring R.
>
> real    0m42.823s
> user    0m13.749s
> sys     0m25.588s
> sage: An error occurred while installing r-2.6.1.p23
> Please email sage-devel http://groups.google.com/group/sage-devel
> explaining the problem and send the relevant part of
> of /Users/kirkby/64/sage-4.1.2.alpha0/install.log.  Describe your
> computer, operating system, etc.
> If you want to try to fix the problem, yourself *don't* just cd to
> /Users/kirkby/64/sage-4.1.2.alpha0/spkg/build/r-2.6.1.p23 and type 'make'.
> Instead type "/Users/kirkby/64/sage-4.1.2.alpha0/sage -sh"
> in order to set all environment variables correctly, then cd to
> /Users/kirkby/64/sage-4.1.2.alpha0/spkg/build/r-2.6.1.p23
> (When you are done debugging, you can type "exit" to leave the
> subshell.)
> make[1]: *** [installed/r-2.6.1.p23] Error 1
>
>
> >
>



-- 
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to