Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] SUDO download error
Date: Wed, 20 Feb 2008 01:18:29 +0100	[thread overview]
Message-ID: <011901c87359$33864420$050514ac@atmel.com> (raw)
In-Reply-To: 1CD05B980C94AC408B37C82BBABAA3E60A342204@mtsexchange.dc.multitech.prv

So even if I get an error like this:

make[1]: Entering directory
`/home/falingtrea/buildroot/build_arm_wchar/at-3.1.10'

/home/falingtrea/buildroot/build_arm_wchar/staging_dir/usr/bin/arm-linux
-uclibc-gcc -Os -pipe
-I/home/falingtrea/buildroot/build_arm_wchar/staging_dir/usr/include
-I/home/falingtrea/buildroot/build_arm_wchar/staging_dir/include
--sysroot=/home/falingtrea/buildroot/build_arm_wchar/staging_dir/
-isysroot /home/falingtrea/buildroot/build_arm_wchar/staging_dir -c -O2
-g -Wall -DHAVE_CONFIG_H -DVERSION=\"3.1.9\" -DETCDIR=\"/etc\"
-DLOADAVG_MX=0.8 -DDAEMON_USERNAME=\"root\" -DDAEMON_GROUPNAME=\"root\"
-DLFILE=\"/var/lib/atjobs/.SEQ\" -Wall atd.c

atd.c:498:2: error: #error "No mail command specified."

make[1]: *** [atd.o] Error 1

And I have a rootfs file, the build is successful?



==> NO, because the rootfs is there from a previous successful build.
        buildroot cannot generate a new root fs, if the makefile exits with 
        an error.

        If you have configured buildroot to build several root fs (jffs2, ext2 etc.)
        then ALL of them have to be present, or the build have failed.

        Any "make[1] ... Error #" like error message means that the build failed.

Best Regards
Ulf Samuelsson 

  reply	other threads:[~2008-02-20  0:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 15:20 [Buildroot] SUDO download error Tim Barr
2008-02-20  0:18 ` Ulf Samuelsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-18 14:27 Tim Barr
2008-02-19  6:33 ` Ulf Samuelsson
2008-02-06 23:06 Tim Barr
2008-01-28 17:41 Tim Barr
2008-01-28 17:36 Tim Barr

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='011901c87359$33864420$050514ac@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