Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] C++ compile probblem
- Date: Fri, 23 Feb 2007 00:27:26 +0900
- From: "Stephen J. Turnbull" <stephen@??>
- Subject: Re: [tlug] C++ compile probblem
- References: <45DD2F44.9020702@example.com> <87tzxeli8r.fsf@example.com> <45DD7AB2.7020304@example.com> <78d7dd350702220357k692e6ed9wdccb24dff7365dbd@example.com>
Nguyen Vu Hung writes: > FYI, Turbull asked you to run Actually, I didn't. > uname -a > cat /etc/rel* > g++ -v > > and post the output. Well, if Brett considers it worth solving the problem, that's halfway there. We also need to see the same info for the system where it's known to work, for the toolchain configuration used to build the working executable. I'm willing to trust Brett to know whether he needs this badly enough to go through that pain. Why do I think it's likely to be painful? Because C++ is famous for (1) changing ABIs across micro releases (2) tightly binding the stdlibc++ to the version of the compiler (3) changing APIs, too. Of course this wouldn't matter if the code Brett is trying to compile was accessing only published stdlibc++ interfaces, but unfortunately we know that's not the case. The code is reaching inside the structures and passing the content to system calls. *shiver*
- Follow-Ups:
- Re: [tlug] C++ compile probblem
- From: Brett Robson
- References:
- [tlug] C++ compile probblem
- From: Brett Robson
- [tlug] C++ compile probblem
- From: Stephen J. Turnbull
- Re: [tlug] C++ compile probblem
- From: Brett Robson
- Re: [tlug] C++ compile probblem
- From: Nguyen Vu Hung
Home | Main Index | Thread Index
- Prev by Date: [tlug] /dev/random is truly random?
- Next by Date: [tlug] /dev/random is truly random?
- Previous by thread: Re: [tlug] C++ compile probblem
- Next by thread: Re: [tlug] C++ compile probblem
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links