All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raffucci, Anastasia <Anastasia.Raffucci@jhuapl.edu>
To: buildroot@busybox.net
Subject: [Buildroot] Error when installing to staging directory
Date: Tue, 22 Jan 2019 14:38:24 +0000	[thread overview]
Message-ID: <1548167904630.87035@jhuapl.edu> (raw)
In-Reply-To: <CANQCQpZ-NUo_5cjPFFNiYaJh_SEeTRS8=Kyt4greg7mRTqSdVw@mail.gmail.com>

I am using origin/2017.11.x (0edec09c322744ce1820337487e9bcb9cbcf7ab7) No modifications. 
Not sure what you mean by br2-external. I guess I am not using it. Should I?

-----Original Message-----
From: Matthew Weber [mailto:matthew.weber at collins.com] 
Sent: Monday, January 21, 2019 9:51 PM
To: Raffucci, Anastasia
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] Error when installing to staging directory

Raffucci,


On Mon, Jan 21, 2019 at 3:48 PM Raffucci, Anastasia <Anastasia.Raffucci@jhuapl.edu> wrote:
>
> Buildroot Support Team,
>
>
> I am relatively new to Buildroot and embedded Linux. I used Buildroot once for one project before the one I am working on right now. I have some support from people that are using it around me as well. But here is one problem I am struggling to solve.
>
>
> I am having a problem where the process breaks when trying to install staging directory. I am building out of tree with custom skeleton and overlays. I was able to build root file system once. But when I cloned my project to another location on the same machine, I have this error:
>
>

Which version of buildroot is your build based on and are there any modifications or use of a br2-external?

>
> >>> skeleton-custom  Installing to staging directory
> rsync -a --ignore-times --exclude .svn --exclude .git --exclude .hg 
> --exclude .bzr --exclude CVS --chmod=u=rwX,go=rX --exclude .empty 
> --exclude '*~' /home/user/linux/buildroot/skeleton/ 
> /home/user/linux/buildroot/host/arm-buildroot-linux-gnueabi/sysroot/
> ln -snf lib 
> /home/user/linux/buildroot/host/arm-buildroot-linux-gnueabi/sysroot/li
> b32 ln -snf lib 
> /home/user/linux/buildroot/host/arm-buildroot-linux-gnueabi/sysroot/us
> r/lib32
> ln: failed to create symbolic link 
> '/home/user/linux/buildroot/host/arm-buildroot-linux-gnueabi/sysroot/u
> sr/lib32': No such file or directory
> package/pkg-generic.mk:273: recipe for target 
> '/home/user/linux/buildroot/build/skeleton-custom/.stamp_staging_insta
> lled' failed
> make[1]: *** 
> [/home/user/linux/buildroot/build/skeleton-custom/.stamp_staging_insta
> lled] Error 1
> Makefile:16: recipe for target '_all' failed
> make: *** [_all] Error 2
>
>
>
> I am not reusing any files or directories that get generated by the Buildroot. I also make sure to checkout buildroot git repository to not have any local changes. Unless it is hidden by .gitignore... What could possibly cause this error? As far as I see, everything in /host directory is populated by the Buildroot process. So why the sysroot/usr is missing? Am I missing to export another environment variable for Buildroot that gets set once when you run it first time and always there unchanged? Please help.

Would you mind pastebin sharing your .config, environment values and command line history showing your initial build and then what you do
when you setup your new build location?    That would help give us an
idea of what sequence might be leading up to this error.

Thanks!
Matt

  reply	other threads:[~2019-01-22 14:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 21:47 [Buildroot] Error when installing to staging directory Raffucci, Anastasia
2019-01-22  2:50 ` Matthew Weber
2019-01-22 14:38   ` Raffucci, Anastasia [this message]
2019-01-22 15:41     ` Matthew Weber
2019-01-23 15:38       ` Raffucci, Anastasia
2019-01-23 15:53         ` Sam Voss
2019-01-23 15:42       ` Raffucci, Anastasia
2019-01-23 16:10         ` Matthew Weber
2019-01-23 19:29           ` Raffucci, Anastasia

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=1548167904630.87035@jhuapl.edu \
    --to=anastasia.raffucci@jhuapl.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.