![]() |
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
Quote:
Removing an unnecessary package dependency is like the least we can do! |
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
Quote:
Quote:
Quote:
See, the difference between gcc 4.2.1 and 4.7.2 is big, there are lots of changes and usually one needs to play a bit with compiler flags. the other VERY useful flag is -mword-relocations, use that if linker aborts with some cryptic error message. Every project is different, I don't think there is a way to write on wiki a full set of instructions. However, feel free to edit the page if you feel something should go there :) |
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
Quote:
|
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
>See, the difference between gcc 4.2.1 and 4.7.2 is big, there are lots of changes
>and usually one needs to play a bit with compiler flags. yes, i know that the difference is big. and while i have used gcc since... let me think... v2.95, i always was too lazy to study all it's options. not that i'm ranting, i just described what i found while installing the things. and yes, i'm actively using c99 (gnu99, to be honest). and sorry... i just forgot about it, it is natural as breathing. so yes, it's my bad with inlining and standards. thank you for clarification. btw, is there any need to use PIC code for ARM .so (except that relocations kills page sharing)? it's the first time i'm writing/porting something for ARM. >However, feel free to edit the page if you feel something should go there nope, i'm still new to scratchbox, and i'm not ready for building my own cross-compiling toolchain (it's not *that* hard to build gcc suite, but all that -dev .debs one need to compile reasonably big project for n900...). that's why i came to ask what i missed. thank you for your answers, i see some light now. %-) btw, is there any 'standard' flag in DEB_BUILD_OPTIONS (or something) that i can use to detect thumb2 builds? sure, i can check gcc version, but it looks like a dirty trick. and some of my projects (my build system is one of that) just can't be built with optimisations and pointer aliasing on gcc 4.2. if there will be some flag in DEB_BUILD_OPTIONS -- something like "thumb2", for example, i can easily check it in debian/rules and have automated builds for both 'arm' and 'thumb' for free. sure, i added such flag in my scratchbox config, but if it will be standardized some way, any developer can use it. %-) |
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
@ketmar: yep, there is, guess how it's called :p
example debian/rules snippet: Code:
ifneq (,$(findstring thumb,$(DEB_BUILD_OPTIONS))) BTW, be careful when building for non-thumb, this is enabled by default EDIT: Having executable pages shared is enough reason on n900(256MB RAM) for -fPIC |
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
Quote:
|
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
Quote:
Basically that's what I'm pushing for since quite some time. Original Nokia concept of one MetaPackage containing all was tailored to fit their idea of rolling out a complete system every once in a while, while same time Nokia doesn't need to care too much about proper dependencies - at least that's my humble guess. Now while maintaining stuff in CSSU, this MP more and more becomes an annoyance and a PITA. So while we noticed that, Merlin1991 and me thought about a way to overcome those problems. See this IRC meeting protocol for related info about making stuff optional. In CSSU we should strive to move more and more packages out of the MP blob and make them proper autonomous packages with a working set of dependencies. CSSU is "seamless" (as in your definition) regarding allowing user to benefit from bugfixes while not forcing any UI/UX changes on her/him. It however is "Community" (again in your definition) in trying to allow user more freedom of choice than original Nokia MP concept did. By no way we're going to replace Nokia's set of forced components and settings by our own deemed improved set that's similarly restrictive regarding freedom of choice. In your above example, ESD would need to become an optional (original Nokia-)package, while for example the new camera-ui would become an optional-alternative CSSU package, since it replaces the original Nokia package, introduces UX changes, and fremantle needs one of both, thus "-alternative". cheers jOERG |
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
hello, I just upgraded CSSU from 38-1Tmaemo5.1+thumb4 to 38-1Tmaemo6 (non-thumb it seems?), because I was assuming if I got an update pushed it would be thumb as well and didn't double-check the version number.
I'd like to keep running thumb though, is there an easy way to go back? Or will You make a thumb version of this update soon? Thanks, Ben |
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
Quote:
I will wait for 1-2 weeks to see if everything is ok with latest -testing and if it is, will issue a new -thumb update. |
Re: [ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900
Quote:
Code:
Preparing to replace libssl0.9.8 0.9.8n-1+maemo4+0m5+0cssu0+thumb1 (using .../libssl0.9.8_0.9.8n-1+maemo4+0m5+0cssu1_armel.deb) ... |
All times are GMT. The time now is 13:25. |
vBulletin® Version 3.8.8