18 Dec
2007
18 Dec
'07
3:27 p.m.
The wine exe connected with this yields and incorrect exe format error. This
had been a problem with dssi-vst but compiling this with recent wine fixed
that. Ardour error persists.
Any ideas.
19 Dec
19 Dec
10:04 p.m.
David Baron wrote:
The wine exe connected with this yields and incorrect
exe format error. This
had been a problem with dssi-vst but compiling this with recent wine fixed
that. Ardour error persists.
Any ideas.
I got the same error. Moreover I could not link ardour with VST=0. Looks
like either the source is broken against glibc or gremlins ate the linker.
David, what's your distro? I'm on Debian Unstable, latest binutils and
stuff.
20 Dec
20 Dec
11:35 a.m.
On Thursday 20 December 2007, Dmitry 'Tanner' Melnichuk wrote:
David Baron wrote:
Same here.
The wine exe connected with this yields and
incorrect exe format error.
This had been a problem with dssi-vst but compiling this with recent wine
fixed that. Ardour error persists.
Any ideas.
I got the same error. Moreover I could not link ardour with VST=0. Looks
like either the source is broken against glibc or gremlins ate the linker.
David, what's your distro? I'm on Debian Unstable, latest binutils and
stuff.
21 Dec
21 Dec
10:53 p.m.
David Baron wrote:
On Thursday 20 December 2007, Dmitry 'Tanner'
Melnichuk wrote:
I've managed to solve the problem by installing
(upgrading) all the
libpcre* stuff. :)
David Baron wrote:
Same here The wine exe connected with this yields and
incorrect exe format error.
This had been a problem with dssi-vst but compiling this with recent wine
fixed that. Ardour error persists.
Any ideas.
I got the same error. Moreover I could not link ardour with VST=0. Looks
like either the source is broken against glibc or gremlins ate the linker.
David, what's your distro? I'm on Debian Unstable, latest binutils and
stuff.
22 Dec
22 Dec
1:45 p.m.
On Saturday 22 December 2007, Dmitry 'Tanner' Melnichuk wrote:
David Baron wrote:
I have the libpcre3, 7.3-2.
There are however also libpcre++ packages which are not conflictin with the
others. Which ones are you referring to and, I assume that ardour needs what
I already have.
On Thursday 20 December 2007, Dmitry
'Tanner' Melnichuk wrote:
I've managed to solve the problem by installing (upgrading) all the
libpcre* stuff. :) David Baron wrote:
Same here The wine exe connected with this yields and
incorrect exe format error.
This had been a problem with dssi-vst but compiling this with recent
wine fixed that. Ardour error persists.
Any ideas.
I got the same error. Moreover I could not link ardour with VST=0. Looks
like either the source is broken against glibc or gremlins ate the
linker.
David, what's your distro? I'm on Debian Unstable, latest binutils and
stuff.
23 Dec
23 Dec
3:42 a.m.
David Baron wrote:
On Saturday 22 December 2007, Dmitry 'Tanner'
Melnichuk wrote:
I've actually installed the lates versions of both libpcre3 and
libpcre++. Than my ardourvst firestarted without recompilation. That's
all I know by the moment.
David Baron wrote:
I have the libpcre3, 7.3-2.
There are however also libpcre++ packages which are not conflictin with the
others. Which ones are you referring to and, I assume that ardour needs what
I already have On Thursday 20 December 2007, Dmitry
'Tanner' Melnichuk wrote:
I've managed to solve the problem by installing (upgrading) all the
libpcre* stuff. :)
David Baron wrote:
> The wine exe connected with this yields and incorrect exe format error.
> This had been a problem with dssi-vst but compiling this with recent
> wine fixed that. Ardour error persists.
>
> Any ideas.
>
I got the same error. Moreover I could not link ardour with VST=0. Looks
like either the source is broken against glibc or gremlins ate the
linker.
David, what's your distro? I'm on Debian Unstable, latest binutils and
stuff.
Same here
9:59 a.m.
On Sunday 23 December 2007, Dmitry 'Tanner' Melnichuk wrote:
David Baron wrote:
OK, installed the ++ flavors as well.
Did not help.
This stuff is libraries for perl-like regular expression parsing. Where did
you get the idea that this was touching ardour-vst? Maybe that will point to
something else.
On Saturday 22 December 2007, Dmitry
'Tanner' Melnichuk wrote:
I've actually installed the lates versions of both libpcre3 and
libpcre++. Than my ardourvst firestarted without recompilation. That's
all I know by the moment. David Baron wrote:
I have the libpcre3, 7.3-2.
There are however also libpcre++ packages which are not conflictin with
the others. Which ones are you referring to and, I assume that ardour
needs what I already have On Thursday 20 December 2007, Dmitry
'Tanner' Melnichuk wrote:
> David Baron wrote:
>> The wine exe connected with this yields and incorrect exe format
>> error. This had been a problem with dssi-vst but compiling this with
>> recent wine fixed that. Ardour error persists.
>>
>> Any ideas.
>
> I got the same error. Moreover I could not link ardour with VST=0.
> Looks like either the source is broken against glibc or gremlins ate
> the linker.
>
> David, what's your distro? I'm on Debian Unstable, latest binutils and
> stuff.
Same here
I've managed to solve the problem by installing (upgrading) all the
libpcre* stuff. :)
10:43 a.m.
David Baron wrote:
On Sunday 23 December 2007, Dmitry 'Tanner'
Melnichuk wrote:
Well, when I tried to debug ardourvst in wine, I got the message
saying
"libglib-2.0.so.0: unresolved reference to pcre_dont_remember_what".
When then I tried to build Ardour without VST support, I got very
similar error but at link time. After a not-so-quick (and totally
unsuccessful) googling I decided to blindly install/update everything
"pcre". And than -- bingo! That's my story.
David Baron wrote:
OK, installed the ++ flavors as well.
Did not help.
This stuff is libraries for perl-like regular expression parsing. Where did
you get the idea that this was touching ardour-vst? Maybe that will point to
something else On Saturday 22 December 2007, Dmitry
'Tanner' Melnichuk wrote:
I've actually installed the lates versions of both libpcre3 and
libpcre++. Than my ardourvst firestarted without recompilation. That's
all I know by the moment.
David Baron wrote:
> On Thursday 20 December 2007, Dmitry 'Tanner' Melnichuk wrote:
>
>> David Baron wrote:
>>
>>> The wine exe connected with this yields and incorrect exe format
>>> error. This had been a problem with dssi-vst but compiling this with
>>> recent wine fixed that. Ardour error persists.
>>>
>>> Any ideas.
>>>
>> I got the same error. Moreover I could not link ardour with VST=0.
>> Looks like either the source is broken against glibc or gremlins ate
>> the linker.
>>
>> David, what's your distro? I'm on Debian Unstable, latest binutils and
>> stuff.
>>
> Same here
>
I've managed to solve the problem by installing (upgrading) all the
libpcre* stuff. :)
I have the libpcre3, 7.3-2.
There are however also libpcre++ packages which are not conflictin with
the others. Which ones are you referring to and, I assume that ardour
needs what I already have
2:09 p.m.
On Monday 24 December 2007, Dmitry 'Tanner' Melnichuk wrote:
David Baron wrote:
I am recompiling without vst right now. So far NO errors but we will see.
Libglib is of course a general object. I doubt is ardour requires pcre
anything, but who knows?
On Sunday 23 December 2007, Dmitry
'Tanner' Melnichuk wrote:
Well, when I tried to debug ardourvst in wine, I got the message saying
"libglib-2.0.so.0: unresolved reference to pcre_dont_remember_what".
When then I tried to build Ardour without VST support, I got very
similar error but at link time. After a not-so-quick (and totally
unsuccessful) googling I decided to blindly install/update everything
"pcre". And than -- bingo! That's my story. David Baron wrote:
OK, installed the ++ flavors as well.
Did not help.
This stuff is libraries for perl-like regular expression parsing. Where
did you get the idea that this was touching ardour-vst? Maybe that will
point to something else On Saturday 22 December 2007, Dmitry
'Tanner' Melnichuk wrote:
> David Baron wrote:
>> On Thursday 20 December 2007, Dmitry 'Tanner' Melnichuk wrote:
>>> David Baron wrote:
>>>> The wine exe connected with this yields and incorrect exe format
>>>> error. This had been a problem with dssi-vst but compiling this
>>>> with recent wine fixed that. Ardour error persists.
>>>>
>>>> Any ideas.
>>>
>>> I got the same error. Moreover I could not link ardour with VST=0.
>>> Looks like either the source is broken against glibc or gremlins ate
>>> the linker.
>>>
>>> David, what's your distro? I'm on Debian Unstable, latest binutils
>>> and stuff.
>>
>> Same here
>
> I've managed to solve the problem by installing (upgrading) all the
> libpcre* stuff. :)
I have the libpcre3, 7.3-2.
There are however also libpcre++ packages which are not conflictin with
the others. Which ones are you referring to and, I assume that ardour
needs what I already have
I've actually installed the lates versions of both libpcre3 and
libpcre++. Than my ardourvst firestarted without recompilation. That's
all I know by the moment.
2:29 p.m.
> I've
managed to solve the problem by installing (upgrading) all the
> libpcre* stuff. :)
I have the libpcre3, 7.3-2.
There are however also libpcre++ packages which are not conflictin with
the others. Which ones are you referring to and, I assume that ardour
needs what I already have
I've actually installed the lates versions of both libpcre3 and
libpcre++. Than my ardourvst firestarted without recompilation. That's
all I know by the moment. I am recompiling without vst right now. So far NO
errors but we will see.
Libglib is of course a general object. I doubt is
ardour requires pcre
anything, but who knows?
So the whole thing build and installed fine. The program starts up, starts
checking the ladspas and all until ...
/usr/local/lib/ardour2/ardour-2.1: symbol lookup
error: /usr/lib/libgnomecanvas-2.so.0: undefined symbol: art_alloc
There is a libart in the builds but nothing bawked.
4:18 p.m.
On Sun, 2007-12-23 at 20:29 +0200, David Baron wrote:
/usr/local/lib/ardour2/ardour-2.1: symbol lookup
error: /usr/lib/libgnomecanvas-2.so.0: undefined symbol: art_alloc
There is a libart in the builds but nothing bawked.
this is caused by an unbelieveable bug in libart_lgpl's headers. I filed
it with GNOME bugzilla months ago, and marked it blocking - it prevents
compilation of any C++ application that uses libart_lgpl.
you need to either backtrack to an older libart_lgpl, or fix the problem
with the headers.
--p
6182
days inactive
6187
days old
linux-audio-user@lists.linuxaudio.org
10 comments
3 participants
participants (3)
-
David Baron -
Dmitry 'Tanner' Melnichuk -
Paul Davis