[Buildroot] [git commit master] synergy: needs C++ support

[Buildroot] [git commit master] synergy: needs C++ support

[Peter Korsgaard]

commit: http://git.buildroot.net/buildroot/commit/?id=fca4e38c80c2187cd492a9223851ba25b817814f
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 CHANGES                   |    6 +++---
 package/synergy/Config.in |    4 ++++
 2 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/CHANGES b/CHANGES
index 5d0214e..36a1372 100644
--- a/CHANGES
+++ b/CHANGES
@@ -9,9 +9,9 @@
 	libelf, libevent, libglib2, liblockfile, libmad, libpcap, libupnp,
 	libuuid, ltrace, lua, lzma, mdadm, ncftp, ncurses, netkittelnet,
 	netsnmp, ntfs-3g, openssl, php, python, quagga, radvd, rsync, samba,
-	sawman, shared-mime-info, speech-tools, sqlite, squashfs, syslinux,
-	tcpdump, u-boot, util-linux, valgrind, vsftpd, wipe, wpa-supplicant,
-	xdata_xcursor-themes, zlib
+	sawman, shared-mime-info, speech-tools, sqlite, squashfs, synergy,
+	syslinux, tcpdump, u-boot, util-linux, valgrind, vsftpd, wipe,
+	wpa-supplicant, xdata_xcursor-themes, zlib
 
 	Removed package: mdnsresponder, mpatrol
 
diff --git a/package/synergy/Config.in b/package/synergy/Config.in
index fe6a634..a2766b1 100644
--- a/package/synergy/Config.in
+++ b/package/synergy/Config.in
@@ -1,6 +1,7 @@
 config BR2_PACKAGE_SYNERGY
 	bool "synergy"
 	depends on BR2_PACKAGE_XORG7
+	depends on BR2_INSTALL_LIBSTDCPP
 	help
 	  Synergy lets you easily share a single mouse and
 	  keyboard between multiple computers with different
@@ -8,3 +9,6 @@ config BR2_PACKAGE_SYNERGY
 	  without special hardware.
 
 	  http://synergy2.sourceforge.net/
+
+comment "synergy requires a toolchain with C++ support enabled"
+	depends on BR2_PACKAGE_XORG7 && !BR2_INSTALL_LIBSTDCPP
-- 
1.6.3.3

[Buildroot] busybox question

[Roman Chertov]

Hello,

I have an ARM920T board that I am trying to get going with buildroot and
uClibc.  I managed to compile the kernel, and it boots up to the point
where the login must happen.  Nothing happens at that point.  However,
the machine runs as I can ping it.  I have tried to init=/bin/sh
init=/bin/ethtool, but I did not get any output to indicate that
something started.

I have the following question.  I can build the default image on the
board (Debian 2.4, glibc) and mount the buildroot root fs over NFS.
However, if I try to execute any program, I get the following errors:

root at ts7000:bin# ./busybox
-bash: ./busybox: No such file or directory

I would expect that at least the program would start and then an error
would occur due to the fact that uClibc is not present.  I am correct in
assuming this?  I am trying to debug if I screwed the cross compiling
(although Linux kernel boots), or if there is a problem with the init
process.


I would appreciate some insight into this issue.

Thanks,

Roman

[Buildroot] busybox question

[Peter Korsgaard]

>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:

 Roman> Hello,
 Roman> I have an ARM920T board that I am trying to get going with buildroot and
 Roman> uClibc.  I managed to compile the kernel, and it boots up to the point
 Roman> where the login must happen.  Nothing happens at that point.  However,
 Roman> the machine runs as I can ping it.  I have tried to init=/bin/sh
 Roman> init=/bin/ethtool, but I did not get any output to indicate that
 Roman> something started.

And you have set console= to something sensible? What is the last output
you get from the kernel?

Do you have software floating point support enabled in buildroot?
(toolchain->Use software floating point by default)

 Roman> I have the following question.  I can build the default image on the
 Roman> board (Debian 2.4, glibc) and mount the buildroot root fs over NFS.
 Roman> However, if I try to execute any program, I get the following errors:

 Roman> root at ts7000:bin# ./busybox
 Roman> -bash: ./busybox: No such file or directory

