[gentoo-user] [OT] Still trying to compile hydrogen

[gentoo-user] [OT] Still trying to compile hydrogen

[meino.cramer]

Hi,

I want to compile hydrogen cleanly.

Since the ebuild of hydrogen fails to compile because
the system "linux3" is not known (which happens even
when compiled on a linux-2.6*-booted machine)...

I was pointed to patch which fixes this problem, but
unfortunately it only opens the way to the next problem.

I decided to try to compile hydrogen from vanilla sources
and outside the emerge/portage system to better understand
wahts happening.

When doing so, one has to set QTDIR and then run scons.

Hydrogen needs qt4.

I set QTDIR to /usr/share/qt4.

The compilation fails because QtGui could not be found.

QtGui is here /usr/include/qt4/Qt/QtGui which is a file which 
includes all relevant header file in one go.

So I tried to set QTDIR to /usr/include/qt4 but this produces
the same problem.

I decided to hack the relevant file of hydorgen and hardcoded
the path to QtGui directly into the include statement. No comments
on this please, it is a bad bad ugly thing to do so. I simply
wa curious to see next problem...

And I was not dissappointed. This time the QtGui-file could not
find the first header file which it includes:

#include <QtCore/QtCore>

To hack also /usr/include/qt4/Qt/QtGui is no way.

So....either hydrogens build mechanism does not fit the installation 
of Qt4 on my Gentoo system (Qt4 was installed via emerge/portage) or
it has a bug or the problem sits right in front of my monitor and
is currently writing a post to the gentoo-users mailinglist... ;)

In the latter case the chance are not small, that I will be able to
fix the problem...

If I only would know, how ;))

What did I wrong here?

Thank you very much in advance for any help!

Best regards
mcc

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Paul Hartman]

On Sat, Feb 18, 2012 at 12:37 AM,  <meino.cramer@gmx.de> wrote:
> I want to compile hydrogen cleanly.
>
> Since the ebuild of hydrogen fails to compile because
> the system "linux3" is not known (which happens even
> when compiled on a linux-2.6*-booted machine)...

You may want to try the ebuild again. I'm using kernel 3.2.6 on ~amd64
and just emerged media-sound/hydrogen-0.9.5 no problems at all.

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[meino.cramer]

Paul Hartman <paul.hartman+gentoo@gmail.com> [12-02-18 09:04]:
> On Sat, Feb 18, 2012 at 12:37 AM,  <meino.cramer@gmx.de> wrote:
> > I want to compile hydrogen cleanly.
> >
> > Since the ebuild of hydrogen fails to compile because
> > the system "linux3" is not known (which happens even
> > when compiled on a linux-2.6*-booted machine)...
> 
> You may want to try the ebuild again. I'm using kernel 3.2.6 on ~amd64
> and just emerged media-sound/hydrogen-0.9.5 no problems at all.
> 

Hi Paul,

thanks for yor reply.

The result is: 

solfire:/home/user>sudo emerge hydrogen
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) media-sound/hydrogen-0.9.5
>>> Downloading 'http://de-mirror.org/distro/gentoo/distfiles/hydrogen-0.9.5.tar.gz'
--2012-02-18 09:52:47--  http://de-mirror.org/distro/gentoo/distfiles/hydrogen-0.9.5.tar.gz
Resolving de-mirror.org... 87.106.54.147
Connecting to de-mirror.org|87.106.54.147|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://de-mirror.org/gentoo/distfiles/hydrogen-0.9.5.tar.gz [following]
--2012-02-18 09:52:47--  http://de-mirror.org/gentoo/distfiles/hydrogen-0.9.5.tar.gz
Reusing existing connection to de-mirror.org:80.
HTTP request sent, awaiting response... 200 OK
Length: 5239702 (5.0M) [application/x-gzip]
Saving to: `/usr/portage/distfiles/hydrogen-0.9.5.tar.gz'

100%[======================================>] 5,239,702    239K/s   in 22s     

2012-02-18 09:53:09 (238 KB/s) - `/usr/portage/distfiles/hydrogen-0.9.5.tar.gz' saved [5239702/5239702]

 * hydrogen-0.9.5.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                             [ ok ]
