[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Axiom-developer] address@hidden: Re: Installing axiom on suse linux 10.

From: root
Subject: [Axiom-developer] address@hidden: Re: Installing axiom on suse linux 10.2]
Date: Wed, 3 Oct 2007 22:14:18 -0400


GCL seems to have built on Suse 10.2 and the system command works.
The GCC compiler appears to be in the path. Yet it appears that
GCL cannot execute it. CC1 seems to be looking in the wrong place
for the .h files. Do you have any insight into this?


------- Start of forwarded message -------
Content-Type: text/plain;
  charset="CP 1253"
From: "C. Frangos" <address@hidden>
Reply-To: address@hidden
To: address@hidden
Subject: Re: Installing axiom on suse linux 10.2
Date: Wed, 3 Oct 2007 23:00:10 +0200
In-Reply-To: <address@hidden>

I tried  the instructions and it seems that the )sys command is 

I use this command to delete foo1, and call gcc in order to compile one of my 
C programs located in another directory (see below).

It seems that gcc is on the path, but I dont recall the linux command to 
explicitly check this.


C. Frangos.

(1) -> )sys rm /home/cfrangos/temp/foo1                    
(1) -> )sys gcc -o test1 /home/cfrangos/src/agvs1.c -lm -O3
(1) -> 

>(1) -> )fin
>BOOT>(defun foo (x) x)
>BOOT>(compile 'foo)
>cc1: error: /root/axiom/mnt/fedora5/bin/../h: Permission denied
>Error: (SYSTEM "gcc -c -Wall -DVOL=volatile -fsigned-char -pipe  
>-I/root/axiom/mnt/fedora5/bin/../h  -O3 -fomit-frame-pointer -c 
>\"/tmp/gazonk5.c\" -o \"/tmp/gazonk5.o\" -w") returned a non-zero value 0.
>Fast links are on: do (si::use-fast-links nil) for debugging
>Error signalled by UNLESS.
>Broken at APPLY.  Type :H for Help.
>BOOT>>(foo 3)
>On Wednesday 03 October 2007 21:49, you wrote:
>> right. the (foo 3) is interpreted.
>> the compile step is failing.
>> somehow axiom (actually gcl) cannot find the gcc command.
>> is gcc on your path?
>> or possibly the "system" command does not work.
>> create a junk file like /tmp/foo by doing "touch /tmp/foo"
>> start axiom
>> type
>>   )sys rm /tmp/foo
>> and see if the file is erased.
>> If the file is erased then the system command works and
>> the problem is that gcc cannot be found. If the file is
>> not erased then the system function is not working and
>> we have to get Camm (the GCL maintainer) involved.
>> Tim
------- End of forwarded message -------

reply via email to

[Prev in Thread] Current Thread [Next in Thread]