>> Problems seems to be related to 1.0.x on x86 (and as Andrew pointed
>> out, looks like a binutils problem at first glance)
>I missed that comment -- anything I can try? As Chuck Remes noted, it
>looks like the problem is triggered by assembly code.
To quote my earlier reply:
>From: [EMAIL PROTECTED] (Andrew Church)
>To: [EMAIL PROTECTED]
>Subject: Re: [transcode-devel] Re: Compiling transcode
>Date: Fri, 27 Apr 2007 08:52:42 JST
>X-WWMF-Version: [EMAIL PROTECTED]
>Reply-To: transcode Developers Mailing List <[EMAIL PROTECTED]>
>
>>> gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_REENTRANT -DLINUX -I.. -Wall
>>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -g
>>> -O2
>>> -no-cpp-precomp -D_INTL_REDIRECT_MACROS -MT tcmemcpy.lo -MD -MP -MF
>>> .deps/tcmemcpy.Tpo -c tcmemcpy.c -fno-common -DPIC -o .libs/
>>> tcmemcpy.o
>>> /var/tmp//ccMwDlN6.s:43:missing or invalid immediate expression
>>> `0b111'
>>> taken as 0
>
>What version of binutils are you using? (Sorry if you already mentioned
>this--I haven't had a chance to review the thread.) This looks like a
>case of an outdated assembler version not being able to parse binary
>constants.
>
>>> /var/tmp//ccMwDlN6.s:206:Alignment too large: 15. assumed.
>
>This should only happen on x86 if you're compiling to a.out, which is
>ancient, or (again) if your assembler is too old. (On the other hand, the
>use of .balign rather than .align here would avoid such potential trouble,
>and I'll look into making that change on CVS HEAD when I have a chance.)
>
>Note that you can disable assembler code entirely by passing --disable-mmx
>to ./configure (but this can slow transcode down considerably depending on
>what you do with it).
--Andrew Church
[EMAIL PROTECTED]
http://achurch.org/