You'll probably have to chroot into the nfs dir to get the dynamic
linker to work.


-- 
Bye, Peter Korsgaard

[Buildroot] busybox question

[Roman Chertov]

Peter Korsgaard wrote:
>>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:
> 
>  Roman> Hello,
>  Roman> I have an ARM920T board that I am trying to get going with buildroot and
>  Roman> uClibc.  I managed to compile the kernel, and it boots up to the point
>  Roman> where the login must happen.  Nothing happens at that point.  However,
>  Roman> the machine runs as I can ping it.  I have tried to init=/bin/sh
>  Roman> init=/bin/ethtool, but I did not get any output to indicate that
>  Roman> something started.
> 
> And you have set console= to something sensible? What is the last output
> you get from the kernel?

console=ttyAM0,115200 ip=dhcp noinitrd root=/dev/nfs init=/sbin/init
nfsroot=192.168.0.1:/proj/tools/buildroot-2009.08/project_build_arm/uclibc/root/
This is my argument list to the kernel.

This was my last message from the kernel

VFS: Mounted root (nfs filesystem).

Freeing init memory: 120K

Based on Francisco's private email, I made some nodes in the /dev
directory as by default, buildroot creates only files and not device
files with major/minor numbers.  I made the nodes by copying some of the
devices from the board's default disk while it was running.  Now, when I
boot, I get the following repeating sequence.

can't open /dev/~: No such file or directory

can't open /dev/tty1: No such file or directory

can't open /dev/tty2: No such file or directory


Looks like the culprit, is the improper device setup.

> 
> Do you have software floating point support enabled in buildroot?
> (toolchain->Use software floating point by default)

This is not set.

> 
>  Roman> I have the following question.  I can build the default image on the
>  Roman> board (Debian 2.4, glibc) and mount the buildroot root fs over NFS.
>  Roman> However, if I try to execute any program, I get the following errors:
> 
>  Roman> root at ts7000:bin# ./busybox
>  Roman> -bash: ./busybox: No such file or directory
> 
> You'll probably have to chroot into the nfs dir to get the dynamic
> linker to work.

I will give this a shot later on today.

Thanks.

Roman

> 
> 

[Buildroot] busybox question

[Emmanuel Riou]

Hi Roman,

please see my comments inline,

Roman Chertov wrote:
> Peter Korsgaard wrote:
>>>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:
>>  Roman> Hello,
>>  Roman> I have an ARM920T board that I am trying to get going with buildroot and
>>  Roman> uClibc.  I managed to compile the kernel, and it boots up to the point
>>  Roman> where the login must happen.  Nothing happens at that point.  However,
>>  Roman> the machine runs as I can ping it.  I have tried to init=/bin/sh
>>  Roman> init=/bin/ethtool, but I did not get any output to indicate that
>>  Roman> something started.
>>
>> And you have set console= to something sensible? What is the last output
>> you get from the kernel?
> 
> console=ttyAM0,115200 ip=dhcp noinitrd root=/dev/nfs init=/sbin/init
> nfsroot=192.168.0.1:/proj/tools/buildroot-2009.08/project_build_arm/uclibc/root/
> This is my argument list to the kernel.
> 
> This was my last message from the kernel
> 
> VFS: Mounted root (nfs filesystem).
> 
> Freeing init memory: 120K
> 
> Based on Francisco's private email, I made some nodes in the /dev
> directory as by default, buildroot creates only files and not device
> files with major/minor numbers.  I made the nodes by copying some of the
> devices from the board's default disk while it was running.  Now, when I
> boot, I get the following repeating sequence.
> 
> can't open /dev/~: No such file or directory
> 
> can't open /dev/tty1: No such file or directory
> 
> can't open /dev/tty2: No such file or directory
> 
You have to configure buildroot to generate a tar archive of your 
filesystem, since buildroot uses fakeroot to create the /dev files in 
the archive (buildroot can't create the /dev files in your project 
directory as you are not root). You just have to untar this archive then 
to get your complete root filesystem you're gonna mount via NFS.

Hope this helps,

Emmanuel.