>>> Unpacking source...
>>> Unpacking hydrogen-0.9.5.tar.gz to /var/tmp/portage/media-sound/hydrogen-0.9.5/work
>>> Source unpacked in /var/tmp/portage/media-sound/hydrogen-0.9.5/work
>>> Preparing source in /var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5 ...
 * Applying portaudio.patch ...
 [ ok ]
 * Applying hydrogen-0.9.5-use_lrdf_pkgconfig.patch ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5 ...
scons: Reading SConscript files ...
Exception: Platform 'linux3' not supported:
  File "/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5/Sconstruct", line 378:
    includes, a , b = get_platform_flags( opts )
  File "/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5/Sconstruct", line 103:
    raise Exception( "Platform '%s' not supported" % sys.platform )
 * ERROR: media-sound/hydrogen-0.9.5 failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  85:  Called src_compile
 *   environment, line 2405:  Called die
 * The specific snippet of code:
 *       scons prefix=/usr DESTDIR="${D}" optflags="${CXXFLAGS}" ${myconf} || die
 * 
 * If you need support, post the output of 'emerge --info =media-sound/hydrogen-0.9.5',
 * the complete build log and the output of 'emerge -pqv =media-sound/hydrogen-0.9.5'.
 * The complete build log is located at '/var/tmp/portage/media-sound/hydrogen-0.9.5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-sound/hydrogen-0.9.5/temp/environment'.
 * S: '/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5'

>>> Failed to emerge media-sound/hydrogen-0.9.5, Log file:

>>>  '/var/tmp/portage/media-sound/hydrogen-0.9.5/temp/build.log'


As mentioned in my previous post, the problem is not the kernel
version and after getting over this bug there are others ahead.

How do I have to set QTDIR correctly under Gentoo/Qt4 ?

Thank you very much in advance for any help!
Best regards,
mcc

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

On Sat, 18 Feb 2012 09:56:03 +0100, meino.cramer@gmx.de wrote:

> Exception: Platform 'linux3' not supported:
>   File
> "/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5/Sconstruct",
> line 378: includes, a , b = get_platform_flags( opts ) File
> "/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5/Sconstruct",
> line 103: raise Exception( "Platform '%s' not supported" % sys.platform
> )

This is not related to your kernel version AFAICT. sys.platform is set to
linux2 on the two systems running version 3 kernels I've tried it on.
According to the python docs

"Changed in version 2.7.3: Since lots of code check for sys.platform ==
'linux2', and there is no essential change between Linux 2.x and 3.x,
sys.platform is always set to 'linux2', even on Linux 3.x. In Python 3.3
and later, the value will always be set to 'linux', so it is recommended
to always use the startswith idiom presented above."

It sounds like you are using an older python.


-- 
Neil Bothwick

If you think that there is good in everybody, you haven't met everybody.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[meino.cramer]

Neil Bothwick <neil@digimed.co.uk> [12-02-18 10:28]:
> On Sat, 18 Feb 2012 09:56:03 +0100, meino.cramer@gmx.de wrote:
> 
> > Exception: Platform 'linux3' not supported:
> >   File
> > "/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5/Sconstruct",
> > line 378: includes, a , b = get_platform_flags( opts ) File
> > "/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5/Sconstruct",
> > line 103: raise Exception( "Platform '%s' not supported" % sys.platform
> > )
> 
> This is not related to your kernel version AFAICT. sys.platform is set to
> linux2 on the two systems running version 3 kernels I've tried it on.
> According to the python docs
> 
> "Changed in version 2.7.3: Since lots of code check for sys.platform ==
> 'linux2', and there is no essential change between Linux 2.x and 3.x,
> sys.platform is always set to 'linux2', even on Linux 3.x. In Python 3.3
> and later, the value will always be set to 'linux', so it is recommended
> to always use the startswith idiom presented above."
> 
> It sounds like you are using an older python.
> 
> 
> -- 
> Neil Bothwick
> 
> If you think that there is good in everybody, you haven't met everybody.



