Cinnamon 2.x porting

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
roelof
Samurai
Samurai
Posts: 112
Joined: 06 Aug 2013, 15:32
Distribution: Porteus 2.1 Gnome
Location: Netherlands

Re: Cinnamon 2.x porting

Post#16 by roelof » 27 Oct 2013, 12:47

I did all the steps of that tutorial again and now I see this :

Code: Select all

tmp
/tmp/cinnamon-2.x
/tmp/cinnamon-2.x/bin
/tmp/cinnamon-2.x/bin/gnome-autogen.sh
/tmp/cinnamon-2.x/bin/gnome-doc-common
/tmp/cinnamon-2.x/share
/tmp/cinnamon-2.x/share/aclocal
/tmp/cinnamon-2.x/share/aclocal/gnome-code-coverage.m4
/tmp/cinnamon-2.x/share/aclocal/gnome-common.m4
/tmp/cinnamon-2.x/share/aclocal/gnome-compiler-flags.m4
/tmp/cinnamon-2.x/share/gnome-common
/tmp/cinnamon-2.x/share/gnome-common/data
/tmp/cinnamon-2.x/share/gnome-common/data/omf.make
/tmp/cinnamon-2.x/share/gnome-common/data/xmldocs.make
How can I make a module which don't begin with tmp/cinnamon-2.x otherwise I cannot use it into my real system.

Roelof

Edit 1 :

I tried this commands
1) dir2xzm $TMP $PKG.xz
2) dir2xzm /tmp/cinnamon-2.x/ /tmp/cinnamon.xzm

User avatar
brokenman
Site Admin
Site Admin
Posts: 5657
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Cinnamon 2.x porting

Post#17 by brokenman » 27 Oct 2013, 13:39

./configure --prefix=/tmp
In my instructions I asked you to compile with: ./configure --prefix=/usr
How do i become super user?
Wear your underpants on the outside and put on a cape.

roelof
Samurai
Samurai
Posts: 112
Joined: 06 Aug 2013, 15:32
Distribution: Porteus 2.1 Gnome
Location: Netherlands

Re: Cinnamon 2.x porting

Post#18 by roelof » 27 Oct 2013, 13:41

Correct, but the tutorial says that I use : ./configure --prefix=/$TMP so everything gets installed into the made tmp directory.

Roelof

User avatar
brokenman
Site Admin
Site Admin
Posts: 5657
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Cinnamon 2.x porting

Post#19 by brokenman » 27 Oct 2013, 13:45

From the tutorial you are reading: http://www.porteus.org/tutorials/9-modu ... ource.html
If you get no output from this then reconfigure using:
# ./configure --prefix=$TMP


This document needs updating. The script configure-for-Porteus doesn't exist. Perhaps it used to but not anymore. Our documents man is absent at the moment so I will update this now. Sorry if you've wasted any time because of this misinformation. Always configure with --prefix=/usr in Porteus. If you compile to /tmp then you could get linked libraries looking in the wrong place.
How do i become super user?
Wear your underpants on the outside and put on a cape.

roelof
Samurai
Samurai
Posts: 112
Joined: 06 Aug 2013, 15:32
Distribution: Porteus 2.1 Gnome
Location: Netherlands

Re: Cinnamon 2.x porting

Post#20 by roelof » 27 Oct 2013, 13:53

Thanks,

I did these steps and now gnome-autogen,sh is being found.
Finally I can try to make cjs as a module.

Roelof
Last edited by roelof on 27 Oct 2013, 14:01, edited 1 time in total.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5657
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Cinnamon 2.x porting

Post#21 by brokenman » 27 Oct 2013, 14:01

Updated the document. Fanthom wrote a very useful script that I use everyday. /opt/porteus-scripts/changes-time

When you run this script it finds all files that were updated in the last 3 minutes (or whatever time you specify). This can be useful when a Makefile contains no DESTDIR variable. Sometimes you can just run make install and then run this script and it will copy all the changed files on your system into /root/chanegesXXXX. It is not 100% foolproof (it relies on timestamps) but most of the times it works for me.
How do i become super user?
Wear your underpants on the outside and put on a cape.

roelof
Samurai
Samurai
Posts: 112
Joined: 06 Aug 2013, 15:32
Distribution: Porteus 2.1 Gnome
Location: Netherlands

Re: Cinnamon 2.x porting

Post#22 by roelof » 27 Oct 2013, 14:04

Thanks,