> 
> Looks like the culprit, is the improper device setup.
> 
>> Do you have software floating point support enabled in buildroot?
>> (toolchain->Use software floating point by default)
> 
> This is not set.
> 
>>  Roman> I have the following question.  I can build the default image on the
>>  Roman> board (Debian 2.4, glibc) and mount the buildroot root fs over NFS.
>>  Roman> However, if I try to execute any program, I get the following errors:
>>
>>  Roman> root at ts7000:bin# ./busybox
>>  Roman> -bash: ./busybox: No such file or directory
>>
>> You'll probably have to chroot into the nfs dir to get the dynamic
>> linker to work.
> 
> I will give this a shot later on today.
> 
> Thanks.
> 
> Roman
> 
>>
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

[Buildroot] busybox question

[Roman Chertov]

Emmanuel,

I have created a tar fs and then untarred as root so that mknod would
work properly.  I have then rebooted the board and pointed it to the new
file system.  I get the uClibc prompt, but I can't log in.  This means
that busybox is working.  However, I suspect that the serial line is not
configured correctly in inittab. (I added ttyS0, ttyS1, and ttyAM0)

However, I also modified /etc/init.d/rcS to print a debug message (echo
-n).  I have also modified rcC to call script which would reboot the
board in 2 minutes.  That would allow me to make changes to the rootfs
and then try booting the whole thing again.  However, I don't see the
debug messages, the sshd, snmpd, ntp, startup messages (rcS is supposed
to invoke those).  Also, my auto reboot does not work.  I suspect that
init never called the /etc/init.d/rcS file.

I would appreciate any hints regarding this.

Roman

Emmanuel Riou wrote:
> Hi Roman,
> 
> please see my comments inline,
> 
> Roman Chertov wrote:
>> Peter Korsgaard wrote:
>>>>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:
>>>  Roman> Hello,
>>>  Roman> I have an ARM920T board that I am trying to get going with
>>> buildroot and
>>>  Roman> uClibc.  I managed to compile the kernel, and it boots up to
>>> the point
>>>  Roman> where the login must happen.  Nothing happens at that point. 
>>> However,
>>>  Roman> the machine runs as I can ping it.  I have tried to init=/bin/sh
>>>  Roman> init=/bin/ethtool, but I did not get any output to indicate that
>>>  Roman> something started.
>>>
>>> And you have set console= to something sensible? What is the last output
>>> you get from the kernel?
>>
>> console=ttyAM0,115200 ip=dhcp noinitrd root=/dev/nfs init=/sbin/init
>> nfsroot=192.168.0.1:/proj/tools/buildroot-2009.08/project_build_arm/uclibc/root/
>>
>> This is my argument list to the kernel.
>>
>> This was my last message from the kernel
>>
>> VFS: Mounted root (nfs filesystem).
>>
>> Freeing init memory: 120K
>>
>> Based on Francisco's private email, I made some nodes in the /dev
>> directory as by default, buildroot creates only files and not device
>> files with major/minor numbers.  I made the nodes by copying some of the
>> devices from the board's default disk while it was running.  Now, when I
>> boot, I get the following repeating sequence.
>>
>> can't open /dev/~: No such file or directory
>>
>> can't open /dev/tty1: No such file or directory
>>
>> can't open /dev/tty2: No such file or directory
>>
> You have to configure buildroot to generate a tar archive of your
> filesystem, since buildroot uses fakeroot to create the /dev files in
> the archive (buildroot can't create the /dev files in your project
> directory as you are not root). You just have to untar this archive then
> to get your complete root filesystem you're gonna mount via NFS.
> 
> Hope this helps,
> 
> Emmanuel.
> 
> 
>>
>> Looks like the culprit, is the improper device setup.
>>
>>> Do you have software floating point support enabled in buildroot?
>>> (toolchain->Use software floating point by default)
>>
>> This is not set.
>>
>>>  Roman> I have the following question.  I can build the default image
>>> on the
>>>  Roman> board (Debian 2.4, glibc) and mount the buildroot root fs
>>> over NFS.
>>>  Roman> However, if I try to execute any program, I get the following
>>> errors:
>>>
>>>  Roman> root at ts7000:bin# ./busybox
>>>  Roman> -bash: ./busybox: No such file or directory
>>>
>>> You'll probably have to chroot into the nfs dir to get the dynamic
>>> linker to work.
>>
>> I will give this a shot later on today.
>>
>> Thanks.
>>
>> Roman
>>
>>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
> 

