That's a really weird error. Can you post a link to the complete
install log? Also, what happenes if you build sage-4.0.2 (the latest
released version)? Also, is there anything funny about your
computer, e.g., post the output of typing "export" at the command
line.
In particular, this one doesn't work for you?
What error message do you get?
I regularly build Sage on 64-bit Suse Linux 11 with no trouble, which
is how I built the above binary.
-- William
On Wed, Jul 8, 2009 at 11:14 PM, Christian Weiss<weissi...@gmx.de> wrote:
>
> Hello,
>
> I tried to build a sage server on a SLES11-System. But the
> installation was aborted with the following error message:
<SNIP>
> make[1]: *** [installed/sqlite-3.5.3.p4] Fehler 1
> make[1]: Leaving directory `/home/cweiss/downloads/sage-4.1.rc1/spkg'
>
> real 0m0.918s
> user 0m0.664s
> sys 0m0.108s
> Error building Sage.
>
> ---------------------------</ERROR
> MESSAGE>-----------------------------------
>
> sqlite3 is installed on my SLES11 system (and I hoped that sage could
> use it...).
Sage includes sqlite 3, and that is the one that Sage uses. Replacing
components that are shipped with Sage with your system's components
will make debugging an order of magnitude more difficult. As the
number of components shipped with Sage are replaced with your system's
components, the combinatorial explosion is huge and would make
debugging almost impossible.
From the error log, it looks to me that you're not using a stable
version of Sage. In fact, you're using the development version Sage
4.1.rc1.
> Any downloadable binary version of sage won't work.
> I am new on Linux and don't know what to do to fix this problem. Maybe
> someone of you can help me!
--
Regards
Minh Van Nguyen
Not really, since the above works for you. I'm just happy to have
another satisfied customer.
What would be useful would be if you could explain why you wrote
before "Any downloadable binary version of sage won't work" since the
above was just one of the downloadable binaries we posted. It would
be very very useful to our webmaster (Harald Schilly), since clearly
our binary download page failed to help you find the right binary. So
if you could provide some constructive criticism about why it didn't
work for you, that would be nice.
-- William
On Wed, Jul 8, 2009 at 11:54 PM, William Stein<wst...@gmail.com> wrote:
>
> On Wed, Jul 8, 2009 at 6:49 AM, Christian Weiss<weissi...@gmx.de> wrote:
<SNIP>
>> Hello,
>>
>> IT WORKS! I have downloaded your linked file and: now it works!
>>
>> Thanks a lot!
>>
>> Are you any longer interested interested in the log-file of the
>> aborted installation? Then I put it on my server and give you the
>> link.
>
> Not really, since the above works for you. I'm just happy to have
> another satisfied customer.
>
> What would be useful would be if you could explain why you wrote
> before "Any downloadable binary version of sage won't work" since the
> above was just one of the downloadable binaries we posted. It would
> be very very useful to our webmaster (Harald Schilly), since clearly
> our binary download page failed to help you find the right binary. So
> if you could provide some constructive criticism about why it didn't
> work for you, that would be nice.
There have been some complaints about the download pages and we
welcome your feedback on why it doesn't work for you. Recently, Harald
Schilly redesigned the download pages so that download mirrors should
be easily visible on first glance. The rationale behind this redesign
is to reduce traffic on the master Sage server. People are encouraged
to download from a mirror nearest to them; see this page for a list of
mirrors:
http://www.sagemath.org/download.html
Clearly, the redesign or something about the download pages didn't
work as expected. Any thoughts on how we can make it better?
You might want to try
http://sage.math.washington.edu/home/kirkby/Solaris-fixes/sqlite-3.6.17/sqlite-3.6.17.spkg
which is an updated version of sqlite.
It is a trac ticket of mine, which needs review
http://sagetrac.org/sage_trac/ticket/6759
I created the new .spkg, since the old version of sqlite in Sage will
not build with Sun's C compiler. That new .spkg will build with both gcc
and Sun's compiler on Solaris. It might just solve your SUSE issue,
though I have not tested that. They may have paid a bit more attention
to portability in the latest release.
Dave