[Buildroot] SUDO download error

[Buildroot] SUDO download error

[Tim Barr]

Looks like the sudo website access has changed. It is now
www.sudo.ws/sudo. Courtesan Consulting also changed name to Gratisoft
Inc.
 


Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
 <mailto:tbarr@multitech.com> tbarr at multitech.com 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080128/6290f307/attachment.htm 

[Buildroot] SUDO download error

[Tim Barr]

Also forgot to mention there is a new release version: sudo-1.6.9p12
 
 
----Original Message-----
From: buildroot-bounces@uclibc.org [mailto:buildroot-bounces at uclibc.org]
On Behalf Of Tim Barr
Sent: Monday, January 28, 2008 11:36 AM
To: buildroot at uclibc.org
Subject: [Buildroot] SUDO download error



Looks like the sudo website access has changed. It is now
www.sudo.ws/sudo. Courtesan Consulting also changed name to Gratisoft
Inc.
 



Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
 <mailto:tbarr@multitech.com> tbarr at multitech.com 







 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080128/30807a43/attachment.htm 

[Buildroot] SUDO download error

[Tim Barr]

I modified sudo.mk and was able to get the latest version to download
but now it looks like there are some cross-compile patches that don't
match up. I'm getting into territory that I am totally unfamiliar with
now. I thought maybe I could find version 1.6.8p12 tar file  in the old
directory of the sudo site but there is olnly a 1.6.8 tar file and a
1.6.8p12 patch.
 
Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
 <mailto:tbarr@multitech.com> tbarr at multitech.com


-----Original Message-----
From: buildroot-bounces@uclibc.org [mailto:buildroot-bounces at uclibc.org]
On Behalf Of Tim Barr
Sent: Monday, January 28, 2008 11:41 AM
To: buildroot at uclibc.org
Subject: Re: [Buildroot] SUDO download error


Also forgot to mention there is a new release version: sudo-1.6.9p12
 
 
----Original Message-----
From: buildroot-bounces@uclibc.org [mailto:buildroot-bounces at uclibc.org]
On Behalf Of Tim Barr
Sent: Monday, January 28, 2008 11:36 AM
To: buildroot at uclibc.org
Subject: [Buildroot] SUDO download error



Looks like the sudo website access has changed. It is now
www.sudo.ws/sudo. Courtesan Consulting also changed name to Gratisoft
Inc.
 



Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
 <mailto:tbarr@multitech.com> tbarr at multitech.com 







 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080206/d6e4499c/attachment.htm 

[Buildroot] SUDO download error

[Tim Barr]

Well I reverted the sudo buildroot code and found a copy of
1.6.8p12.tar.gz on a sudo mirror site and downloaded it manually to my
install directory. The next file with an issue was which-2.16.tar.gz. I
manually downloaded this file and got past the error. Then it failed
trying to copy the file at91sam9260pf-flashboot-2.4.bin to directory
/tftpboot, which does not exist on my machine. So I created the
directory and gave it full permissions. Now I have 3 files in the
buildroot/binaries directory (a flashboot .bin, a linux .gz, and a
rootfs .ext2 file). I did seem to get some sort of error though:
 
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

 
Does buildroot tell you whether it finishes? Or do I just assume that if
I see no errors that buildroot was successful? 


Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
 <mailto:tbarr@multitech.com> tbarr at multitech.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080218/ed170033/attachment.htm 

[Buildroot] SUDO download error

[Ulf Samuelsson]

 
> Does buildroot tell you whether it finishes? Or do I just assume that if
> I see no errors that buildroot was successful? 

You succeeded, If you get a root file system in your binaries directory.



Best Regards
Ulf Samuelsson 

[Buildroot] SUDO download error

[Tim Barr]

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?

Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
tbarr at multitech.com



-----Original Message-----
From: Ulf Samuelsson [mailto:ulf.samuelsson at atmel.com] 
Sent: Tuesday, February 19, 2008 12:33 AM
To: Tim Barr; buildroot at uclibc.org
Subject: Re: [Buildroot] SUDO download error


 
> Does buildroot tell you whether it finishes? Or do I just assume that 
> if I see no errors that buildroot was successful?

You succeeded, If you get a root file system in your binaries directory.



Best Regards
Ulf Samuelsson 

[Buildroot] SUDO download error

[Ulf Samuelsson]

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