[Buildroot] busybox question

[Peter Korsgaard]

>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:

 Roman> Emmanuel,
 Roman> I have created a tar fs and then untarred as root so that mknod would
 Roman> work properly.  I have then rebooted the board and pointed it to the new
 Roman> file system.  I get the uClibc prompt, but I can't log in.

With uclibc prompt I guess you mean login prompt, right? What happens if
you try to login as root?

Do you get a shell if you boot with init=/bin/sh?

Have you verified that you have softfloat enabled like I asked yesterday?

-- 
Bye, Peter Korsgaard

[Buildroot] busybox question

[Roman Chertov]

Peter Korsgaard wrote:
>>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:
> 
>  Roman> Emmanuel,
>  Roman> I have created a tar fs and then untarred as root so that mknod would
>  Roman> work properly.  I have then rebooted the board and pointed it to the new
>  Roman> file system.  I get the uClibc prompt, but I can't log in.
> 
> With uclibc prompt I guess you mean login prompt, right? What happens if
> you try to login as root?

I can't type anything over the serial so I can't log in.  This is what I
see though:

Freeing init memory: 120K



Welcome to Buildroot
uclibc login:


> 
> Do you get a shell if you boot with init=/bin/sh?

I am going to try that in a few.

> 
> Have you verified that you have softfloat enabled like I asked yesterday?

I do not have softfloat enabled.  Do I also need to enable "Enable C99
Floating-point environment" (uclibc-menuconfig)?

Thanks

> 

[Buildroot] busybox question

[Peter Korsgaard]

>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:

Hi,

 >> With uclibc prompt I guess you mean login prompt, right? What happens if
 >> you try to login as root?

 Roman> I can't type anything over the serial so I can't log in.  This is what I
 Roman> see though:

 Roman> Freeing init memory: 120K



 Roman> Welcome to Buildroot
 Roman> uclibc login:

Ok, that looks good atleast.

 >> Have you verified that you have softfloat enabled like I asked yesterday?

 Roman> I do not have softfloat enabled.  Do I also need to enable "Enable C99
 Roman> Floating-point environment" (uclibc-menuconfig)?

If you don't have softfloat enabled (you should), then you'll need to
ensure that you have fpu emulation enabled in the kernel.

And no, you normally don't have to mess with the uclibc config.

Remember that you need to do a clean rebuild after changing
soft/hardfloat (rm -rf output; make if you are using git, rm -rf
*build_*; make if you are using the release).

-- 
Bye, Peter Korsgaard

[Buildroot] busybox question

[Roman Chertov]

> 
> Remember that you need to do a clean rebuild after changing
> soft/hardfloat (rm -rf output; make if you are using git, rm -rf
> *build_*; make if you are using the release).

That worked.  I did a full rebuild and now I can boot up and login.  Thanks.

Roman

> 

[Buildroot] busybox question

[Peter Korsgaard]

>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:

 Roman> Peter Korsgaard wrote:
 >>>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:
 >> 
 Roman> Hello,
 Roman> I have an ARM920T board that I am trying to get going with buildroot and
 Roman> uClibc.  I managed to compile the kernel, and it boots up to the point
 Roman> where the login must happen.  Nothing happens at that point.  However,
 Roman> the machine runs as I can ping it.  I have tried to init=/bin/sh
 Roman> init=/bin/ethtool, but I did not get any output to indicate that
 Roman> something started.
 >> 
 >> And you have set console= to something sensible? What is the last output
 >> you get from the kernel?

 Roman> console=ttyAM0,115200 ip=dhcp noinitrd root=/dev/nfs init=/sbin/init
 Roman> nfsroot=192.168.0.1:/proj/tools/buildroot-2009.08/project_build_arm/uclibc/root/

That's your problem then - The files under project_build_arm/uclibc/root
don't have the right permissions and device nodes are not
created. Instead select tarball under target filesystem options, and
unpack it as root on your NFS server.

-- 
Bye, Peter Korsgaard