mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac Dunham <ibid.ag@gmail.com>
To: musl@lists.openwall.com
Subject: Re: why is there no __MUSL__ macro?
Date: Thu, 11 Sep 2014 07:53:00 -0700	[thread overview]
Message-ID: <20140911145259.GB1779@newbook> (raw)
In-Reply-To: <54119475.1090208@posteo.de>


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


  reply	other threads:[~2014-09-11 14:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 11:00 Jörg Krause
2014-09-11 11:09 ` Laurent Bercot
2014-09-11 11:17   ` Szabolcs Nagy
2014-09-11 12:02     ` Jörg Krause
2014-09-11 12:38       ` Szabolcs Nagy
2014-09-11 13:33         ` Jörg Krause
2014-09-11 14:48           ` Szabolcs Nagy
2014-09-11 14:30   ` Christian Neukirchen
2014-09-11 11:17 ` Jens
2014-09-11 12:24   ` Jörg Krause
2014-09-11 14:53     ` Isaac Dunham [this message]
2014-09-12  7:39       ` Jörg Krause
2014-09-11 14:47 ` Natanael Copa
2014-09-12  7:35   ` Jörg Krause
2014-09-12 15:37     ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140911145259.GB1779@newbook \
    --to=ibid.ag@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).