[sage-devel] Re: sage-4.0.alpha0 build failure on OS X PPC

2009-05-23 Thread gsw

Hi,

good to hear that you were able to build Sage at last!
>From past discussions, and the bad experiences we had with MacPorts/
Fink intervening, I'd say "the glass is half full" rather than "the
glass is half empty".
It's quite a huge effort to make work "to build sage, simply type:
make", on a lot of systems at the same time. And something like a "no
custom C...Flags" patch might have problems on its own ...

Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-devel] Re: sage-4.0.alpha0 build failure on OS X PPC

2009-05-22 Thread Kevin Horton

On 21 May 2009, at 04:19, gsw wrote:

> Sage-4.0.alpha0 did build fine on my G4 PowerBook 550Mhz with OS X
> 10.4.11 and Xcode 2.5. From the istall.log:
>
> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -
> DOPERATION_scan1 -O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL -
> c scan1.c  -fno-common -DPIC -o .libs/scan1.o
> /bin/sh ../libtool --mode=compile --tag=CC ../mpn/m4-ccas --m4="m4"
> gcc -std=gnu99 -c -DHAVE_CONFIG_H-O2 -mpowerpc -no-cpp-precomp -
> force_cpusubtype_ALL -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo
> popcount | sed 's/_$//'` -I. -I. -I..  `test -f 'popcount.asm' || echo
> './'`popcount.asm
> ../mpn/m4-ccas --m4=m4 gcc -std=gnu99 -c -DHAVE_CONFIG_H -O2 -
> mpowerpc -no-cpp-precomp -force_cpusubtype_ALL -D__GMP_WITHIN_GMP -I..
> -DOPERATION_popcount -I. -I. -I.. popcount.asm  -fno-common -DPIC -
> o .libs/popcount.o
> m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_popcount -DPIC
> popcount.asm >tmp-popcount.s
> gcc -std=gnu99 -c -DHAVE_CONFIG_H -O2 -mpowerpc -no-cpp-precomp -
> force_cpusubtype_ALL -D__GMP_WITHIN_GMP -I.. -DOPERATION_popcount - 
> I. -
> I. -I.. tmp-popcount.s -fno-common -DPIC -o .libs/popcount.o
> /bin/sh ../libtool --tag=CC --mode=compile gcc -std=gnu99 -
> DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo
> hamdist | sed 's/_$//'`-O2 -mpowerpc -no-cpp-precomp -
> force_cpusubtype_ALL -c -o hamdist.lo hamdist.c
> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -
> DOPERATION_hamdist -O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL
> -c hamdist.c  -fno-common -DPIC -o .libs/hamdist.o
>
> As one can see, the compilation is done *with* the option "-
> force_cpusubtype_ALL".
>
> From the configuration output of the mpir package on my system:
> ...
> checking build system type... powerpc7450-apple-darwin8.11.0
> ...
> using ABI="32"
>  CC="gcc -std=gnu99"
>  CFLAGS="-O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL"
>  CPPFLAGS=""
>  CXX="g++"
>  CXXFLAGS="-O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL"
>  MPN_PATH=" powerpc32/vmx powerpc32 powerpc32 generic"
>
> From the configuration output of the install.log you posted:
> ...
> checking build system type... powerpc7450-apple-darwin9.7.0
> ...
> using ABI="32"
>  CC="gcc -std=gnu99"
>  CFLAGS="-I/sw/include"
>  CPPFLAGS="-I/sw/include"
>  CXX="g++"
>  CXXFLAGS="-I/sw/include"
>  MPN_PATH=" powerpc32/vmx powerpc32 powerpc32 generic"
>
> So there is some misconfiguration happening --- the mpir maintainers
> probably will find a solution quickly.
> (Beware, I'm uneasy about the occurence of the MacPorts (or Fink?)
> path "-I/sw/include" here.)

Yes, that looks suspicious.  For that build, the sage install detect  
the presence of fink, and offered two options:

You should make sure MacPorts and Fink cannot be found.  Either:
(1) rename /opt/local and /sw, or
(2) change PATH and DYLD_LIBRARY_PATH

I elected option (2), and changed PATH to remove /sw/bin and /sw/ 
sbin.  DYLD_LIBRARY_PATH was not set, so I left it alone.  Maybe that  
was a mistake, but I think it was an honest mistake, apt to be made by  
users who don't know what values to set DYLD_LIBRARY_PATH.

