It compiled without error. Thanks for help and suggestion.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@goog
On Sunday, October 21, 2012 10:45:24 PM UTC+1, Jeroen Demeyer wrote:
> One problem is that extracting tarballs is inherently dangerous. The
> user who happens to have UID 1237 is able to root the system because of
> this. I'm not sure what to do here...
>
It might be a good idea to untar --n
On 2012-10-21 23:01, Volker Braun wrote:
> He's clearly building as root. While not a great idea, I don't like the
> that the Sage install then dies with an obscure error. If you want to
> compile stuff as root you should be allowed to.
One problem is that extracting tarballs is inherently dangerou
I will try building without being root, although I think I tried that
initially and got the same error.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this gro
I did try building without being root, but I got the same error. After the
initial attempt I deleted the folder that I got from the tarball and tried
anew.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sag
I did try building without being root, but I got the same error. So I
deleted the folder and unzipped the tarball again. I thought, "Maybe, if I
log in as root, the error will go away."
On Sunday, October 21, 2012 2:01:14 PM UTC-7, Volker Braun wrote:
>
> He's clearly building as root. While
He's clearly building as root. While not a great idea, I don't like the
that the Sage install then dies with an obscure error. If you want to
compile stuff as root you should be allowed to.
On Sunday, October 21, 2012 9:27:58 PM UTC+1, Jeroen Demeyer wrote:
>
> On 2012-10-21 21:49, miguel wrote
I built as root. (Trying 'make' as root produces the setuptools error.)
Sorry, this is that output of the commands you gave:
root@Paloma:/sage-5.4.rc2# ls -al
/sage-5.4.rc2/spkg/build/setuptools-0.6.16.p0/src
total 224
drwxr-xr-x 6 1237 1237 4096 Oct 21 13:42 .
drwxr-xr-x 5 1237 1237 4096 M
On 2012-10-21 21:49, miguel wrote:
> $ id -a
> uid=1000(miguel) gid=1000(miguel)
> groups=1000(miguel),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lpadmin),123(sambashare)
Is this the user you used to build Sage, or did you build as root?
--
You received this message because you are subscri
$ ls -al /sage-5.4.rc2/spkg/build/setuptools-0.6.16.p0/src
total 224
drwxr-xr-x 6 1237 1237 4096 Oct 21 12:07 .
drwxr-xr-x 5 1237 1237 4096 May 14 05:50 ..
-rw-r--r-- 1 1237 1237 9265 May 20 2011 CHANGES.txt
-rw-r--r-- 1 1237 1237 412 May 20 2011 CONTRIBUTORS.txt
-rw-r--r-- 1 1237 1237 62
On 2012-10-21 21:17, miguel wrote:
> The link to ubuntuforums did reveal what was happening!
>
> I have tried to compile 5.4rc2, and upon getting
> to setuptools-0.6.16.p0.spkg, I get the following error:
>
> patching file setuptools/command/easy_install.py
>
> sys:1: RuntimeWarning: no
The link to ubuntuforums did reveal what was happening!
I have tried to compile 5.4rc2, and upon getting
to setuptools-0.6.16.p0.spkg, I get the following error:
patching file setuptools/command/easy_install.py
> sys:1: RuntimeWarning: not adding directory
>> '/sage-5.4.rc2/spkg/build/setupto
Does this solve your problem? (found by googling "bits/predef")
http://askubuntu.com/questions/82510/gcc-no-longer-works-after-upgrade
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.co
13 matches
Mail list logo
