On Thu, Aug 21, 2008 at 3:54 PM, Aleksej Saushev <[EMAIL PROTECTED]> wrote:
> "Gabriel Dos Reis" <[EMAIL PROTECTED]> writes:
>
>> On Thu, Aug 21, 2008 at 12:03 PM, Aleksej Saushev <[EMAIL PROTECTED]> wrote:
>>> "Gabriel Dos Reis" <[EMAIL PROTECTED]> writes:
>>>
>>>> On Thu, Aug 21, 2008 at 2:02 AM, Aleksej Saushev <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> CLISP-based OpenAxiom works fine.
>>>>
>>>> Excellent news!
>>>>
>>>>> Rechecking ECL now.
>>>>
>>>> OK.
>>>
>>> cd algebra && /usr/pkg/bin/gmake
>>> gmake[2]: Entering directory
>>> `/var/tmp/pkgsrc/wip/openaxiom/work/open-axiom/src/algebra'
>>> ../interp/interpsys -- --system="../../i386--netbsdelf"
>>> --sysalg="../../src/share/algebra/" --compile --output=strap/ABELGRP.fas
>>> strap/ABELGRP.lsp
>>> LOAD: Could not load file
>>> #P"/usr/pkg/lib/open-axiom/i386--netbsdelf/1.3.0-2008-08-19/algebra/exposed.fas"
>>> (Error:
>>> "/usr/pkg/lib/open-axiom/i386--netbsdelf/1.3.0-2008-08-19/algebra/exposed.fas:
>>> unrecognized file format")
>>> Broken at SI:TOP-LEVEL.No restarts available.
>>> Top level.
>>> BOOT>
>>>
>>> Still no luck. The build stucks, it doesn't progress for half a day already.
>>
>> Bummer. Now, I need a third machine where I can reproduce this.
>> On all of my 6 machines (including the CentOS), I cannot reproduce
>> this. The above failure seems to come from the fact that system is
>> trying to access nor yet installed file -- exposed.fas. And it actually
>> does not need that file in order to compile Lisp programs.
>>
>> Many thanks for the report.
>> I now consider ECL voodoo-driven.
>
> From what I see, this is common "build-not-install & install-not-build":
> "/usr/pkg" is PREFIX, DESTDIR is defined to a value like
> "/var/tmp/.../work/.destdir"
> Thus it wants to use a file from ${PREFIX} during build, when
> ${PREFIX} is protected from write. (${DESTDIR} should be too,
> but it is safer, it is sufficient to merely check for it being empty.)
What puzzles me is that it ever tries to use ${PREFIX}. The reason it should
not is that the file it is looking for is in a directory specified as
the argument to
--sysalg= above. This is a key distinction of OpenAxiom from other
AXIOM systems:
It is capable of operating solely based on the values supplied as arguments
to the system invokation. I hope the last commit I dud cures the issue.
When OpenAxiom is built on the openSUSE build farm, it uses similar protection
as you use above above by setting ${DESTDIR} non-empty.
Many thanks for your feedback.
-- Gaby
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
open-axiom-devel mailing list
open-axiom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
