From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ffmpeg - fails to compile on amd64
Date: Mon, 12 Dec 2011 14:52:31 -0500 [thread overview]
Message-ID: <CA+czFiDai+veyAGOs9HMAOH9s98aDjvN033PHb2F1qg1y+hfbw@mail.gmail.com> (raw)
In-Reply-To: <20111212192815.GT3810@syscon4.inet>
On Mon, Dec 12, 2011 at 2:28 PM, Joseph <syscon780@gmail.com> wrote:
> I"m trying to install "kino" but ffmpeg fails to compile:
>
>>>> Configuring source in
>>>> /var/tmp/portage/media-video/ffmpeg-0.7.8/work/ffmpeg-0.7.8 ...
>
> x86_64-pc-linux-gnu-gcc is unable to create an executable file.
> If x86_64-pc-linux-gnu-gcc is a cross-compiler, use the
> --enable-cross-compile option.
> Only do this if you know what cross compiling means.
> C compiler test failed.
>
> * ERROR: media-video/ffmpeg-0.7.8 failed (configure phase):
> * (no error message)
> * * Call stack:
> * ebuild.sh, line 56: Called src_configure
> * environment, line 2680: Called die
> * The specific snippet of code:
> * ./configure --prefix=/usr --libdir=/usr/$(get_libdir)
> --shlibdir=/usr/$(get_libdir) --mandir=/usr/share/man --enable-shared
> --cc="$(tc-getCC)" $(use_enable static-libs static) ${myconf} || die
> * * If you need support, post the output of 'emerge --info
> =media-video/ffmpeg-0.7.8',
> * the complete build log and the output of 'emerge -pqv
> =media-video/ffmpeg-0.7.8'.
> * The complete build log is located at
> '/var/tmp/portage/media-video/ffmpeg-0.7.8/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/media-video/ffmpeg-0.7.8/temp/environment'.
> * S: '/var/tmp/portage/media-video/ffmpeg-0.7.8/work/ffmpeg-0.7.8'
That sounds like a configure-script-time error. I somehow borked up my
gcc profile pretty badly the other day, and the solution turned out to
be re-running:
gcc-config $SOME_PROFILE
where SOME_PROFILE is something you'll find under /etc/env.d/gcc
After that, things worked fine for me again.
(I was in the process of building an email because I was going to ask
this list for help, and I figured out the solution while building the
narrative of things I was trying and testing. It'll probably show up
as another blog post.)
--
:wq
next prev parent reply other threads:[~2011-12-12 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 19:28 [gentoo-user] ffmpeg - fails to compile on amd64 Joseph
2011-12-12 19:32 ` Michael Hampicke
2011-12-12 20:28 ` Joseph
2011-12-12 20:49 ` Michael Hampicke
2011-12-12 20:52 ` Michael Schreckenbauer
2011-12-12 21:09 ` Michael Hampicke
2011-12-12 21:15 ` Michael Hampicke
2011-12-13 0:28 ` [gentoo-user] [SOLVED] " Joseph
2011-12-12 19:52 ` Michael Mol [this message]
2011-12-12 20:23 ` [gentoo-user] " Joseph
2011-12-12 20:29 ` Dale
2011-12-12 20:43 ` Joseph
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=CA+czFiDai+veyAGOs9HMAOH9s98aDjvN033PHb2F1qg1y+hfbw@mail.gmail.com \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox