Summary: | xfcalendar-4.2.3 does not build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
Component: | [OLD] Unspecified | Assignee: | XFCE Team <xfce> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 129371 | ||
Bug Blocks: |
Description
Petteri Räty (RETIRED)
2006-05-14 02:38:06 UTC
I see the same error. After upgrading to gcc 3.4.6 and emerge -e world > -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 Can you check without these? > FEATURES="autoconfig collision-protect confcache distcc distlocks noinfo And without confcache and distcc? If error is still there, it must be valid. Need to verify.(tm) No information has provided and it seems unreproducable. Closing.. (In reply to comment #3) > No information has provided and it seems unreproducable. Closing.. > Why do you have the power to mark bugs as RESOLVED? It should be for developers only. (In reply to comment #2) > > -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 > > Can you check without these? > These are the same CFLAGS that kernel uses to build for my Trasmeta Crusoe processor they should be quite safe. > > > FEATURES="autoconfig collision-protect confcache distcc distlocks noinfo > > And without confcache and distcc? > > If error is still there, it must be valid. Need to verify.(tm) > The error is not there any more, but since reporting this gcc stable has gone to 4.1.1 and even with 3.4.6 I could not reproduce this any more. Granted this could have been confcache related but that has been masked for quite a while so this can be kept as resolved. (In reply to comment #4) > (In reply to comment #3) > > No information has provided and it seems unreproducable. Closing.. > > > > Why do you have the power to mark bugs as RESOLVED? It should be for developers > only. Incoming developers occasionally get bugzilla privs before they're properly, er, broken in, as is the case with drac here. |