From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot_defconfig Error
Date: Thu, 26 Dec 2013 16:59:40 +0100 [thread overview]
Message-ID: <20131226155940.GB3398@free.fr> (raw)
In-Reply-To: <CAO8ZbKt9uYRyRutgkMYFS4hY=EYASWEeyEXha4-q+9C6dmDMCw@mail.gmail.com>
Ron, All,
On 2013-12-26 15:50 +0000, Ron Eggler spake thusly:
> About 30min into the compilation, I keep getting a "buildroot_defconfig"
> error that I'm not able to get resolved.
> It looks like this:
> >>> linux 3.2.52 Configuring
> cp "board/synapse/e10/linux-3.12.1-config"
> /etc/E10-buildroot/br2013.11/output/build/linux-3.2.52/arch/arm/configs/buildroot_defconfig
> cp: cannot stat ?board/synapse/e10/linux-3.12.1-config?: No such file or
> directory
That is the real error: the file 'board/synapse/e10/linux-3.12.1-config'
does not exist.
That file does not exist in upstream Buildroot. You did configure
Buildroot to use that file (it's in the Linux sub-menu), but you do not
provide it. If you got your Buildroot config from someone else, then
that someone else forgot to provide you with that file.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-12-26 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 15:50 [Buildroot] buildroot_defconfig Error Ron Eggler
2013-12-26 15:57 ` Thomas Petazzoni
2013-12-26 15:59 ` Yann E. MORIN [this message]
2013-12-27 15:19 ` Ron Eggler
2013-12-27 15:21 ` Ron Eggler
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=20131226155940.GB3398@free.fr \
--to=yann.morin.1998@free.fr \
--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