Bug 65722 – qt-3.3.3-r1 did not properly create symlinks from /usr/qt/3/lib to lib64

• Status: RESOLVED WORKSFORME
• Product: Gentoo Linux

[Description Jonathan Briggs 2004-09-28 13:35:26 UTC]

I emerged qt-3.3.3-r1 and it created a symlink inside the lib64 directory instead of one level above.  This may have also caused it to fail to create the proper libqt-mt.so link in the directory as well.

I fixed these things by hand and was able to continue.

Reproducible: Always
Steps to Reproduce:
1. Use an amd64 system
2. Make sure /usr/qt does not exist.
3. Emerge qt-3.3.3-r1
4. Look for /usr/qt/3/lib to be a symlink to lib64.  If it isn't then you have reproduced the bug.

Actual Results:  
Programs depending on QT would not compile.

Expected Results:  
Created the symlink correctly.

[Comment 1 Andrew Ross (RETIRED) 2004-09-29 00:19:11 UTC]

*** Bug 65322 has been marked as a duplicate of this bug. ***

[Comment 2 Andrew Ross (RETIRED) 2004-09-29 00:33:52 UTC]

Travis, this looks like something you need to take care of, as per bug 45669

[Comment 3 Gregorio Guidi (RETIRED) 2005-01-02 09:42:24 UTC]

*** Bug 73828 has been marked as a duplicate of this bug. ***

[Comment 4 Dario Birtic 2005-03-04 18:45:29 UTC]

A simple workaround I use;

if [ ! -L /usr/qt/3/lib64 ]; then
  mv /usr/qt/3/lib64/* /usr/qt/3/lib
  rmdir /usr/qt/3/lib64
  ln -s /usr/qt/3/lib /usr/qt/3/lib64
fi

[Comment 5 den_RDC 2005-05-30 11:53:20 UTC]

I have the same problem with x11-libs/qt-3.3.4-r3 after updating my profile to 
2005.0 

[Comment 6 Jakub Moc (RETIRED) 2005-07-24 03:27:29 UTC]

*** Bug 87369 has been marked as a duplicate of this bug. ***

[Comment 7 Glenn L. McGrath 2005-08-06 16:06:05 UTC]

*** Bug 101281 has been marked as a duplicate of this bug. ***

[Comment 8 Glenn L. McGrath 2005-08-06 16:10:54 UTC]

Just marked my bug (kdissert fails to compile) as a duplicate of this bug.

I have to say, its pretty frustrating to be working on a system that has 10
month old bugs laying around which only need a symlink to fix.

Why hasnt this been fixed, is qt still being maintained ?

[Comment 9 Torsten Veller (RETIRED) 2006-01-08 00:03:44 UTC]

Assigning to qt herd -- CC amd64

[Comment 10 Marcus D. Hanwell (RETIRED) 2006-01-08 04:07:08 UTC]

The following lines in the ebuild should already take care of this, and were added quite some time ago. They worked here without issue and I have a lib -> lib64 symlink in /usr/qt/3

    if [ "${SYMLINK_LIB}" = "yes" ]; then
        dosym $(get_abi_LIBDIR ${DEFAULT_ABI}) ${QTBASE}/lib
    fi

This is the first I have seen of this particular bug. At some point programs that don't work without the symlink need fixing anyway, but the symlink is created on all my installations. Including emerge info may help narrow down a common denominator.

[Comment 11 Herbie Hopkins (RETIRED) 2006-01-08 04:42:19 UTC]

qt should (and does here) work without the symlink, this was fixed some time ago.

[Comment 12 Marcus D. Hanwell (RETIRED) 2006-01-08 05:05:10 UTC]

(In reply to comment #11)
> qt should (and does here) work without the symlink, this was fixed some time
> ago.
> 
I don't know if there are some programs hanging around that don't link properly without the symlink, which is more what I was referring to. They will need to be fixed if they haven't already been.

[Comment 13 Simon Stelling (RETIRED) 2006-01-27 14:56:31 UTC]

is this really still an issue? i doubt it, but i don't use qt/kde apps. can anybody confirm? otherwise i'm going to close the bug

[Comment 14 Scott Stoddard (RETIRED) 2006-01-27 15:41:19 UTC]

The current stable version of qt (3.3.4-r8) works properly on my stable system and 3.3.3 is not in the tree any more.  please re-open if anyone is still having troubles once they hit 3.3.4-r8