Bug 349591 - ld relocation problem while backporting php-5.2.4 to el4 on x86_64
ld relocation problem while backporting php-5.2.4 to el4 on x86_64
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: php (Show other bugs)
rawhide
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Joe Orton
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-23 17:07 EDT by Ingvar Hagelund
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-10-23 17:41:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
part of rpmbuild output (4.31 KB, text/plain)
2007-10-23 17:07 EDT, Ingvar Hagelund
no flags Details

  None (edit)
Description Ingvar Hagelund 2007-10-23 17:07:51 EDT
Description of problem:
x86_64/i386 ld problem (while backporting to el4 on x86_64)

Version-Release number of selected component (if applicable):
5.2.4-3

How reproducible:
Always

Steps to Reproduce:

1. Fetch and install missing builddep packages from rpmforge or backport them
from rawhide.

2. Install source rpm on el4. Remove unsupported -Wno-pointer-sign on gcc-3.4.6
from CFLAGS in specfile. 

3. rpmbuild -bb php.spec. Watch as build fails on x86_64. Note that build in
i386 works without problems


Actual results:
ld says: relocation R_X86_64_32 against `a local symbol' can not be used when
making a shared object

For more details, se attached part of build log. 

Expected results:

A clean build as on i386

Additional info:
None
Comment 1 Ingvar Hagelund 2007-10-23 17:07:51 EDT
Created attachment 235551 [details]
part of rpmbuild output
Comment 2 Joe Orton 2007-10-23 17:41:33 EDT
That libc-client is not built with -fPIC.  Please don't file such issues in
Fedora bugzilla, try a RHEL or EPEL mailing list.

Note You need to log in before you can comment on or make changes to this bug.