|
From: Arthur N. <ac...@ca...> - 2012-01-09 17:39:52
|
> I've attached the config.log from the fox directory for your perusal.
>
Your previous email reported errors that contained the text "4.2", as in
"It builds on lion, but with the following errors:
:info:configure configure: Building for Macintosh/Darwin with X
:info:configure llvm-gcc-4.2: error trying to exec
'/usr/bin/../llvm-gcc-4.2/bin/powerpc-apple-darwin11-llvm-gcc-4.2':
execvp:
No such file or directory
:info:configure lipo: can't figure out the architecture type of:
/var/tmp//ccAr5REE.out
:info:configure llvm-gcc-4.2: error trying to exec"
while the one you have now sent us all does not show any mention of
llvm-gc-4.2 at all, and looks pretty reasonable to me (apart from the
fact that I can not promise that CSL will build effortlessly with any C
compiler other than the one that GNU autotools automatically select, i.e.
gcc, since I have not personally tested all other variants). So at the
level of the CSL/Reduce configure script for FOX I do not see evidence
here of an issue!
With regard to the bulk of the whole of the subversion repository for
Reduce, yes it is now quite big. If you do not use CSL at all (ie you are
just fetching for PSL) you can obviously just not fetch the csl directory
and save a LOT. Specifically csl/support-packages contains code that you
will not actually use during the build but is included to try to be extra
careful that (L)GPL rights holders are kept content, and some things that
are not even (L)GPL but are nevertheless imported from elsewhere are put
there for reference and politeness so that people can see the original
form of them. The README.* files there are intended to comment on
provenance and licencing. An individual who is just building Reduce but
does not intent to redistribute it does not need any of that 80 Mbytes!
Similarly when building just for CSL you do not need the 30+ Mbytes of PSL
stuff. And in neither case would jlisp or jslisp be needed. I am supposing
you would only fetch "trunk" and so will avoid the bulky historical
archives.
Might I suggest that if you ever try sending bulky log files you send them
just to me not to the whole newsgroup since there is a limit to the size
of attachment that is automatically accepted there.
I have a Mac with 10.7 on it - although by and large I do not find it by
any means my favourite machine, and I generally do not enjoy development
on that platform. But if there is a really easy recipe you can provide me
with and your most current set of scripts and you believe that with VERY
LITTLE EFFORT and no special magical background I could try running your
script so I can see its behaviour directly that might let me find out what
is going on better. But note that I do NOT use the Xcode gui or anything
other than a command line on a Mac when I do development there, and I do
not want to. And I have NEVER used Macports before and can not be assumed
to be willing to spend a lot of time readings its documentation and
understanding it!
Arthur
|