I have to admit, I'm not quite following how this works...
As an example, RHEL doesn't ship w/ libstdc++.so.6. Does LSB
statically link something to deal with that problem?
geir
On Jan 11, 2007, at 2:27 AM, Sunny Chan wrote:
Hi Geir,
That doesn't really affect that - LSB is based on POSIX, and they
are pretty much just a agreed version of glibc/libstdc++/etc that
all Linux vendor would pledge to implement - of course that doesn't
mean you should use library calls there is, which compromise the
portability to other Unices, just like how you compile to certain
version of RH/Suse/etc, but you also compile on other Unixces too.
Thanks
Geir Magnusson Jr. wrote:
How would this affect portability to non-linux platforms?
geir
On Jan 10, 2007, at 8:22 PM, Sunny Chan wrote:
Geir Magnusson Jr. <geir <at> pobox.com> writes:
I ran into this playing with Harmony on OLPC, and a developer
expressed a little surprise that we were still using 3.x. I don't
follow the gcc ecosystem at all, so I don't know what issues there
are w/ 4.x, and why we wouldn't move forward to it as a general
(not
strict) policy.
geir
Actually let me throw another idea at you - Why not compile with
LSB SDK, which
would actually work across different distribution, and no glibc/
libstdc++
dependency!
For more about LSB, see http://www.freestandards.org/en/LSB
For more about developing with LSB, seehttp://
www.freestandards.org/en/Developers
Thanks,
Sunny Chan