But I see here (http://www.porteus.org/tutorials/9-modu ... ource.html) still the old page.

Roelof

roelof
Samurai
Samurai
Posts: 112
Joined: 06 Aug 2013, 15:32
Distribution: Porteus 2.1 Gnome
Location: Netherlands

Re: Cinnamon 2.x porting

Post#23 by roelof » 27 Oct 2013, 17:08

Hello,

For cjs I need to compile nspr.
So I downloaded the lastest version.
Unpacked it.
Then I do ./configure --prefix=/usr --libdir=/usr/lib/ --includedir=/usr/include/nspr --disable-multilib
and after that make

And I see this message :

Code: Select all

make -C config export
make[1]: Entering directory `/home/guest/Downloads/nspr-4.9.6/mozilla/nsprpub/config'
gcc -m32 -o now.o -c      -Wall -g -fno-inline -fPIC  -UNDEBUG -DDEBUG_guest  -DDEBUG=1 -DHAVE_VISIBILITY_HIDDEN_ATTRIBUTE=1 -DHAVE_VISIBILITY_PRAGMA=1 -DXP_UNIX=1 -D_GNU_SOURCE=1 -DHAVE_FCNTL_FILE_LOCKING=1 -DLINUX=1 -Di386=1 -D_REENTRANT=1  -DFORCE_PR_LOG -D_PR_PTHREADS -UHAVE_CVAR_BUILT_ON_SEM   now.c
In file included from /usr/include/features.h:382:0,
                 from /usr/include/stdio.h:28,
                 from now.c:6:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
compilation terminated.
make[1]: *** [now.o] Error 1
make[1]: Leaving directory `/home/guest/Downloads/nspr-4.9.6/mozilla/nsprpub/config'
make: *** [export] Error 2
According to google the --disable-multilib schould avoid this error.
Anyone a idea how to solve this ?

Roelof

User avatar
brokenman
Site Admin
Site Admin
Posts: 5657
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Cinnamon 2.x porting

Post#24 by brokenman » 27 Oct 2013, 18:29

Before going any further please answer the following questions:

1. Are you compiling on 32 or 64bit?
2. Do you have the Porteus development module installed?
3. Have you updated any core packages?
4. Have you tried the slackware 14.0 version of nspr?

Downloading the latest version of every missing package you find could get you into trouble later since you are compiling on a slackware 14.0 based system.
How do i become super user?
Wear your underpants on the outside and put on a cape.

roelof
Samurai
Samurai
Posts: 112
Joined: 06 Aug 2013, 15:32
Distribution: Porteus 2.1 Gnome
Location: Netherlands

Re: Cinnamon 2.x porting

Post#25 by roelof » 27 Oct 2013, 18:33

1. Are you compiling on 32 or 64bit?

64bit

2. Do you have the Porteus development module installed?

Not that I know. Can I do that by using ppm ?

3. Have you updated any core packages?

Nope, I only made cjs , and ms185 and nspr

4. Have you tried the slackware 14.0 version of nspr?

No, Is there a manual how I can add these to my own module.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5657
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Cinnamon 2.x porting

Post#26 by brokenman » 27 Oct 2013, 18:40

1. Are you compiling on 32 or 64bit?
64bit

Then your --libdir is incorrect. It should be lib64. Leave it out of ./configure as it will automatically know.

2. Do you have the Porteus development module installed?
Not that I know. Can I do that by using ppm ?

http://dl3.porteus.org/x86_64/current/m ... -devel.xzm

Nope, I only made cjs , and ms185 and nspr
I assume you mean js185

4. Have you tried the slackware 14.0 version of nspr?
No, Is there a manual how I can add these to my own module.

slackyd -u ## update slackyd
slackyd -s nspr ## Search for nspr
slackyd -g nspr-0.0.0 ## Get nspr

It will be downloaded to /var/slackyd and you can convert it into a module or install the slackware package.
To install the slackware package: installpkg /var/slackyd/nspr*
To convert the package to a module: txz2xzm /var/slackyd/nspr* /tmp/nspr.xzm
How do i become super user?
Wear your underpants on the outside and put on a cape.

roelof
Samurai
Samurai
Posts: 112
Joined: 06 Aug 2013, 15:32
Distribution: Porteus 2.1 Gnome
Location: Netherlands

Re: Cinnamon 2.x porting

Post#27 by roelof » 27 Oct 2013, 18:50

Thanks,

What i mean is how can I add it to my own cinnamon-2.0.6 module.
Do I have to unpack the module into my own /tmp/cinnamom-2.0.6 directory.

Roelof

User avatar
brokenman
Site Admin
Site Admin
Posts: 5657
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Cinnamon 2.x porting

Post#28 by brokenman » 27 Oct 2013, 19:06

The easiest way to compile and get it working is to boot Porteus without using any changes= cheatcode. All packages you download or compile should be made into modules and placed in your porteus/modules directory or create the folder in porteus/optional/devmods and then boot with the cheatcode load=devmods. This way when you screw up, you can just reboot and everything will be reset to normal. When you are happy and have everything (cinnamon) running as you like, you can then create a single module by unpacking all the modules into a single directory, removing all the unnecessary stuff and creating a module from it.

Dumping everything you compile/download into /tmp/cinnamom-2.0.6 and creating a single giant module each time you want to test is a bad idea for many many reasons.
How do i become super user?
Wear your underpants on the outside and put on a cape.

roelof
Samurai
Samurai
Posts: 112
Joined: 06 Aug 2013, 15:32
Distribution: Porteus 2.1 Gnome
Location: Netherlands

Re: Cinnamon 2.x porting

Post#29 by roelof » 27 Oct 2013, 19:22

oke,

That's a very clear idea of a workflow.
I will try it and hopefully I will succeed in the next weeks.
If I succeed I will make it public so more people can enjoy it.

Roelof

roelof
Samurai
Samurai
Posts: 112
Joined: 06 Aug 2013, 15:32
Distribution: Porteus 2.1 Gnome
Location: Netherlands

Re: Cinnamon 2.x porting

Post#30 by roelof » 29 Oct 2013, 13:48

Hello,

I now succeed in making 2 of the 10 modules ready.
But when I activate it I see this message :

Code: Select all

Updating shared library links:  /sbin/ldconfig
Updating glib schemas: /usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas
warning: Schema 'apps.gecko-mediaplayer.preferences' has path '/apps/gecko-mediaplayer/preferences/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'apps.gnome-mplayer.preferences' has path '/apps/gnome-mplayer/preferences/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.crypto.cache' has path '/desktop/gnome/crypto/cache/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.crypto.pgp' has path '/desktop/gnome/crypto/pgp/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.dns_sd' has path '/system/dns-sd/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.locale' has path '/system/locale/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy' has path '/system/proxy/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy.http' has path '/system/proxy/http/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy.https' has path '/system/proxy/https/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy.ftp' has path '/system/proxy/ftp/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy.socks' has path '/system/proxy/socks/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.smb' has path '/system/smb/'.  Paths starting with '/apps/', '/deskt
[code]

Do I need to solve this one and how do I do this ?
Or is this harmless ?

Roelof

Post Reply