View previous topic :: View next topic |
Author |
Message |
Guest Guest
|
Posted: Mon May 06, 2002 8:55 am Post subject: xmms qt nas-sound love triangle? |
|
|
Here is a recap of my recent ebuild script woes....
qt-3.0.4.ebuild failed. I did some research and it seems that the problem may be in the configure script of the qt sourcecode. The "-system-nas-sound" input parameter does not appear to be properly parsed and is rejected. (There is some pretty hairy reg-exp that seems to be comming up short.) Note this is the only parameter of the -system-xxxxx variety to have a hyphen '-' in the xxxxx part of the parameter name.
Commenting the line for this option out of the qt ebuild script allowed qt to carry on just fine with installing qt-3.0.4.
Then I tried to emerge xmms-1.2.7-r4 which has a dependency on avifile-0.6 or greater. The most recent avifile that I have is avifile-0.7.4.20020426.ebuild. It has a dependency for qt that spells out ( =x11-libs/qt-3.0.3*).
So what is nas-sound anyway and why is that config option causing qt-3.0.4 to blow up? What can I expect if I emerge xmms and allow qt-3.0.3.1 to go on after 3.0.4 has been installed? Why does avifile explicitly limit the qt library to a 3.0.3* series?
Hopefully I will remember the right combination of username and email to get the help I forgot my password link to do me some good, but in the meantime these are the questions that I am trying to research. If anyone else happens to be exploring same/similiar issues let's try to compare notes (well issues with the ebuild that is, not the password problem...) Maybe I should get some sleep... |
|
Back to top |
|
|
papaC n00b
Joined: 25 Apr 2002 Posts: 19 Location: Florida
|
Posted: Thu May 09, 2002 5:20 pm Post subject: |
|
|
FYI - This is from QT- mailing list.
Hi,
> I always perfer to use system libraries whenever possible. I already have
> latest nas library installed and tried to compile qt-3.0.4 with the
> -system-nas-sound flag.
>
> The configure script does not allow this flag even though it is listed as a
> valid choice. It appears that the problem may be with the fact that the
> section of the configure script which parses the options can not handle the
> fact that the option has two hyphens (-) in it. At least that is what
> appeared to be the problem from adding some echo statements to the configure
> script. The regular expressions used to parse the parameters is a bit more
Yes, the regular expressions are incorrect. Change the first
.*
to
[^-]*
for each of the involved regular expression.
Otherwise Qt bugs are handled by sending a bug report to
qt-bugs@trolltech.com
The information is hidden here:
http://www.trolltech.com/company/contact.html
I'm forwarding this bug to qt-bugs@trolltech.com.
Dimitri
--
List archive and information: http://lists.trolltech.com/qt-interest/ _________________ Down with categorical imperative! |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|