emerge -1 busybox fails

grahn · n00b Joined: 27 Aug 2002 Posts: 64

Hi, I somehow managed to unmerge busybox and now I am unable to re-emerge it

The output of

NathanZachary · Moderator Joined: 30 Jan 2007 Posts: 2605

Can you please post the output of:

grahn · n00b Joined: 27 Aug 2002 Posts: 64

Thank you, I updated my question with the information.

I am afraid it is a general problem. You could just try

NathanZachary · Moderator Joined: 30 Jan 2007 Posts: 2605

I am able to build busybox without a problem on my machine (though it is quite different). You may want to try doing a sync, and then allowing ~$ARCH for at least this one package. If it wants to pull in a bunch of other dependencies for the ~ version, then we'll skip that route. The reason that I wanted to see your emerge --info was to check if you were using ccache. I remember some time ago there was a problem with ccache and busybox.

Cheers,
Nathan Zachary
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---

grahn · n00b Joined: 27 Aug 2002 Posts: 64

The same result with sys-apps/busybox-1.22.1-r1, after syncing and setting ACCEPT_KEYWORDS="~amd64".

v_andal · Guru Joined: 26 Aug 2008 Posts: 541 Location: Germany

It would be interesting to see the /var/tmp/portage/sys-apps/busybox-1.21.0/temp/build.log, actually the part at the end where the actual command producing error is visible.

From the output you have provided, it looks like there's -Werror somewhere that triggers conversion of warnings into errors. I know that version 4.9.1 of gcc causes such behavior, but you use 4.7.3.

Have you tried to compile it with CFLAGS set only to '-O2 -march=native'?

I don't have any problems on my system.

grahn · n00b Joined: 27 Aug 2002 Posts: 64

I tried

i92guboj · Posted: Mon Oct 20, 2014 12:55 pm Post subject:

And if you USE="-savedconfig"?

You don't seem to have one anyway...

grahn · n00b Joined: 27 Aug 2002 Posts: 64

I could try someone else' configfile. Maybe it is the generated default one which causes the problem.

i92guboj · Posted: Mon Oct 20, 2014 1:12 pm Post subject:

Did you try disabling it?

I learnt the hard way that busybox is a picky beast when it comes to custom config while building binaries for android.

grahn · n00b Joined: 27 Aug 2002 Posts: 64

RazielFMX · l33t Joined: 23 Apr 2005 Posts: 835 Location: NY, USA

The config file statement is either informational or a warning and not the actual error. You are, however, failing during the configure phase of the build, which is rather odd.

Can you provide some background? What has prompted you to attempt to rebuild busybox? Did it fail during a world update?

grahn · n00b Joined: 27 Aug 2002 Posts: 64

I played with cross compiling (as root) and at one point I accidentally executed emerge --unmerge busybox.

RazielFMX · l33t Joined: 23 Apr 2005 Posts: 835 Location: NY, USA

Well that's... bad.

Alright, there are a few things we can do, depending on how hardcore you want to get about this.

Personally, if I did this, I would lose the box for a day and do this:

grahn · n00b Joined: 27 Aug 2002 Posts: 64

I will try

i92guboj · Posted: Mon Oct 20, 2014 2:47 pm Post subject:

I doubt it will fix the problem at hand. But in any case it won't do any harm. That's for sure.

RazielFMX · l33t Joined: 23 Apr 2005 Posts: 835 Location: NY, USA

It may very well work. Give it a shot.
_________________
I am not anti-systemd; I am pro-choice. If being the latter makes you feel that I am the former, then so be it.

grahn · n00b Joined: 27 Aug 2002 Posts: 64

I will do that overnight. I will keep you informed. Thanks so far.

v_andal · Guru Joined: 26 Aug 2008 Posts: 541 Location: Germany

Quite possible, there are some environment variables left after cross-compile attempts. These variables mess up the emerge compilation.

krinn · Watchman Joined: 02 May 2003 Posts: 7470

https://bugs.gentoo.org/show_bug.cgi?id=525586#c2
better look for a version using defconfig