Hi,

I have the same problem.


> On Thu, Nov 07, 2002 at 11:27:34PM +0100, Uwe Martin wrote:
>> i'm getting this:
>> 
>> -------------------------------
>> /bin/sh ../../../libtool --mode=link gcc  -O4 -fomit-frame-pointer -mcpu=i686 
>> -march=i686 -ffast-math -D_GNU_SOURCE -D_REENTRANT  -D_LARGEFILE_SOURCE 
>> -D_FILE_OFFSET_BITS=64    -o libavcodeci386.la   fdct_mmx.lo idct_mmx.lo 
>> cputest.lo dsputil_mmx.lo idct_mmx.lo motion_est_mmx.lo mpegvideo_mmx.lo 
>> simple_idct_mmx.lo  -lnsl -ldl
>> ----> rm -fr .libs/libavcodeci386.la .libs/libavcodeci386.* 
>> .libs/libavcodeci386.*
>> (cd . && ln -s fdct_mmx.lo fdct_mmx.lo)
>> (cd . && ln -s idct_mmx.lo idct_mmx.lo)
>> (cd . && ln -s cputest.lo cputest.lo)
>> (cd . && ln -s dsputil_mmx.lo dsputil_mmx.lo)
>> (cd . && ln -s idct_mmx.lo idct_mmx.lo)
>> ln: ?idct_mmx.lo?: Datei existiert
>> make[3]: *** [libavcodeci386.la] Fehler 1
> 
> this looks more like bug in autotool -

autotool? Now idea what this is.
I am using SuSE 8.0 with
autoconf-2.54-0
automake-1.7-0
libtool-1.4.2-188

I also tried SuSE 8.1


> 
> have you been trying this with fresly unpacked tar.gz configure avifile ?
> 
>> .lo files is not correct. the problem lies in ffmpeg/libavcodec/i386/Makefile
>> I never workd with makefiles bigger than 10 lines, so i can't fix it.
> 
> 
> try make clean   & make

tried it with a new tarball (rpm build)

The only strange thing I found during configure was:

> avifile configure options: --prefix=/usr
> checking build system type... i686-suse-linux
> checking host system type... i686-suse-linux
> checking target system type... i686-suse-linux
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /tmp/rpm-rainer/BUILD/avifile0.7-0.7.21/admin/missing: Unknown `--run' option
> Try `/tmp/rpm-rainer/BUILD/avifile0.7-0.7.21/admin/missing --help' for more 
>information
> configure: WARNING: `missing' script is too old or missing

But I can't change that, since missing is in the avifile tarball.


And I tried it with the 20021122 release.


Any hints?

rgds, Rainer

Attachment: msg04211/pgp00000.pgp
Description: PGP signature

Reply via email to