Hi Neil,

now it becomes more complicate (at least for me... ;)

With

    eselect python list

I get

Available Python interpreters:
  [1]   python2.6
  [2]   python2.7
  [3]   python3.1
  [4]   python3.2 *

Compiling hydrogen with this settings I get:
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) media-sound/hydrogen-0.9.5
 * hydrogen-0.9.5.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                             [ ok ]
>>> Unpacking source...
>>> Unpacking hydrogen-0.9.5.tar.gz to /var/tmp/portage/media-sound/hydrogen-0.9.5/work
>>> Source unpacked in /var/tmp/portage/media-sound/hydrogen-0.9.5/work
>>> Preparing source in /var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5 ...
 * Applying portaudio.patch ...
 [ ok ]
 * Applying hydrogen-0.9.5-use_lrdf_pkgconfig.patch ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5 ...
scons: Reading SConscript files ...
Exception: Platform 'linux3' not supported:
  File "/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5/Sconstruct", line 378:
    includes, a , b = get_platform_flags( opts )
  File "/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5/Sconstruct", line 103:
    raise Exception( "Platform '%s' not supported" % sys.platform )
 * ERROR: media-sound/hydrogen-0.9.5 failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  85:  Called src_compile
 *   environment, line 2405:  Called die
 * The specific snippet of code:
 *       scons prefix=/usr DESTDIR="${D}" optflags="${CXXFLAGS}" ${myconf} || die
 * 
 * If you need support, post the output of 'emerge --info =media-sound/hydrogen-0.9.5',
 * the complete build log and the output of 'emerge -pqv =media-sound/hydrogen-0.9.5'.
 * The complete build log is located at '/var/tmp/portage/media-sound/hydrogen-0.9.5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-sound/hydrogen-0.9.5/temp/environment'.
 * S: '/var/tmp/portage/media-sound/hydrogen-0.9.5/work/hydrogen-0.9.5'

>>> Failed to emerge media-sound/hydrogen-0.9.5, Log file:

>>>  '/var/tmp/portage/media-sound/hydrogen-0.9.5/temp/build.log'



eix -n dev-lang/python results in:


[I] dev-lang/python
     Available versions:  
	(2.5)	2.5.4-r4
	(2.6)	2.6.6-r2 ~2.6.7-r2
	(2.7)	2.7.2-r3
	(3.1)	3.1.4-r3
	(3.2)	3.2.2
	{-berkdb build doc elibc_uclibc examples gdbm ipv6 +ncurses +readline sqlite +ssl +threads tk +wide-unicode wininst +xml}
     Installed versions:  2.6.6-r2(2.6)(18:09:51 10/19/11)(doc examples gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml -berkdb -build -elibc_uclibc -wininst) 2.7.2-r3(2.7)(01:33:12 10/28/11)(doc examples gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml -berkdb -build -elibc_uclibc -wininst) 3.1.4-r3(3.1)(01:35:36 10/28/11)(doc examples gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml -build -elibc_uclibc -wininst) 3.2.2(3.2)(00:00:43 02/18/12)(doc examples gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml -build -elibc_uclibc -wininst)
     Homepage:            http://www.python.org/
     Description:         Python is an interpreted, interactive, object-oriented programming language.


Is there anything newer than what I have installed and eselected?


I am still confused...

Best regards,
mcc

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Paul Hartman]

On Sat, Feb 18, 2012 at 2:56 AM,  <meino.cramer@gmx.de> wrote:
> As mentioned in my previous post, the problem is not the kernel
> version and after getting over this bug there are others ahead.

