[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140911145259.GB1779@newbook>
Date: Thu, 11 Sep 2014 07:53:00 -0700
From: Isaac Dunham <ibid.ag@...il.com>
To: musl@...ts.openwall.com
Subject: Re: why is there no __MUSL__ macro?
On Thu, Sep 11, 2014 at 02:24:21PM +0200, Jörg Krause wrote:
>
> On 09/11/2014 01:17 PM, Jens wrote:
> >
> >A somewhat limited build of ffmpeg, atleast, works fine with musl:
> >OPTPREFIX=opt/av
> >configure --prefix=/$OPTPREFIX \
> > --enable-gpl\
> > --enable-small --disable-ffplay --disable-ffprobe --disable-ffserver\
> > --enable-libmp3lame\
> > --enable-libx264 \
> > --disable-network --cc=musl-gcc
>
> I'm using a musl cross-compiling toolchain and the limited build even
> without mp3 and x264 fails for me:
>
> ./configure --enable-cross-compile\
> --cross-prefix=/home/joerg/x86_64-linux-musl/bin/x86_64-linux-musl-\
> --arch=x86_64 --target-os=linux\
> --prefix=/home/joerg/test/ffmpeg\
> --enable-gpl\
> --enable-small --disable-ffplay --disable-ffprobe --disable-ffserver\
> --disable-network
> [...]
> make: *** [libavformat/segment.o] Error 1
>
It would be easier to see what's going on if you provided the command line
for compiling that file, plus the rest of the error.
If ffmpeg is showing the "CC ..." message rather than a massive command
line, then run "make V=1".
Thanks,
Iaac Dunham
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
