11 Sep
2006
11 Sep
'06
1:01 p.m.
Hi.
After Reason :), I encounter another problem with GCC 4.1, with
Muse. Apparately I'm not alone, because there's the same probleme with
Muse 0.8.1a in the pro-audio overlay :
http://www.mail-archive.com/proaudio@lists.tuxfamily.org/msg00438.html
What is weird is that I encounter exactly the same problem with
the « mainstream » version, the one in the normal branch of gentoo :
/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/../../../../i686-pc-linux-gnu/bin/ld:
cannot find -lwine_unicode
collect2: ld returned 1 exit status
make[4]: *** [muse] Erreur 1
make[4]: Leaving directory `/var/tmp/portage/museseq-0.8.1-r1/work/muse-0.8.1/muse'
make[3]: *** [all-recursive] Erreur 1
I try to compile Muse this way, to add lash support :
~ > emerge -vp museseq
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] media-sound/museseq-0.8.1-r1 USE="X lash* -debug -doc" 0
kB
I have seen nothing like that in the bug reports of Gentoo, of
course I can post one but if I could have an advice or something
before... There's a CVS version, hard masked, in the overlay but I'm not
really found of CVS versions as I use Muse very intensively, so I haven't
tried it. Maybe am I wrong ?
Thanks :).
Y.
11 Sep
11 Sep
1:49 p.m.
Hi Yves,
On Monday 11 September 2006 17:01, Yves Potin wrote:
Hi.
After Reason :), I encounter another problem with GCC 4.1, with
Muse. Apparately I'm not alone, because there's the same probleme with
Muse 0.8.1a in the pro-audio overlay :
http://www.mail-archive.com/proaudio@lists.tuxfamily.org/msg00438.html
What is weird is that I encounter exactly the same problem with
the « mainstream » version, the one in the normal branch of gentoo :
/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/../../../../i686-pc-linux-gnu/bin/ld:
cannot find -lwine_unicode
collect2: ld returned 1 exit status
make[4]: *** [muse] Erreur 1
make[4]: Leaving directory
`/var/tmp/portage/museseq-0.8.1-r1/work/muse-0.8.1/muse' make[3]: ***
[all-recursive] Erreur 1
I try to compile Muse this way, to add lash support :
~ > emerge -vp museseq
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] media-sound/museseq-0.8.1-r1 USE="X lash* -debug -doc" 0
kB
I have seen nothing like that in the bug reports of Gentoo, of
course I can post one but if I could have an advice or something
before... There's a CVS version, hard masked, in the overlay but I'm not
really found of CVS versions as I use Muse very intensively, so I haven't
tried it. Maybe am I wrong ?
Thanks :).
Does this build enable vst support for muse? Vaguely I recall that vst support
requires some specific version of wine. But I could be wrong, it was a long
time since I tried vst with muse.
The error must be wine related but it's hard to give any other clues. I
suspect it is a gentoo issue.
/Robert
Y.
--
http://spamatica.se/musicsite/
12 Sep
12 Sep
5:35 a.m.
Yves Potin wrote:
Le 11 Sep à 17:51, Robert Jonsson ecrivait:
Hi,
I think I know the cause of the problem:
The configure script is checking for FST via libfst.pc
Which still will be installed with >=fst-1.7 in the proaudio gentoo overlay
This behavior is wrong as >=fst-1.7 is not compatible to fst/libfst-1.6
--> libfst.pc pulls -lwine_unicode as dependency
So I'll release a new ebuild for fst which will not install libfst.pc
But I think the muse configure script should not check for fst presence if
--disable-vst is selected
Greetz Frieder
Does this build enable vst support for muse?
Hi Robert.
This build fails with or without vst support in any version...
Y.
6:22 a.m.
Frieder Bürzele wrote:
Yves Potin wrote:
sync the overlay and try:
emerge fst =museseq-0.8.1a
hth
Greetz Frieder
Le 11 Sep à 17:51, Robert Jonsson ecrivait:
Hi,
I think I know the cause of the problem:
The configure script is checking for FST via libfst.pc
Which still will be installed with >=fst-1.7 in the proaudio gentoo
overlay
This behavior is wrong as >=fst-1.7 is not compatible to fst/libfst-1.6
--> libfst.pc pulls -lwine_unicode as dependency
So I'll release a new ebuild for fst which will not install libfst.pc
But I think the muse configure script should not check for fst
presence if
--disable-vst is selected
Greetz Frieder Does this build enable vst support for muse?
Hi Robert. This build fails with or without vst
support in any version...
Y.
1:12 p.m.
Le 12 Sep à 10:22, Frieder Bürzele ecrivait:
sync the overlay and try:
emerge fst =museseq-0.8.1a
It works perfectly :
[I--] [ ] media-libs/fst-1.8-r3 ()
[I--] [ ] media-sound/museseq-0.8.1a (0)
As far as I see, without having testing this build of Muse
intensively, it works. It's a really great pleasure to have such a
support from so nice people, a great thank you :).
Cheers,
Y.
13 Sep
13 Sep
5:03 a.m.
Le 12 Sep à 10:22, Frieder Bürzele ecrivait:
sync the overlay and try:
emerge fst =museseq-0.8.1a
Hi.
Well, after testing more carefully, I notice that I can't have vst
support in Muse. I have this in my package.use :
media-sound/museseq -lash vst
After compiling it a few times, I've finaly noticed this :
>> Emerging (1 of 1) media-sound/museseq-0.8.1a
to /
* muse-0.8.1a.tar.gz MD5 ;-) ...[ ok ]
* muse-0.8.1a.tar.gz RMD160 ;-) ...[ ok ]
* muse-0.8.1a.tar.gz SHA1 ;-) ...[ ok ]
* muse-0.8.1a.tar.gz SHA256 ;-) ...[ ok ]
* muse-0.8.1a.tar.gz size ;-) ...[ ok ]
* checking ebuild checksums ;-) ...[ ok ]
* checking auxfile checksums ;-) ...[ ok ]
* checking miscfile checksums ;-) ...[ ok ]
* checking muse-0.8.1a.tar.gz ;-) ...[ ok ]
>> Unpacking source...
>> Unpacking muse-0.8.1a.tar.gz to /var/tmp/portage/museseq-0.8.1a/work
>> Source unpacked.
>> Compiling source in /var/tmp/portage/museseq-0.8.1a/work/muse-0.8.1
>> ...
* vst useflag is disabled due segfault
automake version: 1.9.6 (ok)
autoconf version: 2.59 (ok)
libtool version: 1.5.22 (ok)
pkg-config: /usr/bin/pkg-config
pkg-config version: 0.20 (ok)
Then the script and the whole build continues running without a
problem. If I run the configure manually, it gives me this :
checking for JACK... yes
configure: WARNING: LASH support is disabled
checking for FST... configure: creating ./config.status
config.status: creating Makefile
config.status: creating m4/Makefile
config.status: creating doc/Makefile
The script echoes no answer about FST, for me this is weird. Then
this :
MusE configured
using rtcap: no
LASH support: no
setuid root install: no
setuid root build: no
VST/win support: no
My version of fst :
[I--] [ ] media-libs/fst-1.8-r3
And wine :
[I--] [ ~] app-emulation/wine-0.9.20
I'm absolutely not in a hurry regarding to this, as MIDI Thru works
perfectly to communicate between Muse and VST plugins, but if this problem
can find a solution, maybe should it be useful for others...
Thanks in advance,
Yves.
2:20 p.m.
Hi,
On Wednesday 13 September 2006 09:03, Yves Potin wrote:
Le 12 Sep à 10:22, Frieder Bürzele ecrivait:
Again, it was a while since I tried so I may be wrong, but as I recall fst
1.8/1.7 is quite different from the older versions, which is what MusE
supports. It is quite unfortunate that their version numbering is
consecutive.
I think I tried fixing one of the versions for muse at one time but gave up.
Btw, the vst check is changed in muse cvs now such that it's only performed
when --enable-vst is added.
/Robert
sync the overlay and try:
emerge fst =museseq-0.8.1a
Hi.
Well, after testing more carefully, I notice that I can't have vst
support in Muse. I have this in my package.use :
media-sound/museseq -lash vst
After compiling it a few times, I've finaly noticed this :
--
http://spamatica.se/musicsite/
>> Emerging (1 of 1)
media-sound/museseq-0.8.1a to /
* muse-0.8.1a.tar.gz MD5 ;-) ...[ ok ]
* muse-0.8.1a.tar.gz RMD160 ;-) ...[ ok ]
* muse-0.8.1a.tar.gz SHA1 ;-) ...[ ok ]
* muse-0.8.1a.tar.gz SHA256 ;-) ...[ ok ]
* muse-0.8.1a.tar.gz size ;-) ...[ ok ]
* checking ebuild checksums ;-) ...[ ok ]
* checking auxfile checksums ;-) ...[ ok ]
* checking miscfile checksums ;-) ...[ ok ]
* checking muse-0.8.1a.tar.gz ;-) ...[ ok ]
>> Unpacking source...
>> Unpacking muse-0.8.1a.tar.gz to /var/tmp/portage/museseq-0.8.1a/work
>> Source unpacked.
>> Compiling source in /var/tmp/portage/museseq-0.8.1a/work/muse-0.8.1
>> ...
* vst useflag is disabled due segfault
automake version: 1.9.6 (ok)
autoconf version: 2.59 (ok)
libtool version: 1.5.22 (ok)
pkg-config: /usr/bin/pkg-config
pkg-config version: 0.20 (ok)
Then the script and the whole build continues running without a
problem. If I run the configure manually, it gives me this :
checking for JACK... yes
configure: WARNING: LASH support is disabled
checking for FST... configure: creating ./config.status
config.status: creating Makefile
config.status: creating m4/Makefile
config.status: creating doc/Makefile
The script echoes no answer about FST, for me this is weird. Then
this :
MusE configured
using rtcap: no
LASH support: no
setuid root install: no
setuid root build: no
VST/win support: no
My version of fst :
[I--] [ ] media-libs/fst-1.8-r3
And wine :
[I--] [ ~] app-emulation/wine-0.9.20
I'm absolutely not in a hurry regarding to this, as MIDI Thru works
perfectly to communicate between Muse and VST plugins, but if this problem
can find a solution, maybe should it be useful for others...
Thanks in advance,
Yves. 
5:41 p.m.
New subject: VST in MusE (was: Re: [linux-audio-user] Muse 0.8.1-r1 with GCC 4.1)
Quoting Robert Jonsson <rj(a)spamatica.se>se>:
Hi,
On Wednesday 13 September 2006 09:03, Yves Potin wrote:
I asked about this same issue on lmuse-user a while ago [0] (got no replies,
though). I understood from my attempts that MusE needs fst <= 1.6, and fst-1.6
needs Wine's libwine_unicode.so library. The tricky part is that in recent Wine
releases it has been merged with libwine.so. I can't remember if I tried to
change all mentions of libwine_unicode to libwine in the fst sources. Maybe I
could see if that helps.
I don't know what the last Wine release was that included libwine_unicode.so,
but installing that and fst-1.6 should (in theory) enable VST in MusE.
Personally, I enjoy the cutting edge too much to retreat. :)
Juuso
[0]
http://sourceforge.net/mailarchive/forum.php?thread_id=30173531&forum_i…
----------------------------------------------------------------
This mail sent through L-secure: http://www.l-secure.net/
Le 12 Sep � 10:22, Frieder B�rzele ecrivait:
Again, it was a while since I tried so I may be wrong, but as I recall fst
1.8/1.7 is quite different from the older versions, which is what MusE
supports. It is quite unfortunate that their version numbering is
consecutive.
I think I tried fixing one of the versions for muse at one time but gave up. sync the overlay and try:
emerge fst =museseq-0.8.1a
Hi.
Well, after testing more carefully, I notice that I can't have vst
support in Muse.
14 Sep
14 Sep
7:13 p.m.
New subject: VST in MusE (was: Re: [linux-audio-user] Muse 0.8.1-r1 with GCC 4.1)
Quoting juuso.alasuutari(a)tamperelainen.org:
I asked about this same issue on lmuse-user a while
ago [0] (got no replies,
though). I understood from my attempts that MusE needs fst <= 1.6, and
fst-1.6
needs Wine's libwine_unicode.so library. The tricky part is that in recent
Wine
releases it has been merged with libwine.so. I can't remember if I tried to
change all mentions of libwine_unicode to libwine in the fst sources. Maybe I
could see if that helps.
Update: Apparently there are also other changes in Wine apart from what I
mentioned which prohibit fst-1.6 from compiling. I replaced libwine_unicode.so
with libwine.so and ran make. Here's what it eventually spat out:
make[1]: Entering directory `/usr/src/fst-1.6/fst'
LD_LIBRARY_PATH=":$LD_LIBRARY_PATH" /usr/bin/winebuild -fPIC -o libfst.spec.c
--exe libfst -mgui pthread.o interlocked.o gettid.o libwinelib.o vstwin.o
fstinfofile.o fst.o -L/usr/lib/wine -L/usr/lib/wine -ladvapi32 -lcomdlg32
-lgdi32 -lkernel32 -lodbc32 -lole32 -loleaut32 -lshell32 -luser32 -lwinspool
winebuild: executable must be named via the -F option
make[1]: *** [libfst.spec.c] Error 1
make[1]: Leaving directory `/usr/src/fst-1.6/fst'
make: *** [fst] Error 2
Juuso
----------------------------------------------------------------
This mail sent through L-secure: http://www.l-secure.net/
12 Sep
12 Sep
6:34 a.m.
On Tuesday 12 September 2006 09:34, Frieder Bürzele wrote:
Yves Potin wrote:
Quite correct.
I'll check the build script when I get home.
Regards,
Robert
Le 11 Sep à 17:51, Robert Jonsson ecrivait:
Hi,
I think I know the cause of the problem:
The configure script is checking for FST via libfst.pc
Which still will be installed with >=fst-1.7 in the proaudio gentoo overlay
This behavior is wrong as >=fst-1.7 is not compatible to fst/libfst-1.6
--> libfst.pc pulls -lwine_unicode as dependency
So I'll release a new ebuild for fst which will not install libfst.pc
But I think the muse configure script should not check for fst presence if
--disable-vst is selected Does this build enable vst support for muse?
Hi Robert.
This build fails with or without vst support in any version...
Y.
Greetz Frieder
6706
days inactive
6709
days old
linux-audio-user@lists.linuxaudio.org
10 comments
4 participants
participants (4)
-
Frieder Bürzele -
juuso.alasuutari＠tamperelainen.org -
Robert Jonsson -
yves_p＠nnx.com