Sorry, I didn't see the other thread.

It's strange that it emerges normally for me, and the program works,
too. If there's any info about my setup that we can compare, please
ask me. :)

> How do I have to set QTDIR correctly under Gentoo/Qt4 ?

Because Qt4 is not segregated into its own directory like Qt3 was, I
would try setting QTDIR=/usr and see if it works. I have not tried
this myself.

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Alex Schuster]

meino.cramer@gmx.de writes:

> How do I have to set QTDIR correctly under Gentoo/Qt4 ?

QTDIR ist for Qt3 only, AFAIK Qt4 does not use it at all.

	Wonko

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[meino.cramer]

Alex Schuster <wonko@wonkology.org> [12-02-18 14:12]:
> meino.cramer@gmx.de writes:
> 
> > How do I have to set QTDIR correctly under Gentoo/Qt4 ?
> 
> QTDIR ist for Qt3 only, AFAIK Qt4 does not use it at all.
> 
> 	Wonko
> 

When trying to compile media-sound/museseq it complains that QTDIR is
not set and breaks...

Best regards,
mcc

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[meino.cramer]

meino.cramer@gmx.de <meino.cramer@gmx.de> [12-02-18 14:40]:
> Alex Schuster <wonko@wonkology.org> [12-02-18 14:12]:
> > meino.cramer@gmx.de writes:
> > 
> > > How do I have to set QTDIR correctly under Gentoo/Qt4 ?
> > 
> > QTDIR ist for Qt3 only, AFAIK Qt4 does not use it at all.
> > 
> > 	Wonko
> > 
> 
> When trying to compile media-sound/museseq it complains that QTDIR is
> not set and breaks...
> 
> Best regards,
> mcc
> 
> 
> 


Right after reinstalling Qt-4.7 (core) and QtGui
emerging museseq it fails with



        ***************** WARNING *****************

    YOU HAVE NOT SET YOUR 'QTDIR' ENVIRONMENT VARIABLE!!!

    This is the source of most people's problems when
    configuring muse.  If the configuration fails to find
    qt, try setting your QTDIR environment variable to
    the directory where qt is installed.

        *******************************************


    checking for QT includes (/usr/include/qt)... no
    checking for QT libraries ()... no
    checking for QT moc (moc)... no
    checking for QT uic (uic)... no
    configure: error: need qt >= 3.2.0


Something is very very rotten here...but I dont not what...

Any help in sight at the horizon ... ?

Best regards,
mcc

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Alex Schuster]

meino.cramer@gmx.de writes:

> meino.cramer@gmx.de <meino.cramer@gmx.de> [12-02-18 14:40]:
> > Alex Schuster <wonko@wonkology.org> [12-02-18 14:12]:
> > > meino.cramer@gmx.de writes:
> > > 
> > > > How do I have to set QTDIR correctly under Gentoo/Qt4 ?
> > > 
> > > QTDIR ist for Qt3 only, AFAIK Qt4 does not use it at all.

> > When trying to compile media-sound/museseq it complains that QTDIR is
> > not set and breaks...

> Right after reinstalling Qt-4.7 (core) and QtGui
> emerging museseq it fails with
> 
> 
> 
>         ***************** WARNING *****************
> 
>     YOU HAVE NOT SET YOUR 'QTDIR' ENVIRONMENT VARIABLE!!!
> 
>     This is the source of most people's problems when
>     configuring muse.  If the configuration fails to find
>     qt, try setting your QTDIR environment variable to
>     the directory where qt is installed.
> 
>         *******************************************

This variable was necessary for Qt3, because that was often installed in
unusual locations like /usr/qt/3. Qt4 uses the normal hierarchy, with
stuff being installed in /usr/bn, /usr/lib, and so on. So this variable
should not be needed any more.

