Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 15 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 10 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 19 hrs ago - more...
| The Following 10 Users Say Thank You to pali For This Useful Post: | ||
|
2013-04-19
, 11:46
|
|
Posts: 839 |
Thanked: 3,386 times |
Joined on Mar 2009
|
#63
|
1029 packages from squeeze. And now I started packages from Wheezy (repo opened for it, check opening post).
----
I have problem. Wheezy installs (some) libraries to the
/lib/arm-linux-gnueabi/
and
/usr/lib/arm-linux-gnueabi/
I have then added LD_LIBRARY_PATH=/lib/arm-linux-gnueabi/:/usr/lib/arm-linux-gnueabi/ and I can use them.
But during debian packaging it is not using LD_LIBRARY_PATH . I tried to tune /scratchbox/compilers/linaro-4.7-2012.07-fremantle-armv7a/gcc.specs
I added
And for some packages it works, but not all. So I'm thinking this is still wrong way. I have one example: during compiling wget (configure) it runs:
And error is
When I then modify line, it found needed libraries:
What will be the correct (and/or cleanest) way to handle this?
----
I have problem. Wheezy installs (some) libraries to the
/lib/arm-linux-gnueabi/
and
/usr/lib/arm-linux-gnueabi/
I have then added LD_LIBRARY_PATH=/lib/arm-linux-gnueabi/:/usr/lib/arm-linux-gnueabi/ and I can use them.
But during debian packaging it is not using LD_LIBRARY_PATH . I tried to tune /scratchbox/compilers/linaro-4.7-2012.07-fremantle-armv7a/gcc.specs
I added
Code:
*link_libgcc: %D -L/usr/lib/arm-linux-gnueabi -L/lib/arm-linux-gnueabi/
Code:
gcc -o conftest -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DNO_SSLv2 -D_FILE_OFFSET_BITS=64 -g -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -L/usr/lib/arm-linux-gnueabi conftest.c /usr/lib/libgnutls.so -lgcrypt -lgpg-error -lz
Code:
/scratchbox/compilers/linaro-4.7-2012.07-fremantle-armv7a/bin/../lib/gcc/arm-none-linux-gnueabi/4.7.2/../../../../arm-none-linux-gnueabi/bin/ld: warning: libtasn1.so.3, needed by /usr/lib/libgnutls.so, not found (try using -rpath or -rpath-link)
Code:
gcc -o conftest -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DNO_SSLv2 -D_FILE_OFFSET_BITS=64 -g -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-rpath -Wl,/usr/lib/arm-linux-gnueabi conftest.c /usr/lib/libgnutls.so -lgcrypt -lgpg-error -lz
|
|
2013-04-19
, 13:52
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#65
|
Originally Posted by AapoRantalainen
Set LD_LIBRARY_PATH correctly in /etc/ld.so.conf* files which configure dynamic linker
1029 packages from squeeze. And now I started packages from Wheezy (repo opened for it, check opening post).
----
I have problem. Wheezy installs (some) libraries to the
/lib/arm-linux-gnueabi/
and
/usr/lib/arm-linux-gnueabi/
I have then added LD_LIBRARY_PATH=/lib/arm-linux-gnueabi/:/usr/lib/arm-linux-gnueabi/ and I can use them.
But during debian packaging it is not using LD_LIBRARY_PATH .
| The Following 6 Users Say Thank You to pali For This Useful Post: | ||
|
|
2013-04-28
, 06:49
|
|
Posts: 6 |
Thanked: 17 times |
Joined on Jun 2010
|
#66
|
maybe I'm missing something, but why recompile? starting with wheezy debian offers an armhf port (thumb-enabled), which runs just fine on n900... the obvious problems are hardware support in the debian kernel.
| The Following 4 Users Say Thank You to wirr For This Useful Post: | ||
|
|
2013-05-04
, 12:41
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#67
|
el and hf are abi incompatible iirc. closed source components would therefore pose some issues. wheezy should support multiarch but not sure how it would be in terms of data interchange between the two.
edit: explains it a bit better http://www.memetic.org/raspbian-benc...rmel-vs-armhf/
Last edited by Android_808; 2013-05-04 at 12:54.
edit: explains it a bit better http://www.memetic.org/raspbian-benc...rmel-vs-armhf/
Last edited by Android_808; 2013-05-04 at 12:54.
 |