After that build failed, sage-4.0.rc0 dropped, so I tried installing  
it.  This time I used option (1) - I renamed /sw, and the build went OK.

Perhaps the options when /sw is detected need to be reworked.  Maybe  
the user should be given specific direction on what value to set for  
DYLD_LIBRARY_PATH.

--
Kevin Horton
Ottawa, Canada




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



[sage-devel] Re: sage-4.0.alpha0 build failure on OS X PPC

2009-05-22 Thread mabshoff



On May 21, 1:19 am, gsw  wrote:
> Hi,



> using ABI="32"
>       CC="gcc -std=gnu99"
>       CFLAGS="-O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL"
>       CPPFLAGS=""
>       CXX="g++"
>       CXXFLAGS="-O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL"
>       MPN_PATH=" powerpc32/vmx powerpc32 powerpc32 generic"
>
> From the configuration output of the install.log you posted:
> ...
> checking build system type... powerpc7450-apple-darwin9.7.0
> ...
> using ABI="32"
>       CC="gcc -std=gnu99"
>       CFLAGS="-I/sw/include"
>       CPPFLAGS="-I/sw/include"
>       CXX="g++"
>       CXXFLAGS="-I/sw/include"
>       MPN_PATH=" powerpc32/vmx powerpc32 powerpc32 generic"
>
> So there is some misconfiguration happening --- the mpir maintainers
> probably will find a solution quickly.
> (Beware, I'm uneasy about the occurence of the MacPorts (or Fink?)
> path "-I/sw/include" here.)

Yes, CFLAGS seems completely wrong. I have a patch that will not let
the user set custom [C|CPP|LD]FLAGS unless explicitly forcing Sage to
do so and it will print a big, fat warning in install.log. I doubt
this is Sage's fault, but I guess looking at MPIR's config.log in spkg/
build/gmp-mpir.../src/src should help.

Oh well.

> Cheers,
> gsw

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-devel] Re: sage-4.0.alpha0 build failure on OS X PPC

2009-05-21 Thread gsw

Hi,

Sage-4.0.alpha0 did build fine on my G4 PowerBook 550Mhz with OS X
10.4.11 and Xcode 2.5. From the istall.log:

 gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -
DOPERATION_scan1 -O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL -
c scan1.c  -fno-common -DPIC -o .libs/scan1.o
/bin/sh ../libtool --mode=compile --tag=CC ../mpn/m4-ccas --m4="m4"
gcc -std=gnu99 -c -DHAVE_CONFIG_H-O2 -mpowerpc -no-cpp-precomp -
force_cpusubtype_ALL -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo
popcount | sed 's/_$//'` -I. -I. -I..  `test -f 'popcount.asm' || echo
'./'`popcount.asm
 ../mpn/m4-ccas --m4=m4 gcc -std=gnu99 -c -DHAVE_CONFIG_H -O2 -
mpowerpc -no-cpp-precomp -force_cpusubtype_ALL -D__GMP_WITHIN_GMP -I..
-DOPERATION_popcount -I. -I. -I.. popcount.asm  -fno-common -DPIC -
o .libs/popcount.o
m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_popcount -DPIC
popcount.asm >tmp-popcount.s
 gcc -std=gnu99 -c -DHAVE_CONFIG_H -O2 -mpowerpc -no-cpp-precomp -
force_cpusubtype_ALL -D__GMP_WITHIN_GMP -I.. -DOPERATION_popcount -I. -
I. -I.. tmp-popcount.s -fno-common -DPIC -o .libs/popcount.o
/bin/sh ../libtool --tag=CC --mode=compile gcc -std=gnu99 -
DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo
hamdist | sed 's/_$//'`-O2 -mpowerpc -no-cpp-precomp -
force_cpusubtype_ALL -c -o hamdist.lo hamdist.c
 gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -
DOPERATION_hamdist -O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL
-c hamdist.c  -fno-common -DPIC -o .libs/hamdist.o

As one can see, the compilation is done *with* the option "-
force_cpusubtype_ALL".

>From the configuration output of the mpir package on my system:
...
checking build system type... powerpc7450-apple-darwin8.11.0
...
using ABI="32"
  CC="gcc -std=gnu99"
  CFLAGS="-O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL"
  CPPFLAGS=""
  CXX="g++"
  CXXFLAGS="-O2 -mpowerpc -no-cpp-precomp -force_cpusubtype_ALL"
  MPN_PATH=" powerpc32/vmx powerpc32 powerpc32 generic"

