On 02/14/2011 07:32 PM, Ng Oon-Ee wrote:
> Just a quick question for you, as I understand it Trinity is basically a
> fork of kde3. From your comments in this thread it does seem there is
> some activity in the project. What's the plans of the project, an
> indefinite maintenance of current functio
On Mon, 2011-02-14 at 19:19 -0600, David C. Rankin wrote:
> On 02/14/2011 09:33 AM, David C. Rankin wrote:
> > So there is definitely a problem with gcc 4.5.2
> > (g++).
>
> Correction,
>
> There was a definite problem with the Trinity code after
> http://gcc.gnu.org/bugzilla/show_bug.cgi?i
On 02/14/2011 09:33 AM, David C. Rankin wrote:
> So there is definitely a problem with gcc 4.5.2
> (g++).
Correction,
There was a definite problem with the Trinity code after
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11764 for gcc >=4.5 that rejected
the existing class constructors in t
On 02/13/2011 10:07 PM, Allan McRae wrote:
>>
>> What other parts/packages do I need to downgrade, etc. to work with gcc-4.3?
>>
>
> None - you probably need to rebuild earlier Trinity components with the older
> gcc though.
>
> Allan
Allan,
Thanks -- that was the ticket. I rebuilt everything
On 02/13/2011 10:07 PM, Allan McRae wrote:
> None - you probably need to rebuild earlier Trinity components with the older
> gcc though.
>
> Allan
Thanks!
--
David C. Rankin, J.D.,P.E.
On 14/02/11 13:59, David C. Rankin wrote:
On 02/13/2011 09:52 PM, David C. Rankin wrote:
On 02/13/2011 08:52 PM, David C. Rankin wrote:
On 02/13/2011 07:07 PM, Allan McRae wrote:
That is not a downgrade but a separate package. You will need to use something
like "CC=gcc-4.3 ./configure" in y
On 02/13/2011 09:52 PM, David C. Rankin wrote:
> On 02/13/2011 08:52 PM, David C. Rankin wrote:
>> On 02/13/2011 07:07 PM, Allan McRae wrote:
>>> That is not a downgrade but a separate package. You will need to use
>>> something
>>> like "CC=gcc-4.3 ./configure" in your PKGBUILD to use that gcc
On 02/13/2011 08:52 PM, David C. Rankin wrote:
> On 02/13/2011 07:07 PM, Allan McRae wrote:
>> That is not a downgrade but a separate package. You will need to use
>> something
>> like "CC=gcc-4.3 ./configure" in your PKGBUILD to use that gcc version.
>>
>> Allan
>
> Oh, your good...
>
> I w
On 02/13/2011 07:07 PM, Allan McRae wrote:
> That is not a downgrade but a separate package. You will need to use
> something
> like "CC=gcc-4.3 ./configure" in your PKGBUILD to use that gcc version.
>
> Allan
Oh, your good...
I would have messed that up royally. Thanks for being clairvoyan
On 14/02/11 10:59, David C. Rankin wrote:
On 02/13/2011 06:42 PM, Allan McRae wrote:
Grab the gcc43 package from the AUR. I had a quick look at the PKGBUILD and it
looks good. The gcc44 package not so much...
Allan
Great! Thank you Allan,
I'll be downgrading a VirtualBox VM so if it
On 02/13/2011 06:42 PM, Allan McRae wrote:
>
>
> Grab the gcc43 package from the AUR. I had a quick look at the PKGBUILD and
> it
> looks good. The gcc44 package not so much...
>
> Allan
Great! Thank you Allan,
I'll be downgrading a VirtualBox VM so if it all goes south - not much of an
On 14/02/11 10:35, David C. Rankin wrote:
Guys,
After running into a gcc 4.5.2 segfault, the trinity developer suggested a
test to downgrade gcc to 4.4 or 4.3 and see if the gcc issue and issue
concerning iccconfig.cpp go away. Looking through my old packages, the earliest
I can find is 4.5.1
Guys,
After running into a gcc 4.5.2 segfault, the trinity developer suggested a
test to downgrade gcc to 4.4 or 4.3 and see if the gcc issue and issue
concerning iccconfig.cpp go away. Looking through my old packages, the earliest
I can find is 4.5.1.
How best to downgrade?... and will I bre
13 matches
Mail list logo