|
2013-06-13
, 21:49
|
|
Posts: 148 |
Thanked: 216 times |
Joined on Jul 2010
@ Yerevan
|
#68
|
would like to say that I love the idea and effort.
also, by having free maemo we will be able to run it not only on n900 but on any hardware we could find kernel sources. geek phones, nexuses, gta-04 phones, etc.
because hardware dies, so is any n900 will die some day, but ideas - not - and software which is maintained can live in different bodies.
I would like to have a gta-04 tablet with your maemo like system.
also, by having free maemo we will be able to run it not only on n900 but on any hardware we could find kernel sources. geek phones, nexuses, gta-04 phones, etc.
because hardware dies, so is any n900 will die some day, but ideas - not - and software which is maintained can live in different bodies.
I would like to have a gta-04 tablet with your maemo like system.
| The Following 3 Users Say Thank You to norayr For This Useful Post: | ||
|
|
2013-06-14
, 07:27
|
|
Posts: 839 |
Thanked: 3,386 times |
Joined on Mar 2009
|
#69
|
Originally Posted by wirr
Firstly: We suppose that pure Debian (as it) is not truly working on N900.
maybe I'm missing something, but why recompile?
Some packages from debian can be installed top of Maemo5 and they will work. But some packages can't be installed, because they depends different version of libraries. And some packages can be installed, but they are not working. I don't have list or numbers how many of them will fail.
-----
Now I'm building packages from Wheezy, so far over 800 packages (check first post). I haven't had spare device to test them on real device and they can't be easily installed via apt-get, because maemo's apt-get is too old for that server. I'm starting device testing on (hopefully) next week,.
Packages are compiled against:
libc6: 2.10.90-maemo1
libglib2.0-0: 2.35.3-0maemo3
libstdc++6: 4.7.2-0+cssu0
|
|
2013-08-20
, 18:19
|
|
Posts: 172 |
Thanked: 170 times |
Joined on Jan 2010
@ Sweden
|
#70
|
You might already know about this, but I thought I would mention in case it can help you. Back in 2010 there was a wiki Brainstorm to check what could be done in stead of optification (in those days optification worked very poorly):
http://maemo.org/community/brainstor...on_in_the_n900
As we all know, we ended up in optification anyway, but the brainstorm got some good ideas, also the tmo-thread (linked from the Brainstorm) had many interesting ideas. Might be worth a look.
BTW, I think your project is marvelous, and exactly what I wish Maemo/MeeGo was from the start! Imagine if we had had a Debian compatible distro with all the phone specific packages back in 2009! It could have given Android a run for its money! Especially if it was binary compatible with Debian - that would have been a phone with a slick interface where all Debian packages could be installed... This whole convergence bruhaha from Canonical would have been achieved already then! :-)
Anyway, I still want this on my N900!
http://maemo.org/community/brainstor...on_in_the_n900
As we all know, we ended up in optification anyway, but the brainstorm got some good ideas, also the tmo-thread (linked from the Brainstorm) had many interesting ideas. Might be worth a look.
BTW, I think your project is marvelous, and exactly what I wish Maemo/MeeGo was from the start! Imagine if we had had a Debian compatible distro with all the phone specific packages back in 2009! It could have given Android a run for its money! Especially if it was binary compatible with Debian - that would have been a phone with a slick interface where all Debian packages could be installed... This whole convergence bruhaha from Canonical would have been achieved already then! :-)
Anyway, I still want this on my N900!
http://elinux.org/N900