>From the configuration output of the install.log you posted:
...
checking build system type... powerpc7450-apple-darwin9.7.0
...
using ABI="32"
  CC="gcc -std=gnu99"
  CFLAGS="-I/sw/include"
  CPPFLAGS="-I/sw/include"
  CXX="g++"
  CXXFLAGS="-I/sw/include"
  MPN_PATH=" powerpc32/vmx powerpc32 powerpc32 generic"

So there is some misconfiguration happening --- the mpir maintainers
probably will find a solution quickly.
(Beware, I'm uneasy about the occurence of the MacPorts (or Fink?)
path "-I/sw/include" here.)

Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-devel] Re: sage-4.0.alpha0 build failure on OS X PPC

2009-05-19 Thread Kevin Horton

On 19 May 2009, at 20:55, mabshoff wrote:

>
> On May 19, 5:34 pm, Kevin Horton  wrote:
>>
>> On Tue, May 19, 2009 at 8:28 PM, mabshoff   
>> wrote:
>>
>>> On May 19, 5:22 pm, Kevin Horton  wrote:
 Should sage-4.0.alpha0 build on OS X 10.5 PPC?
>>
>>> Yes, it should. What XCode release are you using?
>>
>> I've got XCode 3.1.2, and now that I check I see that gives me gcc  
>> 4.0.1,
>> and the README says that is bad.
>
> No, gcc 4.0.0 is bad in many cases, but XCode 3.1.2 should work.
> Please post a link to the compressed install.log and I will take a
> look.
>

The install log is at:
http://www.kilohotel.com/misc/install.log.gz

>>  I'll look for a newer XCode, with at least
>> gcc 4.1
>
> There is none publicly available with any gcc post 4.0.1 by Apple
> AFAIK. XCode 3.1.2 is that latest available for OSX 10.5. And the
> problem is more likely to be an issue with the assembler IMHO anyway.
> What CPU are you running on exactly?

Its a G4, a 12" PowerBook.

Regards,

Kevin


--
Kevin Horton
Ottawa, Canada




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



[sage-devel] Re: sage-4.0.alpha0 build failure on OS X PPC

2009-05-19 Thread mabshoff



On May 19, 5:34 pm, Kevin Horton  wrote:
> Sorry about the last one - blasted Send button
>
> On Tue, May 19, 2009 at 8:28 PM, mabshoff  wrote:
>
> > On May 19, 5:22 pm, Kevin Horton  wrote:
> > > Should sage-4.0.alpha0 build on OS X 10.5 PPC?
>
> > Yes, it should. What XCode release are you using?
>
> I've got XCode 3.1.2, and now that I check I see that gives me gcc 4.0.1,
> and the README says that is bad.

No, gcc 4.0.0 is bad in many cases, but XCode 3.1.2 should work.
Please post a link to the compressed install.log and I will take a
look.

> I'll look for a newer XCode, with at least
> gcc 4.1

There is none publicly available with any gcc post 4.0.1 by Apple
AFAIK. XCode 3.1.2 is that latest available for OSX 10.5. And the
problem is more likely to be an issue with the assembler IMHO anyway.
What CPU are you running on exactly?

> Kevin

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-devel] Re: sage-4.0.alpha0 build failure on OS X PPC

2009-05-19 Thread Kevin Horton
Sorry about the last one - blasted Send button
On Tue, May 19, 2009 at 8:28 PM, mabshoff  wrote:

>
>
>
> On May 19, 5:22 pm, Kevin Horton  wrote:
> > Should sage-4.0.alpha0 build on OS X 10.5 PPC?
>
> Yes, it should. What XCode release are you using?
>

I've got XCode 3.1.2, and now that I check I see that gives me gcc 4.0.1,
and the README says that is bad.  I'll look for a newer XCode, with at least
gcc 4.1

Kevin

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



[sage-devel] Re: sage-4.0.alpha0 build failure on OS X PPC

2009-05-19 Thread mabshoff



On May 19, 5:22 pm, Kevin Horton  wrote:
> Should sage-4.0.alpha0 build on OS X 10.5 PPC?

Yes, it should. What XCode release are you using?

> --
> Kevin Horton
> Ottawa, Canada

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---