[scribus] Idiot wants to build 1.5.0 from source
John Jason Jordan
johnxj at comcast.net
Wed Jun 22 16:02:04 UTC 2011
On Wed, 22 Jun 2011 17:51:03 +1000
"Owen" <rcook at pcug.org.au> dijo:
>> Looking at /usr/local/scribus_svn/bin/ there is an executable with
>> the name "scribus." Launching it starts Scribus 1.3.9. Its
>> properties says it is owned by root. Launching it from the command
>> line as root gives me:
>>
>> [root at Devil8 bin]# scribus
>> No protocol specified
>> scribus: cannot connect to X server :0.0
>You cannot start an executable from within the "bin" directory that
>way.
>
>You must do # ./scribus
>
>better still, get out of that directory and run
>/usr/local/bin/scribus_svn , or see below, just # scribus
>
>I suggest you try this:
>
># env|grep PATH
>
>It will produce something like;
>
>PATH=/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/local/sbin:/usr/sbin:/sbin:/home/owen/bin
>
>This means that if you issue the command 'scibus', it will first
>search /usr/local/bin (but not if you are in it), then /usr/bin where
>I bet your scribus-1.3.9 is living
OK, you are correct. There are exactly two executable files named
"scribus" on this computer:
/usr/bin/scribus
/usr/local/scribus_svn/bin/scribus
My user path is:
[jjj at Devil8 bin]$ env|grep PATH
PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/real/RealPlayer:/home/jjj/bin:/opt/real/RealPlayer
Using Nautilus, if I double click on /usr/bin/scribus it launches
1.3.9, as expected. If I double click
on /usr/local/scribus_svn/bin/scribus nothing happens.
Using Alacarte I created a launcher for Scribus 1.5.0 specifying the
full path and executable. But when I launch it nothing happens, the
same as double clicking on the executable in Nautilus. Of course, the
GUI may not be giving me the error messages.
From the command line I get:
[jjj at Devil8 bin]$ cd ~/
[jjj at Devil8 ~]$ ./usr/local/scribus_svn/bin/scribus
bash: ./usr/local/scribus_svn/bin/scribus: No such file or directory
[jjj at Devil8 ~]$ cd /usr/local/scribus_svn/bin/
[jjj at Devil8 bin]$ ./scribus
Segmentation fault (core dumped)
[jjj at Devil8 bin]$
Or as root (even though I take to heart the advice that this is not a
good idea);
[root at Devil8 bin]# cd /
[root at Devil8 /]# ./usr/local/scribus_svn/bin/scribus
No protocol specified
scribus: cannot connect to X server :0.0
[root at Devil8 /]# cd /usr/local/scribus_svn/bin/
[root at Devil8 bin]# ./scribus
No protocol specified
scribus: cannot connect to X server :0.0
The root errors are no doubt caused (as mentioned here) by the fact
that root cannot connect to X which is being run as jjj.
This error message is the troubling one:
Segmentation fault (core dumped)
At this point it appears that something seriously bad happened to my
build of last night. It could be a problem with something the developers
added recently, but it's far more likely that I just didn't build it
correctly.
These are the exact commands I used:
mkdir ~/Software/Scribus/src/
mkdir ~/Software/Scribus/src/scribus_svn
mkdir /usr/local/scribus_svn
cd ~/Software/Scribus/src/scribus_svn
svn co svn://scribus.net/trunk/Scribus
cd ./Scribus
cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr/local/scribus_svn
make
make install
Note that I deleted the "sudos" from the commands on the web page
because I ran the whole thing as root. Now I am going to do it over as
jjj (adding back the two sudos). I'm going to start by nuking the
~/Software/Scribus folder and the /usr/local/scribus_svn folder, just
to make sure everything is clean to start over with. A couple hours
from now I will follow up with a report on the results.
More information about the scribus
mailing list