Bug 122468

Summary: Compile problems after upgrading to 7.0
Product: Base System Reporter: ruud
Component: amd64Assignee: freebsd-amd64 (Nobody) <amd64>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description ruud 2008-04-05 16:10:00 UTC 
I've upgrade freebsd 6.3 to 7.0 using this site :
http://www.cyberciti.biz/faq/howto-...erver-upgrades/

After upgrading i've tried to upgrade the ports tree.
I've got the same error over different ports.
The port apache22 gives the following error :
/usr/bin/ld: /usr/lib/libpthread.a(thr_syscalls.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC
/usr/lib/libpthread.a: could not read symbols: Bad value
*** Error code 1

Stop in /usr/ports/www/apache22/work/httpd-2.2.8/srclib/apr.
*** Error code 1

Fix: 

After installing i had to create a symlink : ln -s /usr/lib/libthr.so /usr/lib/libpthread.so
This fixes the problem.
How-To-Repeat: Upgrade to 7.0 on an amd64 system
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2008-04-05 20:28:25 UTC 
Ruud Boon wrote:

> FreeBSD myserver.nl 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008     root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
> 
>> Description:
> I've upgrade freebsd 6.3 to 7.0 using this site :
> http://www.cyberciti.biz/faq/howto-...erver-upgrades/

That is not a working URL, but it's also not official upgrade 
documentation.  That you ran into problems after following it suggests 
that the instructions may well be broken.  Talk to the person who wrote 
them.

> After installing i had to create a symlink : ln -s /usr/lib/libthr.so /usr/lib/libpthread.so
> This fixes the problem.

A correctly upgraded system will already have this symlink.

Kris
Comment 2 Kris Kennaway freebsd_committer freebsd_triage 2008-04-14 17:37:44 UTC 
State Changed
From-To: open->feedback

Submitter needs to provide additional information about his upgrade 
process before we can attempt to proceed.
Comment 3 ruud 2008-04-14 21:13:44 UTC 
I've upgraded an other system doing the following upgrade procedure. The 
same problem occured.
I used this procedure :

# fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz
# fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz.asc
# gpg --verify freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz
# tar -xf freebsd-update-upgrade.tgz
# sh freebsd-update.sh -f freebsd-update.conf -r 7.0-RELEASE upgrade
# sh freebsd-update.sh -f freebsd-update.conf install
# shutdown -r now

# sh freebsd-update.sh -f freebsd-update.conf install
# portupgrade -faP
# sh freebsd-update.sh -f freebsd-update.conf install
# shutdown -r now
Comment 4 Gavin Atkinson freebsd_committer freebsd_triage 2008-08-28 17:28:58 UTC 
State Changed
From-To: feedback->open

Feedback was received
Comment 5 Jaakko Heinonen freebsd_committer freebsd_triage 2010-11-28 09:49:31 UTC 
State Changed
From-To: open->feedback

Is this still a problem with later upgrades?
Comment 6 Jaakko Heinonen freebsd_committer freebsd_triage 2011-03-12 07:52:16 UTC 
State Changed
From-To: feedback->closed

Feedback timeout.