Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Encountered error when building ARM toolchain (sed)
Date: Sat, 26 Apr 2008 15:31:39 +0200	[thread overview]
Message-ID: <012a01c8a7a8$73e04100$020514ac@atmel.com> (raw)
In-Reply-To: 326f33790804251043x18a84ea6wbd5ebea1385b206d@mail.gmail.com


>> Hi everyone,
>>
>> After successfully doing a build for an x86 platform, I am now attempting
>> to build for an ARM platform. After about half an hour into the build
>> process I encountered the error:
>>
>> /root/buildroot/toolchain_build_arm/bin/sed -i -e
>> 's,^EXTRA_VERSION=.*,EXTRA_VERSION==""."4""",g'
>> /root/buildroot/toolchain_build_arm/bin/sed: no input files
>>
>> Does anyone happen to know what this error is referring to? I understand
>> that the editor sed requires an input stream where it performs text
>> transformations, but why am I getting "no input files" here? Is the syntax
>> for the line above that's being passed for sed not correct? Any tips on how
>> to fix this? Thanks a lot for looking into this.
>>
>

Your problem is because you did not specify a valid linux configuration file.
This means that BR2_<xxx>_KCONFIG is empty and 
"sed  <script> $(BR2_<xxx>_KCONFIG)" becomes 
"sed  <script>"

Best Regards
Ulf Samuelsson

      parent reply	other threads:[~2008-04-26 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25  4:33 [Buildroot] Encountered error when building ARM toolchain (sed) Arun Reddy
2008-04-25 17:43 ` Arun Reddy
     [not found]   ` <46a136670804251132g3b77c228i4a8e5e9c744f7f28@mail.gmail.com>
2008-04-25 18:36     ` John Voltz
2008-04-25 18:47       ` Arun Reddy
2008-04-26 13:31   ` Ulf Samuelsson [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='012a01c8a7a8$73e04100$020514ac@atmel.com' \
    --to=ulf.samuelsson@atmel.com \
    --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