Sugar on Ubuntu: Difference between revisions
Jump to navigation
Jump to search
(fix typos, spacing and capitalization of "Edgy" to be consistant with the rest of the doc) |
mNo edit summary |
||
(112 intermediate revisions by 58 users not shown) | |||
Line 1: | Line 1: | ||
{{jhbuild-nav}} |
|||
The easiest way to install [[Sugar]] on Ubuntu is to use [[Sugar with sugar-jhbuild|Sugar-jhbuild]]. The instructions on this page are for [[Ubuntu]] 6.10 "Edgy Eft" on x86 (building seems to be currently broken on x86_64). |
|||
== |
== Page moved to Sugar Labs == |
||
You need a number of packages from the Ubuntu repositories. Some of these packages are not available for the stock Ubuntu install, and you will need to enable the ''universe'' and ''multiverse'' repositories. (You can do this by either using the Synaptic Package Manager, or simply editing /etc/apt/sources.list, but don't forget to reload afterwards.) |
|||
Dapper/Edgy |
|||
<pre> |
|||
sudo apt-get install build-essential cvs docbook-utils subversion libgtk2.0-dev libidl-dev \ |
|||
gnome-common gtk-doc-tools libxt-dev automake1.7 automake1.8 automake1.9 python-gtk2-dev \ |
|||
python-avahi git-core cogito python-dev avahi-utils \ |
|||
libgconf2-dev xserver-xephyr libgnome2-dev libmatchbox-dev python-cairo-dev \ |
|||
libtiff4-dev python-gnome2-dev libxdamage-dev libxdamage1 libxcomposite-dev \ |
|||
libgnomeui-dev libtool libfribidi-dev libgsf-1-dev libbz2-dev libwmf-dev \ |
|||
libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev libgnomeprintui2.2-dev \ |
|||
libenchant-dev libnspr-dev darcs libxslt1.1 libxslt1-dev firefox firefox-dev \ |
|||
libasound2-dev sqlite3 libsqlite3-dev libssl-dev libncurses5-dev \ |
|||
bison flex libtheora-dev libtheora-bin |
|||
</pre> |
|||
Feisty |
|||
<pre> |
|||
sudo aptitude install libloudmouth1-0 libloudmouth1-dev libdbus-glib-1-2 \ |
|||
libdbus-glib-1-dev darcs libsqlite3-dev libtheora-dev libxml2-utils |
|||
</pre> |
|||
Even with the universe and multiverse enabled you can have some problems installing these packages. |
|||
You can fix them using the sources.list generator that you can find on [http://www.ubuntu-nl.org/source-o-matic/ www.ubuntu-nl.org]. |
|||
There may be more packages required; if you find any more, please append them to this list. |
|||
<pre>Note:I needed to install libgnomeui-dev version 2.16.1, libgnomeuimm-2.6-1c2a, and |
|||
libgnomeuimm-2.6-dev. I no longer get the error "package libgnomeui-2.0 cannot be found" |
|||
however I still encounter other errors [chundevi]</pre> |
|||
<pre>I was building an Edgy-based VM from a debootstrap base and using Edgy packages. I needed to install librsvg2-common before sugar would run.</pre> |
|||
Note: If you get the error "package python-avahi not available" try this- |
|||
<pre>On PPC, I used the following command: sudo apt-get install build-essential cvs docbook-utils subversion libgtk2.0-dev libidl-dev \ |
|||
gnome-common gtk-doc-tools libxt-dev automake1.7 automake1.8 automake1.9 python-gtk2-dev git-core python-dev libgconf2-dev libgnome2-dev \ |
|||
python-cairo-dev libtiff4-dev python-gnome2-dev libxdamage-dev libxdamage1 libxcomposite-dev libgnomeui-dev libtool libfribidi-dev \ |
|||
libgsf-1-dev libbz2-dev libwmf-dev libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev libgnomeprintui2.2-dev libenchant-dev |
|||
~~~~ |
|||
</pre> |
|||
Then you must ensure that the Avahi daemon is enabled and running. Execute: |
|||
<pre>sudo vim /etc/default/avahi-daemon</pre> |
|||
and ensure the directive "AVAHI_DAEMON_START" is set to 1. Then execute: |
|||
<pre>sudo /etc/init.d/avahi-daemon start</pre> |
|||
-------- |
|||
[[User:SRiggins|SRiggins]]: |
|||
I had to do a lot of work with the help of many to get Ubuntu Edgy to run Sugar. First off, you have to use the universe for apt-get, which you do by editing: |
|||
<pre>sudo pico /etc/apt/sources.list</pre> |
|||
and uncommenting the two entries for universe. |
|||
Then do the large apt-get at the top, and if there are still any missing packages, remove them from the list and try again. |
|||
Next, I installed Nework Manager, as mentioned on this page, but that broke all networking in Parallels, so I uninstalled it and the XO team fixed the build to not require it. |
|||
next, I ran these commands: |
|||
<pre> |
|||
sudo apt-get install libssl-dev libncurses5-dev |
|||
./sugar-jhbuild buildone -a loudmouth |
|||
./sugar-jhbuild buildone -a telepathy-gabble |
|||
./sugar-jhbuild buildone -a telepathy-python |
|||
./sugar-jhbuild buildone -a artwork |
|||
./sugar-jhbuild buildone -a sugar |
|||
</pre> |
|||
== Using Sugar-jhbuild == |
|||
Use of Sugar-jhbuild is detailed on [[Sugar_with_sugar-jhbuild|building Sugar from sources]]. To summarize those instructions: |
|||
git-clone git://dev.laptop.org/sugar-jhbuild |
|||
cd sugar-jhbuild |
|||
./sugar-jhbuild |
|||
If you had already checked out sugar-jhbuild previously, make sure your copy is up-to-date before building: |
|||
cd sugar-jhbuild |
|||
git pull |
|||
== Troubleshooting == |
|||
=== automake version mismatch === |
|||
The following solution also applies in other situations. I ran into it when attempting: |
|||
./sugar-jhbuild build-base |
|||
make died while building fontconfig on a Ubuntu Dapper box with a missing separator error. |
|||
During the building task you may get the following error: |
|||
error during stage configure of matchbox-window-manager:....[9/12] |
|||
This error happens because Ubuntu uses the automake 1.4 version in contrast with matchbox-window-manager which uses the automake 1.9 version. In order to bypass this error you can execute the following command: |
|||
sudo update-alternatives --config automake |
|||
You will get the following list with the asterisk being at the 1 selection |
|||
There are 3 alternatives which provide `automake'. |
|||
Selection Alternative |
|||
+ 1 /usr/bin/automake-1.4 |
|||
2 /usr/bin/automake-1.7 |
|||
* 3 /usr/bin/automake-1.9 |
|||
Press enter to keep the default[*], or type selection number: |
|||
Here you should press the button 3 and the try again to build sugar. |
|||
=== Mozilla Build Error === |
|||
You may get stuck at a Mozilla build error - I did on Edgy AMD64. Two ways to resolve the problem, either: |
|||
sudo aptitude install libxul-dev |
|||
which may not work, or copy the Mozilla or Firefox .pc files in /usr/lib/pkgconfig to xulrunner-*.pc files (You may only need to create xulrunner-gtkmozembed.pc and not the rest...). Either way, then, build with ./sugar-jhbuild build -s mozilla to skip building Mozilla from source. I have not yet completed a full Sugar build, though, so these instructions may just be masking a problem. --RP |
|||
=== Building libabiword === |
|||
If you get an error like |
|||
<pre> |
|||
*** Building libabiword *** [24/35] |
|||
<...> |
|||
I can't seem to figure out which platform you are using. |
|||
You should probably try using the autoconfiscated build system (rather |
|||
than this, the deprecated and unsupported diving make system) by running |
|||
configure (creating it with autogen.sh if need be) and using GNU Make. |
|||
Using configure is a requirement for all known platforms that aren't some form |
|||
of Windows, QNX Neutrino, or MacOS X. |
|||
</pre> |
|||
just choose the "configure" option. This error shows up (probably) because AbiWord has a regular Makefile setup for building on Windows in addition to AutoConf stuff for nearly every other platform, so it is just "faking out" jhbuild in all likelyhood. |
|||
=== git, the SCM === |
|||
On Ubuntu 6.06 Dapper Drake, git has been deprecated. You have to run the following command to get git to work properly. |
|||
sudo update-alternatives --config git |
|||
Select option #2: git-scm |
|||
=== network manager error === |
|||
If, after running <tt> ./sugar-jhbuild run</tt> you get the following error: |
|||
DBusException: Connection ":1.12" is not allowed to own |
|||
the service "org.freedesktop.NetworkManagerInfo" due to |
|||
security policies in the configuration file |
|||
you have two solutions |
|||
==== Method 1 : Install NetworkManager==== |
|||
You want to ensure that the NetworkManager is |
|||
* installed |
|||
sudo apt-get install network-manager |
|||
* reachable by console applications, in file <tt>/etc/dbus-1/system.d/NetworkManager.conf</tt> add |
|||
<allow own="org.freedesktop.NetworkManagerInfo"/> |
|||
after |
|||
<policy at_console="true"> |
|||
* started, by restarting the whole dbus |
|||
sudo /etc/init.d/dbus restart |
|||
==== Method 2 : Only provide .conf file ==== |
|||
Copy the [http://cvs.gnome.org/viewcvs/*checkout*/NetworkManager/gnome/applet/nm-applet.conf?rev=1.2 configuration file] to <tt>/etc/dbus-1/system.d</tt> . |
|||
Restart the dbus as above. |
|||
=== os.py not finding sugar-emulator folder === |
|||
The error message is: |
|||
./sugar-jhbuild run |
|||
Traceback (most recent call last): |
|||
File "./sugar-jhbuild", line 11, in ? |
|||
main.main(sys.argv[1:]) |
|||
File "/home/barbolo/Desktop/sugar/sugar-jhbuild/main.py", line 104, in main |
|||
jhbuild.commands.run(command, config, args) |
|||
File "/home/barbolo/Desktop/sugar/sugar-jhbuild/build-scripts/jhbuild/jhbuild/commands/__init__.py", line 74, in run |
|||
return cmd.execute(config, args) |
|||
File "/home/barbolo/Desktop/sugar/sugar-jhbuild/build-scripts/jhbuild/jhbuild/commands/base.py", line 238, in execute |
|||
os.execlp(args[0], *args) |
|||
File "/usr/lib/python2.4/os.py", line 324, in execlp |
|||
execvp(file, args) |
|||
File "/usr/lib/python2.4/os.py", line 341, in execvp |
|||
_execvpe(file, args) |
|||
File "/usr/lib/python2.4/os.py", line 379, in _execvpe |
|||
func(fullname, *argrest) |
|||
OSError: [Errno 2] No such file or directory |
|||
The solution: |
|||
Edit the archive sugar-jhbuild/main.py: |
|||
Change line 101: |
|||
args.append('sugar-emulator') |
|||
for |
|||
args.append('/home/barbolo/Desktop/sugar/sugar-jhbuild/source/sugar/sugar-emulator') |
|||
Note that /home/barbolo/Desktop/sugar is where my sugar-jhbuild folder is located, so you may change it! |
|||
== Testing sugar == |
|||
When using [[Sugar_with_sugar-jhbuild|sugar-jhbuild]], you can use: |
|||
./sugar-jhbuild run |
|||
If you want to run Sugar from the source tree enter in a jhbuild shell: |
|||
./sugar-jhbuild shell |
|||
Then use: |
|||
sugar-shell |
|||
'''This page has been [http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu moved] to the Sugar Labs wiki.''' |
|||
[[Category:Installing Sugar]] |
[[Category:Installing Sugar]] |
||
[[Category:Python]] |
Latest revision as of 18:49, 25 September 2010
Developer's Setup |
Fedora |
Ubuntu |
Debian |
Gentoo |
Slackware |
Wiki Category |
modify |
Page moved to Sugar Labs
This page has been moved to the Sugar Labs wiki.