From: Meino.Cramer@gmx.de
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] issues with RPI3
Date: Sat, 30 Jul 2016 11:18:38 +0200 [thread overview]
Message-ID: <20160730091838.GE4615@solfire> (raw)
In-Reply-To: <B8A5072B-00A0-46D0-886F-75C496BC613A@gmail.com>
Yeah! Good news! :)
Have a nice weekend!
Best regards,
Meino
Herminio Hernandez Jr. <herminio.hernandezjr@gmail.com> [16-07-30 11:12]:
> The problem was with the SSD I made. I deleted it and rebuilt. Now all is working. I am currently updating @world.
>
> Sent from my iPhone
>
> > On Jul 30, 2016, at 1:56 AM, Meino.Cramer@gmx.de wrote:
> >
> > Herminio Hernandez, Jr. <herminio.hernandezjr@gmail.com> [16-07-30 06:32]:
> >> I have gentoo on my RPI3. I am running into issues with the install. I
> >> cannot emerge anything and some commands will not run. When I emerge I get
> >> warnings that bzip2 cannot be found. However I see the file is /usr/bin.
> >> Here are some examples
> >>
> >> localhost ~ # bzip2
> >>> -bash: /usr/bin/bzip2: No such file or directory
> >>> localhost ~ # whereis bzip2
> >>> bzip2: /usr/bin/bzip2 /bin/bzip2 /usr/share/man/man1/bzip2.1
> >>> /usr/share/man/man1/bzip2.1.gz
> >>> localhost ~ # file bzip2
> >>> bzip2: cannot open `bzip2' (No such file or directory)
> >>> localhost ~ # file /usr/bin/bzip2
> >>> /usr/bin/bzip2: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),
> >>> dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 2.6.27,
> >>> BuildID[sha1]=1e1317befeb837f9059eacbef1ca926a4b4f246c, stripped
> >>> localhost ~ # ld /usr/bin/bzip2
> >>> ld: warning: cannot find entry symbol _start; defaulting to 00011300
> >>> localhost ~ # ldd /usr/bin/bzip2
> >>> /usr/bin/ldd: line 116: /usr/bin/bzip2: No such file or directory
> >>
> >> I used the following stage 3: stage3-armv7a_hardfp-20160523.tar.bz
> >>
> >> Here is my *emerge info* <http://pastebin.com/mgMJ2mBa>
> >>
> >> I tried emerging strace and that failed here is the *build log*
> >> <http://pastebin.com/yud95Y3H>
> >>
> >> Any thoughts?
> >
> > Hi,
> >
> > check the output of
> >
> > echo $PATH
> >
> > of root and check, whether it contains the directories in which
> > the binaries could be found, which cannot be executed.
> >
> > HTH!
> > :)
> >
> > Best regards,
> > Meino
> >
> >
> >
> >
>
prev parent reply other threads:[~2016-07-30 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 4:25 [gentoo-embedded] issues with RPI3 Herminio Hernandez, Jr.
2016-07-30 8:56 ` Meino.Cramer
2016-07-30 9:01 ` Herminio Hernandez Jr.
2016-07-30 9:18 ` Meino.Cramer [this message]
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=20160730091838.GE4615@solfire \
--to=meino.cramer@gmx.de \
--cc=gentoo-embedded@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