Subject: Re: [ecasound] ecasound linking problem
From: S. Massy (firstname.lastname@example.org)
Date: Sat May 06 2000 - 22:48:43 EEST
On Sat, 06 May 2000, Richard A. Smith wrote:
> On Sat, 6 May 2000 03:57:52 -0400, S. Massy wrote:
> >Well, searching through this mailing list I noticed someone had a
> >problem similar to mine. (ecasound compilation bails out at linking
> >stage with tons of "multiple definitions error") BTW, I'm a Debian user too
> >so maybe it's a problem related to the distribution. Whatsoever I
> >would be grateful if any of you could hint me about how I could solve
> >this problem.
> Does sound a little suspect dosen't it. What release of Debian are you
> using? I have been able to get the binary .rpms installed on my system
Basically Slink with glibc and a few other things updated with
packages from potato. I once tried to install ecasound using the
rpm'ed version as you mention but it wouldn't work (was an old
release of ecasound though). The previous releases used to compile,
with some work (it never compiled on its own for me.)
> using alien. Both ecasound and ecawave installed ok. Alien whined about
> some stuff but it dosen't appear to have broken the packages.
> I was able to run ecawave and load up a file. (ecawave segfaulted on me
> while I was playing with it though *grin*)
> I grabbed the latesest developement release of ecawave and tried to
> compile it but received the same type of errors.
> Perhaps we should start looking at the differences between the debian
> library placements/versions and the redhat ones.
Either, this or something's wrong with ld. I'm not overly familiar
with C++ but I thought multiple definitions were allowed in it, is
that right? Is anybody familiar enough with both RH and Debian to
hint about what's going on here?
> Richard A. Smith email@example.com
> "I'd hang out with science kids - they can blow things up!
> I mean , what's cooler than that?"
> - Tori Amos
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <firstname.lastname@example.org>.
-- To unsubscribe send message 'unsubscribe' in the body of the message to <email@example.com>.
This archive was generated by hypermail 2b28 : Sat May 06 2000 - 22:49:27 EEST