17 Aug
2005
17 Aug
'05
12:37 p.m.
I have wine20040505.1-i586 (also the -devel package) installed.
I already got fst working on ubuntu i386.
On suse 9.3 (x86_64) the configure script can't include 'windef.h', even
if it is inside /usr/incude/wine/windows.
Running:
./configure --prefix=/usr --with-wine-include=/usr/include/wine
i get:
checking for windef.h... configure: error: Could not find the Wine
headers (windef.h)
c.
28 Aug
28 Aug
6:41 p.m.
Please help!
c.
I have wine20040505.1-i586 (also the -devel package)
installed.
I already got fst working on ubuntu i386.
On suse 9.3 (x86_64) the configure script can't include 'windef.h', even
if it is inside /usr/incude/wine/windows.
Running:
./configure --prefix=/usr --with-wine-include=/usr/include/wine
i get:
checking for windef.h... configure: error: Could not find the Wine
headers (windef.h)
c.
10:02 p.m.
Cesare Marilungo wrote:
Please help!
c.
>I have wine20040505.1-i586 (also the -devel package) installed.
>
>I already got fst working on ubuntu i386.
>On suse 9.3 (x86_64) the configure script can't include 'windef.h', even
>if it is inside /usr/incude/wine/windows.
>
>Running:
>./configure --prefix=/usr --with-wine-include=/usr/include/wine
>
>i get:
>checking for windef.h... configure: error: Could not find the Wine
>headers (windef.h)
>
>c.
>
>
Cesare,
A couple of ideas: First, and it sounds like you already have verified
this, make sure that exact file is present in that exact directory. If
so, try copying it into the source file directory of fst where you're
compiling it. Finally, you might both copy the file and add #include
"./windef.h" right in the source file that's looking for it.
Frank
29 Aug
29 Aug
11:48 a.m.
running ./autogen.sh I get:
configure.ac:468: warning: underquoted definition of AC_PATH_FILE
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
configure.ac:509: warning: underquoted definition of AC_PATH_HEADER
configure.ac:545: warning: underquoted definition of AC_PATH_LIBRARY
I've already tried copying the windef.h into fst-1.6/include.
c.
Cesare Marilungo wrote:
I have wine20040505.1-i586 (also the -devel package)
installed.
I already got fst working on ubuntu i386.
On suse 9.3 (x86_64) the configure script can't include 'windef.h', even
if it is inside /usr/incude/wine/windows.
Running:
./configure --prefix=/usr --with-wine-include=/usr/include/wine
i get:
checking for windef.h... configure: error: Could not find the Wine
headers (windef.h)
c.
12:01 p.m.
New subject: [linux-audio-user] problem compiling fst under suse 9.3 on AMD64
On Mon, 2005-08-29 at 17:47 +0200, Cesare Marilungo wrote:
running ./autogen.sh I get:
configure.ac:468: warning: underquoted definition of AC_PATH_FILE
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
configure.ac:509: warning: underquoted definition of AC_PATH_HEADER
configure.ac:545: warning: underquoted definition of AC_PATH_LIBRARY
this is just auto-crap version issues. they are only warnings.
I've already tried copying the windef.h into
fst-1.6/include.
an incredibly bad idea. it sounds as if you don't have your wine and/or
wine-devel install done correctly.
--p
2:15 p.m.
New subject: [linux-audio-user] problem compiling fst under suse 9.3 on AMD64
Paul Davis wrote:
On Mon, 2005-08-29 at 17:47 +0200, Cesare Marilungo
wrote:
I know this is a bad idea.
Anyway, I don't know why the configure script doesn't find a file which
is in its search path.
But yes, the problem must be wine. I've already compiled and used your
software, Paul, on other distributions without problems.
So, I'm trying compling wine-20040505 from scratch. No probs with a
32bit linux. But on my suse9.3 for amd64 I get the following error while
making:
interlocked.c:248:3: #error You must implement the interlocked*
functions for your CPU
I guess it is because wine it's not 64bit ready. So how can I force a
32bit build?
c.
running ./autogen.sh I get:
configure.ac:468: warning: underquoted definition of AC_PATH_FILE
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
configure.ac:509: warning: underquoted definition of AC_PATH_HEADER
configure.ac:545: warning: underquoted definition of AC_PATH_LIBRARY
this is just auto-crap version issues. they are only warnings.
I've already tried copying the windef.h into
fst-1.6/include.
an incredibly bad idea. it sounds as if you don't have your wine and/or
wine-devel install done correctly.
--p
3:37 p.m.
New subject: [linux-audio-user] problem compiling fst under suse 9.3 on AMD64
So, I'm trying compling wine-20040505 from
scratch. No probs with a
32bit linux. But on my suse9.3 for amd64 I get the following error while
making:
interlocked.c:248:3: #error You must implement the interlocked*
functions for your CPU
I guess it is because wine it's not 64bit ready. So how can I force a
32bit build?
wine compiles and runs as great as you could ask it to on amd64, but definitely not
20040505 - try 20050725 or newer. xfst compiled out of the box here with WINE of a recent
vintage, just had to had -m32 and a libpath (/usr/lib32) to the makefile.. if you cant
find xfst i think the person to ask is Genesis on freenode (but not totally positive on
that, just that the name Genesis was in the tarball, and i dont think its Phil Collins)..
then theres the fact that youre goign to need 2 jackd's, one running in 32bit land,
and another in 64, and talk to eachother via UDP, if you want to really share audio
between apps from both architectures at once.. how bad do you want to run VST plugins
again?
c.
>--p
>
>
>
>
>
4:18 p.m.
New subject: [linux-audio-user] problem compiling fst under suse 9.3 on AMD64
carmen wrote:
Is this really needed? I thought that
I could talk between 32bit and
64bit applications using jack.
I'm still also having problem with pure data. A x86_64 version from a
rpm gives different (and poorer) audio results from the same patch. The
32bit works but just with OSS. Otherwise i get seg faults.
I understand that my Suse distro comes with alsa libraries for both
architectures.
'Confusion will be my epitaph
As I crawl a cracked and broken path
If we make it
we can all sit back And laugh.
But I fear tomorrow I’ll be crying.'
So, I'm
trying compling wine-20040505 from scratch. No probs with a
32bit linux. But on my suse9.3 for amd64 I get the following error while
making:
interlocked.c:248:3: #error You must implement the interlocked*
functions for your CPU
I guess it is because wine it's not 64bit ready. So how can I force a
32bit build?
wine compiles and runs as great as you could ask it to on amd64, but definitely not
20040505 - try 20050725 or newer. xfst compiled out of the box here with WINE of a recent
vintage, just had to had -m32 and a libpath (/usr/lib32) to the makefile.. if you cant
find xfst i think the person to ask is Genesis on freenode (but not totally positive on
that, just that the name Genesis was in the tarball, and i dont think its Phil Collins)..
then theres the fact that youre goign to need 2 jackd's, one running in 32bit land,
and another in 64, and talk to eachother via UDP, if you want to really share audio
between apps from both architectures at once.. how bad do you want to run VST plugins again?
I need some vst plugins (mostly Crystal synth) to work on some tracks
made under mac.
c.
>--p
>
>
>
>
>
>
4:27 p.m.
New subject: [linux-audio-user] problem compiling fst under suse 9.3 on AMD64
On Mon, 2005-08-29 at 22:17 +0200, Cesare Marilungo wrote:
Is this really needed? I thought that I could talk
between 32bit and
64bit applications using jack.
I'm still also having problem with pure data. A x86_64 version from a
rpm gives different (and poorer) audio results from the same patch.
The 32bit works but just with OSS. Otherwise i get seg faults.
Sounds like a huge pain in the ass for very little gain. Why don't you
just run in 32 bit mode?
Lee
7:06 p.m.
New subject: [linux-audio-user] problem compiling fst under suse 9.3 on AMD64
Lee Revell wrote:
On Mon, 2005-08-29 at 22:17 +0200, Cesare Marilungo
wrote:
I'm using jack 0.99 that came with suse 9.3. I have jack libraries both
in /usr/lib and /usr/lib64. How can I invoke jack in 32 bit mode? I
guess I must compile it with -m32 gcc option and use a different name
for the binary. Is it correct? So why do I have also the 32 bit
libraries (in /usr/lib) (and a package called jack-32bit)?
c.
Is this really needed? I thought that I could talk
between 32bit and
64bit applications using jack.
I'm still also having problem with pure data. A x86_64 version from a
rpm gives different (and poorer) audio results from the same patch.
The 32bit works but just with OSS. Otherwise i get seg faults.
Sounds like a huge pain in the ass for very little gain. Why don't you
just run in 32 bit mode?
Lee
7:35 p.m.
New subject: [linux-audio-user] problem compiling fst under suse 9.3 on AMD64
On Tue, 2005-08-30 at 01:06 +0200, Cesare Marilungo wrote:
Lee Revell wrote:
No, I mean run your whole system in 32 bit mode. Then try 64 again in a
few months when the apps have had a chance to catch up. Otherwise it
seems you're facing quite an uphill battle, unless you know how to port
32 bit apps to 64 bit architectures...
Lee
On Mon, 2005-08-29 at 22:17 +0200, Cesare
Marilungo wrote:
I'm using jack 0.99 that came with suse 9.3. I have jack libraries both
in /usr/lib and /usr/lib64. How can I invoke jack in 32 bit mode? I
guess I must compile it with -m32 gcc option and use a different name
for the binary. Is it correct? So why do I have also the 32 bit
libraries (in /usr/lib) (and a package called jack-32bit)? Is this really needed? I thought that I could talk
between 32bit and
64bit applications using jack.
I'm still also having problem with pure data. A x86_64 version from a
rpm gives different (and poorer) audio results from the same patch.
The 32bit works but just with OSS. Otherwise i get seg faults.
Sounds like a huge pain in the ass for very little gain. Why don't you
just run in 32 bit mode?
Lee
10:19 p.m.
New subject: [linux-audio-user] problem compiling fst under suse 9.3 on AMD64
Lee Revell wrote:
On Tue, 2005-08-30 at 01:06 +0200, Cesare Marilungo
wrote:
I like to think that I'm helping the linux community by testing audio
apps on a less supported platform.
BTW, I got pure data to work, by compiling latest jackd and the testing
version of pd. I guess that the pd patch I was using for testing
'filter_floyd.pd' is a tricky one, in fact it seems to me that it has
been rewritten recently. I can talk with jack and everything.
Now I just need some way to host vst plugins. Everything else works.
c.
Lee Revell wrote:
No, I mean run your whole system in 32 bit mode. Then try 64 again in a
few months when the apps have had a chance to catch up. Otherwise it
seems you're facing quite an uphill battle, unless you know how to port
32 bit apps to 64 bit architectures...
Lee
On Mon, 2005-08-29 at 22:17 +0200, Cesare
Marilungo wrote:
I'm using jack 0.99 that came with suse 9.3. I have jack libraries both
in /usr/lib and /usr/lib64. How can I invoke jack in 32 bit mode? I
guess I must compile it with -m32 gcc option and use a different name
for the binary. Is it correct? So why do I have also the 32 bit
libraries (in /usr/lib) (and a package called jack-32bit)?
Is this really needed? I thought that I could talk
between 32bit and
64bit applications using jack.
I'm still also having problem with pure data. A x86_64 version from a
rpm gives different (and poorer) audio results from the same patch.
The 32bit works but just with OSS. Otherwise i get seg faults.
Sounds like a huge pain in the ass for very little gain. Why don't
you
just run in 32 bit mode?
Lee
5:37 p.m.
carmen wrote:
>then theres the fact that youre goign to need 2 jackd's, one running
>in 32bit land, and another in 64, and talk to eachother via UDP, if
>you want to really share audio between apps from both architectures
>at once..
Cesare Marilungo <cesare(a)poeticstudios.com> writes:
Is this really needed? I thought that I could talk
between 32bit and
64bit applications using jack.
No. We have that on our post-1.0 TODO list, but it's really hard and
won't happen any time soon, if at all.
--
joq
30 Aug
30 Aug
6:19 a.m.
New subject: [linux-audio-user] JACK 32<>64
On Mon, Aug 29, 2005 at 04:42:54PM -0500, Jack O'Quin wrote:
and its quite possibly not necessary, with an asound.conf like this (set your 32 bit apps
to use ALSA):
(As stolen from the ALSA FAQ):
pcm.!default {
type plug
slave { pcm "jack" }
}
pcm.jack {
type jack
playback_ports {
0 alsa_pcm:playback_1
1 alsa_pcm:playback_2
}
capture_ports {
0 alsa_pcm:capture_1
1 alsa_pcm:capture_2
}
}
carmen wrote:
>then theres the fact that youre goign to need 2 jackd's, one running
>in 32bit land, and another in 64, and talk to eachother via UDP, if
>you want to really share audio between apps from both architectures
>at once..
Cesare Marilungo <cesare(a)poeticstudios.com> writes:
Is this really needed? I thought that I could
talk between 32bit and
64bit applications using jack.
No. We have that on our post-1.0 TODO list, but it's really hard and
won't happen any time soon, if at all.
6820
days inactive
6833
days old
linux-audio-user@lists.linuxaudio.org
13 comments
6 participants
participants (6)
-
carmen -
Cesare Marilungo -
Jack O'Quin -
Lee Revell -
Paul Davis -
pirrone