Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ross beazley <rossbeazley@lycos.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Cant get mplayer to build on x86 unless CFLAGS has -fomit-frame-pointer
Date: Sun, 23 Sep 2007 07:59:31 +0000	[thread overview]
Message-ID: <183560612499095@lycos-europe.com> (raw)

Has anyone had success getting mplayer to build on an x86. I had to modify the .mk file to include -fomit-frame-pointer in the CFLAGS.

CFLAGS="$(TARGET_CFLAGS) -fomit-frame-pointer" \

Is this required because of something else going on with uclibc I can look into?
Is there a better way to include this CFLAG?
Would it interfere with other builds and make them break?

Buildroot is a great product, well impressed, keep up the good work! :)


cheers

ross

Lycos email has 300 Megabytes of free storage... Get it now at mail.lycos.co.uk

             reply	other threads:[~2007-09-23  7:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-23  7:59 ross beazley [this message]
2007-09-28  6:35 ` [Buildroot] Cant get mplayer to build on x86 unless CFLAGS has -fomit-frame-pointer Adam Hawes

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=183560612499095@lycos-europe.com \
    --to=rossbeazley@lycos.co.uk \
    --cc=buildroot@busybox.net \
    /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