Linked by Thom Holwerda on Sun 12th Aug 2007 15:52 UTC, submitted by zaboing
PDAs, Cellphones, Wireless "A few months ago, the GNOME Mobile Platform was announced to the public. One of the main forces behind the launch of this initiative was Nokia, which uses a lot of GNOME-components in its Linux-based Internet Tablets Nokia 770 and N800. During this years GUADEC Andreas Proschofsky had the chance to sit down with Carlos Guerreiro, Nokias Manager for Open Source Software, to talk - amidst other things - about the not so different needs of personal computers and mobile devices, about the necessity for GTK+ 3.0 and the impact of the iPhone launch."
Thread beginning with comment 263019
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: what situation?
by yokem55 on Mon 13th Aug 2007 13:55 UTC in reply to "RE: what situation?"
yokem55
Member since:
2005-07-06

The problem with the C++ Linux ABI (which is really the GNU C++ ABI) is that it changes frequently.


I am no developer, but I do run gentoo, and I know when the c++ abi changes due to a gcc upgrade (I have to rebuild everying linking against libstdc++), and if I remember correctly, there hasn't been an abi breakage since the upgrade from gcc-3.3 to 3.4, and 3.4 was shipped in April of 2004. So, comparitively with the previous abi history of gcc (about 1 break per year), things have stablized considerably in C++ abi land with gcc 3.4+.

Reply Parent Score: 4

RE[3]: what situation?
by binarycrusader on Mon 13th Aug 2007 19:16 in reply to "RE[2]: what situation?"
binarycrusader Member since:
2005-07-06

"The problem with the C++ Linux ABI (which is really the GNU C++ ABI) is that it changes frequently.


I am no developer, but I do run gentoo, and I know when the c++ abi changes due to a gcc upgrade (I have to rebuild everying linking against libstdc++), and if I remember correctly, there hasn't been an abi breakage since the upgrade from gcc-3.3 to 3.4, and 3.4 was shipped in April of 2004. So, comparitively with the previous abi history of gcc (about 1 break per year), things have stablized considerably in C++ abi land with gcc 3.4+.
"

Wrong, the ABI recently chnaged again in 4.1:
http://gcc.gnu.org/gcc-4.1/changes.html

Reply Parent Score: 2

RE[4]: what situation?
by yokem55 on Mon 13th Aug 2007 21:22 in reply to "RE[3]: what situation?"
yokem55 Member since:
2005-07-06

From the page you linked:

The x86-64 medium model (that allows building applications whose data segment exceeds 4GB) was redesigned to match latest ABI draft. New implementation split large datastructures into separate segment improving performance of accesses to small datastructures and also allows linking of small model libraries into medium model programs as long as the libraries are not accessing the large datastructures directly. Medium model is also supported in position independent code now.

The ABI change results in partial incompatibility among medium model objects. Linking medium model libraries (or objects) compiled with new compiler into medium model program compiled with older will likely result in exceeding ranges of relocations.


Basically, this is only a partial abi breakage on 64-bit binaries with data segments that can exceed 4 GB. Anything that is 32-bit only (as is the vast majority of ISV-ware) is unaffected.

Edited 2007-08-13 21:23

Reply Parent Score: 1