Hi all,
> BTW, to the best of my knowledge, dynamic linking does *not* require -fPIC!
> It just so happens that if you compile with -fPIC then some amount of
> memory can be saved if the dynamic object is shared by different processes.
> Which is an unlikely situation for all dynamic objects that
My prcessor is AMD. The package I downloaded is for the i686. I have a i386
processor. Should I download the x86 Debian packages for i386?
From: Christian Thaeter <[EMAIL PROTECTED]>
Reply-To: cinelerra@skolelinux.no
To: cinelerra@skolelinux.no
CC: Frank Mejia <[EMAIL PROTECTED]>
Subject: Re:
On 2007-04-27 22:10, Dennis Schulmeister wrote:
> Hi,
>
> Like I told in my first message I'm trying to run Cinelerra 2.1CV on a 2
> GHz, 1GiB RAM IA-32 AthlonXP Machine on Ubuntu 7.04 real-time.
>
> Now I wanted to ask for general opinion what performance I can expect.
> Although there are worki
Hi,
Like I told in my first message I'm trying to run Cinelerra 2.1CV on a 2
GHz, 1GiB RAM IA-32 AthlonXP Machine on Ubuntu 7.04 real-time.
Now I wanted to ask for general opinion what performance I can expect.
Although there are working binary drivers with proper OpenGL support for
my NVIDIA car
On Thursday 26 April 2007 08:10, Graham Evans wrote:
> /usr/bin/ld: ffmpeg/libavcodec/.libs/libavcodec.a(cputest.o): relocation
> R_X86_64_32 against `a local symbol' can not be used when making a
> shared object; recompile with -fPIC
> ffmpeg/libavcodec/.libs/libavcodec.a(cputest.o): could not rea
Hello,
I switched from Ubuntu 6.10 (i386) to Gentoo (amd64) a few weeks ago and
managed to compile revision 1008 succesfully with these ./configure
options:
./configure --prefix=/usr --with-buildinfo=svn/recompile --enable-mmx
--enable-3dnow --with-external-ffmpeg
I did the distro switch because
just wanted to point out: the problem of some objects to be liked dynamically
but not beeing built with -fPIC is the most common source of build problems
on x86_64. I learned to look at this first when problems pop up: are really
all (note all) parts to be linked in built with -fPIC ??
Herm
Martin Ellison wrote:
That's a link step, so the compiler options are not going to help there.
But you might (a) Google for all these messages, (b) check the wikis
and (c) trawl through any posts to this list. As I remember I had the
same R_X86_64_32S error a few weeks ago. I think I got aroun
On 26/04/07, Anne Tennies <[EMAIL PROTECTED]> wrote:
I have a 2GB Athlon 64 3500+ and I'm running Cin 2.1CV ...
I am detecting a pattern here?
Regards,
Martin
That's a link step, so the compiler options are not going to help there.
But you might (a) Google for all these messages, (b) check the wikis and (c)
trawl through any posts to this list. As I remember I had the same
R_X86_64_32S error a few weeks ago. I think I got around it by using the
externa
I have a 2GB Athlon 64 3500+ and I'm running Cin 2.1CV on Ubuntu Feisty
(although I've had the same problems under Edgy)
A couple questions:
1. Has anyone figured out how to display audio waveforms when they're
not showing? I get to a point in my projects, and the audio flatlines,
despite havin
just wanted to point out: the problem of some objects to be liked dynamically
but not beeing built with -fPIC is the most common source of build problems
on x86_64. I learned to look at this first when problems pop up: are really
all (note all) parts to be linked in built with -fPIC ??
I thi
12 matches
Mail list logo