10 May
2011
10 May
'11
6:48 p.m.
theres a correct build with gcc 4.6 support.. this can be helpfull
see : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611255
a release of qt3 susesfully patched for gcc 4.6 can be!
On 5/9/11, Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only zealots
users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.
Le Mon, 09 May
2011 17:18:11 -0500,
"David C. Rankin" <drankinatty(a)suddenlinkmail.com> a écrit :
Both of you are correct. As you find them, please add the
filenames to
the list at http://trinity.etherpad.trinitydesktop.org/27 and I or Serghei
will commit them to SVN and remove them from that list every now and then
Thanks!
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Tim, Serghei,
As we find the headers that need to be patched with '#include
<cstddef>', can those be updated in SVN? Is there any reason not?
If adding the include won't impact those building on gcc < 4.6, then
I say we do it so that the code is 4.6 compliant and won't need
fixing later.
If #include'ing <cstddef> to a header breaks compilation
of the code
with any compiler, there are serious problems with the code and they
shall be solved.