Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] oprofile "requires" gmp???
Date: Tue, 28 Dec 2010 10:04:57 -0300	[thread overview]
Message-ID: <4D19E079.9030704@zacarias.com.ar> (raw)
In-Reply-To: <9AC3F0E75060224C8BBC5BA2DDC8853A1EAEB132@EXV1.corp.adtran.com>

On 12/27/10 20:12, ANDY KENNEDY wrote:

> Gustavo,
> 
> Where did BR2_STAGING_DIR go?  I'm used to it being under Build Options,
> but I cannot find it.
> 
> In fact, when I put this in and did a make oldconfig it deleted my entry
> in the .config file.

Staging lives now in output/host/usr/tuple/sysroot, it's no longer an
option. We can keep

> Also, the gmp builds now -- they ifdef'ed out the asm code and replaced
> it with a do while (0) C code -- which makes more sense, I think.
> Though, I cannot get oprofile to build still.  The error message is:
> 
> /root/src/PRODUCTION/newbuildroo/buildroot-gz/output/host/usr/mips-unkno
> wn-linux-uclibc/sysroot/usr/lib/libbfd.a(archures.o): relocation
> R_MIPS_HI16 against `__gnu_local_gp' can not be used when making a
> shared object; recompile with -fPIC
> /root/src/PRODUCTION/newbuildroo/buildroot-gz/output/host/usr/mips-unkno
> wn-linux-uclibc/sysroot/usr/lib/libbfd.a: could not read symbols: Bad
> value

Oh, bad mips.
Ok, we need a shared libbfd, i was hoping to get away with a static one
but it seems not.
Fixed in git, pull again and retry.

> . . . and before you say anything, yes I build as root ;).

Please don't, things should work and are far less risky without root.

> You want me to work these issues with you off-list until we (ur, you)
> get it fixed, or shall I trim just reply to the list (removing the
> /root/src etc and making it look like it is in a user's dir).
> 
> I don't mind either way.
> 
> I'm gone for the evening.  I'll catch up with you in the morning.  Enjoy
> the long hours of sunlight and warm temperatures!!!
> 
> Andy 

Keep copying the list, maybe someone else is interested in this or can
chime in with an idea.

  parent reply	other threads:[~2010-12-28 13:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23  4:47 [Buildroot] oprofile "requires" gmp??? ANDY KENNEDY
2010-12-23  7:27 ` Thomas Petazzoni
2010-12-23 19:03   ` ANDY KENNEDY
2010-12-24  8:05     ` Thomas Petazzoni
2010-12-27 18:15       ` ANDY KENNEDY
2010-12-27 18:15         ` Gustavo Zacarias
2010-12-27 18:18           ` Gustavo Zacarias
     [not found]             ` <9AC3F0E75060224C8BBC5BA2DDC8853A1EAEB132@EXV1.corp.adtran.com>
2010-12-28 13:04               ` Gustavo Zacarias [this message]
2010-12-28 16:19                 ` [Buildroot] oprofile "requires" gmp??? Slight fork: BR2_STAGING_DIR ANDY KENNEDY
2010-12-28 21:21                   ` Gustavo Zacarias
2010-12-28 22:31                     ` ANDY KENNEDY
2010-12-29 10:57                     ` Thomas Petazzoni
2010-12-29 11:21                       ` Peter Korsgaard
2010-12-29 21:02                 ` [Buildroot] oprofile "requires" gmp??? ANDY KENNEDY
2010-12-29 21:10                   ` Peter Korsgaard
2010-12-29 21:54                     ` ANDY KENNEDY
2010-12-29 22:01                       ` Gustavo Zacarias
2010-12-29 22:41                 ` ANDY KENNEDY
2010-12-29 23:26                 ` ANDY KENNEDY

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=4D19E079.9030704@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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