[FFmpeg-devel] Broken configure causes ffmpeg failing on Solaris

Måns Rullgård mans
Sun Mar 2 01:34:44 CET 2008


pross at xvid.org writes:

> On Sat, Mar 01, 2008 at 06:34:52PM -0500, Rich Felker wrote:
>> On Fri, Feb 29, 2008 at 03:11:26PM -0800, Frank Liu wrote:
>> > Hi there,
>> > 
>> > I took the suggestions from this list:
>> > "man standards" and set the PATH properly
>> > ffmpeg seems to compile fine on my Solaris 10 SPARC box, but the
>> > compiled binary doesn't work.
>> > 
>> > I did some more research and found out ./configure sets up the wrong
>> > endian for the SPARC architecture.
>> > 
>> > Here is the line in "configure":
>> > 
>> > grep -q BIGE $TMPO && enable bigendian
>> > 
>> > With the PATH I have, it is equivalent to
>> > /usr/xpg4/bin/grep -q BIGE $TMPO && enable bigendian
>> > 
>> > that grep never matches, so bigendian doesn't get enabled.
>> > (my guess is only GNU grep can act on binary file?)
>> > 
>> > Even though the compilation went well, the resulting ffmpeg executable
>> > doesn't really work.
>> 
>> This test is invalid anyway. grep requires input to be a text file; a
>> .o file is not valid. Try something like:
>> 
>> tr -cd BIGE < "$TMPO" | grep ...

That should work, assuming the compiler didn't by chance scatter the
bytes B I G E elsewhere in the file.  An alternative might be to send
the file through od and grep the hex output.  This would of course
rely on the data being 4-byte aligned within the file.  I don't know
if any object file format allows non-aligned data.

> IIRC, the -q flag is not supported by the grep shipped with solaris 10.

That makes solaris 10 broken.  The -q flag is standard.

-- 
M?ns Rullg?rd
mans at mansr.com




More information about the ffmpeg-devel mailing list