>     checking for QT includes (/usr/include/qt)... no
>     checking for QT libraries ()... no
>     checking for QT moc (moc)... no
>     checking for QT uic (uic)... no
>     configure: error: need qt >= 3.2.0
> 
> 
> Something is very very rotten here...but I dont not what...
> 
> Any help in sight at the horizon ... ?

My guess would be that musesq uses Qt3 only, not Qt4.

Someone has the same problem here [*], and someone else came up with a
new ebuild for musesq-2.0_beta2. If that's newer than yours, give that a
try.

[*] http://www.mail-archive.com/proaudio@lists.tuxfamily.org/msg04168.html

	Wonko

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[meino.cramer]

Alex Schuster <wonko@wonkology.org> [12-02-18 15:08]:
> meino.cramer@gmx.de writes:
> 
> > meino.cramer@gmx.de <meino.cramer@gmx.de> [12-02-18 14:40]:
> > > Alex Schuster <wonko@wonkology.org> [12-02-18 14:12]:
> > > > meino.cramer@gmx.de writes:
> > > > 
> > > > > How do I have to set QTDIR correctly under Gentoo/Qt4 ?
> > > > 
> > > > QTDIR ist for Qt3 only, AFAIK Qt4 does not use it at all.
> 
> > > When trying to compile media-sound/museseq it complains that QTDIR is
> > > not set and breaks...
> 
> > Right after reinstalling Qt-4.7 (core) and QtGui
> > emerging museseq it fails with
> > 
> > 
> > 
> >         ***************** WARNING *****************
> > 
> >     YOU HAVE NOT SET YOUR 'QTDIR' ENVIRONMENT VARIABLE!!!
> > 
> >     This is the source of most people's problems when
> >     configuring muse.  If the configuration fails to find
> >     qt, try setting your QTDIR environment variable to
> >     the directory where qt is installed.
> > 
> >         *******************************************
> 
> This variable was necessary for Qt3, because that was often installed in
> unusual locations like /usr/qt/3. Qt4 uses the normal hierarchy, with
> stuff being installed in /usr/bn, /usr/lib, and so on. So this variable
> should not be needed any more.
> 
> >     checking for QT includes (/usr/include/qt)... no
> >     checking for QT libraries ()... no
> >     checking for QT moc (moc)... no
> >     checking for QT uic (uic)... no
> >     configure: error: need qt >= 3.2.0
> > 
> > 
> > Something is very very rotten here...but I dont not what...
> > 
> > Any help in sight at the horizon ... ?
> 
> My guess would be that musesq uses Qt3 only, not Qt4.
> 
> Someone has the same problem here [*], and someone else came up with a
> new ebuild for musesq-2.0_beta2. If that's newer than yours, give that a
> try.
> 
> [*] http://www.mail-archive.com/proaudio@lists.tuxfamily.org/msg04168.html
> 
> 	Wonko
> 

As this line in my previous posting states, museseq needs Qt 4.*,
which is installed...:

       configure: error: need qt >= 3.2.0


Slightly confused,
mcc

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Alex Schuster]

meino.cramer@gmx.de writes:

> As this line in my previous posting states, museseq needs Qt 4.*,
> which is installed...:
> 
>        configure: error: need qt >= 3.2.0

Um, huh? If it would need Qt 4.*, it would say that you need qt >=
4.something. But it says you need qt >= 3.2.0, so qt-meta 3.3.8b-r2
(which I have installed) would do fine.
Oh, I just see that this is no longer in portage, my qt-meta:3 comes from
the kde-sunset overlay.

Maybe having Qt4 installed with the qt3support USE flag would work, but I
doubt it. Qt4 is very different from Qt3.

	Wonko

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Alan McKinnon]

On Sat, 18 Feb 2012 15:37:24 +0100
Alex Schuster <wonko@wonkology.org> wrote:

