Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 84554

Summary: crystalspace requires -fPIC on amd64
Product: Gentoo Linux Reporter: Guido <gentoo>
Component: New packagesAssignee: Gentoo Games <games>
Status: RESOLVED INVALID    
Severity: minor CC: amd64, as.gentoo, bruno
Priority: High    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Patch that appends -fPIC on amd64

Description Guido 2005-03-08 15:00:27 UTC
To be able to successfully build Crystal Space on AMD64 architecture the flag "-fPIC" must be appended to CFLAGS/CXXFLAGS. To fix this bug this line should be added to the src_compile() function:

    [ "${ARCH}" = "amd64" ] && append-flags -fPIC

This also requires that "flag-o-matic" is inherited. Of course the ~amd64 keyword should be added as well.

Reproducible: Always
Steps to Reproduce:
Comment 1 Guido 2005-03-08 15:03:51 UTC
Created attachment 52974 [details, diff]
Patch that appends -fPIC on amd64

The patch implements the proposed modifications.
Comment 2 SpanKY gentoo-dev 2005-03-08 18:30:15 UTC
fix it properly and we'll add amd64 support

sticking -fPIC into CFLAGS is NOT the proper fix
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2005-06-06 00:50:24 UTC
*** Bug 95170 has been marked as a duplicate of this bug. ***
Comment 4 Simon Stelling (RETIRED) gentoo-dev 2005-08-16 10:46:45 UTC
*** Bug 94541 has been marked as a duplicate of this bug. ***
Comment 5 Attila Stehr 2005-08-16 12:32:13 UTC
Why is this bug marked "resolved invalid"?
I still can't emerge crystalspace successfully!

anyway:
As upgrading to 2005.0 resolved the fPIC issue now there is an other issue. See
# 94541.

regards
Comment 6 Chris Gianelloni (RETIRED) gentoo-dev 2005-08-16 13:26:12 UTC
*** Bug 94541 has been marked as a duplicate of this bug. ***
Comment 7 SpanKY gentoo-dev 2005-08-16 20:15:07 UTC
read comment #2 ... just throwing -fPIC into CFLAGS/CXXFLAGS is incorrect
Comment 8 Attila Stehr 2005-08-17 05:56:35 UTC
So what is the solution then? This bugs state is <b>_RESOLVED_</b> (invalid).

If so just saying "fix it properly" resolves a bug?! Very interesting...