> meino.cramer@gmx.de writes:
> 
> > As this line in my previous posting states, museseq needs Qt 4.*,
> > which is installed...:
> > 
> >        configure: error: need qt >= 3.2.0
> 
> Um, huh? If it would need Qt 4.*, it would say that you need qt >=
> 4.something. But it says you need qt >= 3.2.0, so qt-meta 3.3.8b-r2
> (which I have installed) would do fine.
> Oh, I just see that this is no longer in portage, my qt-meta:3 comes
> from the kde-sunset overlay.
> 
> Maybe having Qt4 installed with the qt3support USE flag would work,
> but I doubt it. Qt4 is very different from Qt3.

my understanding is that qt3support gives run-time support only 
for apps built against qt3 but running under qt4 (i.e it's just a
simple run-time wrapper around API calls).

But qt3support cannot be used to built against qt4

-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[meino.cramer]

Alan McKinnon <alan.mckinnon@gmail.com> [12-02-18 16:00]:
> On Sat, 18 Feb 2012 15:37:24 +0100
> Alex Schuster <wonko@wonkology.org> wrote:
> 
> > meino.cramer@gmx.de writes:
> > 
> > > As this line in my previous posting states, museseq needs Qt 4.*,
> > > which is installed...:
> > > 
> > >        configure: error: need qt >= 3.2.0
> > 
> > Um, huh? If it would need Qt 4.*, it would say that you need qt >=
> > 4.something. But it says you need qt >= 3.2.0, so qt-meta 3.3.8b-r2
> > (which I have installed) would do fine.
> > Oh, I just see that this is no longer in portage, my qt-meta:3 comes
> > from the kde-sunset overlay.
> > 
> > Maybe having Qt4 installed with the qt3support USE flag would work,
> > but I doubt it. Qt4 is very different from Qt3.
> 
> my understanding is that qt3support gives run-time support only 
> for apps built against qt3 but running under qt4 (i.e it's just a
> simple run-time wrapper around API calls).
> 
> But qt3support cannot be used to built against qt4
> 
> -- 
> Alan McKinnnon
> alan.mckinnon@gmail.com
> 
> 

So, if QT3 is removed from protage, and museseq which still is in
portage seems only to build agains qt3, I see a contradiction here...

May be on my system there somewhere leftovers from ancient time,
when qt3 needs some additional environment variables or such (?)...
what would it be...where I can I look for such settings?

best regards,
mcc

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Alan McKinnon]

On Sat, 18 Feb 2012 16:16:37 +0100
meino.cramer@gmx.de wrote:

> Alan McKinnon <alan.mckinnon@gmail.com> [12-02-18 16:00]:
> > On Sat, 18 Feb 2012 15:37:24 +0100
> > Alex Schuster <wonko@wonkology.org> wrote:
> > 
> > > meino.cramer@gmx.de writes:
> > > 
> > > > As this line in my previous posting states, museseq needs Qt
> > > > 4.*, which is installed...:
> > > > 
> > > >        configure: error: need qt >= 3.2.0
> > > 
> > > Um, huh? If it would need Qt 4.*, it would say that you need qt >=
> > > 4.something. But it says you need qt >= 3.2.0, so qt-meta
> > > 3.3.8b-r2 (which I have installed) would do fine.
> > > Oh, I just see that this is no longer in portage, my qt-meta:3
> > > comes from the kde-sunset overlay.
> > > 
> > > Maybe having Qt4 installed with the qt3support USE flag would
> > > work, but I doubt it. Qt4 is very different from Qt3.
> > 
> > my understanding is that qt3support gives run-time support only 
> > for apps built against qt3 but running under qt4 (i.e it's just a
> > simple run-time wrapper around API calls).
> > 
> > But qt3support cannot be used to built against qt4
> > 
> > -- 
> > Alan McKinnnon
> > alan.mckinnon@gmail.com
> > 
> > 
> 
> So, if QT3 is removed from protage, and museseq which still is in
> portage seems only to build agains qt3, I see a contradiction here...

But media-sound/museseq is NOT in the portage tree. If you have it,
then it comes from an overlay, or from a local ebuild that you maintain.

If museseq requires qt3, then the maintainer of the overlay (or you)
must provide qt3 or provide documentation about which overlay it is in.

IIRC you can find qt3 in kde-sunset

Either way it looks like a maintainer mistake

> May be on my system there somewhere leftovers from ancient time,
> when qt3 needs some additional environment variables or such (?)...
> what would it be...where I can I look for such settings?



-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[meino.cramer]

Alan McKinnon <alan.mckinnon@gmail.com> [12-02-18 16:36]:
> On Sat, 18 Feb 2012 16:16:37 +0100
> meino.cramer@gmx.de wrote:
> 
> > Alan McKinnon <alan.mckinnon@gmail.com> [12-02-18 16:00]:
> > > On Sat, 18 Feb 2012 15:37:24 +0100
> > > Alex Schuster <wonko@wonkology.org> wrote:
> > > 
> > > > meino.cramer@gmx.de writes:
> > > > 
> > > > > As this line in my previous posting states, museseq needs Qt
> > > > > 4.*, which is installed...:
> > > > > 
> > > > >        configure: error: need qt >= 3.2.0
> > > > 
> > > > Um, huh? If it would need Qt 4.*, it would say that you need qt >=
> > > > 4.something. But it says you need qt >= 3.2.0, so qt-meta
> > > > 3.3.8b-r2 (which I have installed) would do fine.
> > > > Oh, I just see that this is no longer in portage, my qt-meta:3
> > > > comes from the kde-sunset overlay.
> > > > 
> > > > Maybe having Qt4 installed with the qt3support USE flag would
> > > > work, but I doubt it. Qt4 is very different from Qt3.
> > > 
> > > my understanding is that qt3support gives run-time support only 
> > > for apps built against qt3 but running under qt4 (i.e it's just a
> > > simple run-time wrapper around API calls).
> > > 
> > > But qt3support cannot be used to built against qt4
> > > 
> > > -- 
> > > Alan McKinnnon
> > > alan.mckinnon@gmail.com
> > > 
> > > 
> > 
> > So, if QT3 is removed from protage, and museseq which still is in
> > portage seems only to build agains qt3, I see a contradiction here...
> 
> But media-sound/museseq is NOT in the portage tree. If you have it,
> then it comes from an overlay, or from a local ebuild that you maintain.
> 
> If museseq requires qt3, then the maintainer of the overlay (or you)
> must provide qt3 or provide documentation about which overlay it is in.
> 
> IIRC you can find qt3 in kde-sunset
> 
> Either way it looks like a maintainer mistake
> 
> > May be on my system there somewhere leftovers from ancient time,
> > when qt3 needs some additional environment variables or such (?)...
> > what would it be...where I can I look for such settings?
> 
> 
> 
> -- 
> Alan McKinnnon
> alan.mckinnon@gmail.com
> 
> 

Ooops! Sorry, I was mislead by some numbering "[1]" is used
for installs coming from pro-audio overlay and not "(1)" as I
thought.

Nonetheless, still wondering whats going on here...

Still investigating...

Best regards,
mcc

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Alex Schuster]

meino.cramer@gmx.de writes:

> So, if QT3 is removed from protage, and museseq which still is in
> portage seems only to build agains qt3, I see a contradiction here...

No, it has already been removed from portage two years ago [1], because it
still depends on Qt3. So your version probably comes from the proaudio
overlay.

What about trying the new ebuild for musesq-2.0 [2]?

[1] http://www.gossamer-threads.com/lists/gentoo/dev/206852
[2] http://www.mail-archive.com/proaudio@lists.tuxfamily.org/msg04170.html

	Wonko

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[meino.cramer]

Alex Schuster <wonko@wonkology.org> [12-02-18 16:44]:
> meino.cramer@gmx.de writes:
> 
> > So, if QT3 is removed from protage, and museseq which still is in
> > portage seems only to build agains qt3, I see a contradiction here...
> 
> No, it has already been removed from portage two years ago [1], because it
> still depends on Qt3. So your version probably comes from the proaudio
> overlay.
> 
> What about trying the new ebuild for musesq-2.0 [2]?
> 
> [1] http://www.gossamer-threads.com/lists/gentoo/dev/206852
> [2] http://www.mail-archive.com/proaudio@lists.tuxfamily.org/msg04170.html
> 
> 	Wonko
> 

The mail at [2] is of 10.2011. If I am not totally wrong here I should
have the ebuild already on my system. I am doing updates regularily...

?

Best regards,
mcc

Re: [gentoo-user] [OT] Still trying to compile hydrogen

[Alex Schuster]

meino.cramer@gmx.de writes:

> Alex Schuster <wonko@wonkology.org> [12-02-18 16:44]:

> > What about trying the new ebuild for musesq-2.0 [2]?
> > 
> > [1] http://www.gossamer-threads.com/lists/gentoo/dev/206852
> > [2]
> > http://www.mail-archive.com/proaudio@lists.tuxfamily.org/msg04170.html
> > 
> > 	Wonko
> > 
> 
> The mail at [2] is of 10.2011. If I am not totally wrong here I should
> have the ebuild already on my system. I am doing updates regularily...

Well, but which version are you actually emerging?

I just added the pro-audio overlay to check for myself. emerge museseq
wants to build version 1.0.1. Which fails, aparrently it tries to write
to /usr/qt/3/etc/settings/ which is not allowed:

ACCESS DENIED  open_wr:      /usr/qt/3/etc/settings/.qt_plugins_3.3rc.lock
ISE:write_logfile unable to append logfile
ISE open_wr(/usr/qt/3/etc/settings/.qt_plugins_3.3rc.lock): Permission
denied abs_path: /usr/qt/3/etc/settings/.qt_plugins_3.3rc.lock
        res_path: /usr/qt/3/etc/settings/.qt_plugins_3.3rc.lock
/usr/lib64/libsandbox.so(+0x3832)[0x7fb1c5cbb832]
/usr/lib64/libsandbox.so(+0x38ab)[0x7fb1c5cbb8ab]
/usr/lib64/libsandbox.so(+0x4d8d)[0x7fb1c5cbcd8d]
/usr/lib64/libsandbox.so(open64+0xad)[0x7fb1c5cc0a4d]
/usr/qt/3/lib64/libqt-mt.so.3(+0x5c79cd)[0x7fb1c58279cd]
/usr/qt/3/lib64/libqt-mt.so.3(_ZN16QSettingsHeading4readERK7QString+0x5a)[0x7fb1c582973a]
/usr/qt/3/lib64/libqt-mt.so.3(_ZN16QSettingsPrivate9readGroupEv+0x6ac)[0x7fb1c582b64c]
/usr/qt/3/lib64/libqt-mt.so.3(_ZN9QSettings9readEntryERK7QStringS2_Pb+0x17e)[0x7fb1c582cf3e]
/usr/qt/3/lib64/libqt-mt.so.3(_ZN9QSettings13readListEntryERK7QStringPb+0x2e)[0x7fb1c582d5ce]
/usr/qt/3/lib64/libqt-mt.so.3(_ZN11QComLibrary22createInstanceInternalEv+0x2c2)[0x7fb1c57f2a62]
/proc/4891/cmdline: /usr/qt/3/bin/uic -L ../../muse/widgets -o
organguibase.cpp -impl organguibase.h organguibase.ui 

make[5]: *** [organguibase.lo] Aborted

But with FEATURES="-sandbox -usersandbox" emerge museseq it builds fine.
1.9999 and 2.9999 seem to be written for Qt4, but subversion is unable to
check out the sources. Maybe this project is just dead?

But add kde-sunset to your overlays and emerge qt-meta:3, and it should
work.

	Wonko