Pkun | 1 Dec 12:39 2010
Picon

BR2_LINUX_COPYTO_ROOTFS lack

Hello

There was an .config option BR2_LINUX_COPYTO_ROOTFS in early buildroot versions (at least in version 2009.11). Then the kernel configuration was refactored and this option was removed. Why? It was usefull. Do you plan to restore the feature to copy kernel image to the rootfs automatically?

Serj Kalichev

_______________________________________________
buildroot mailing list
buildroot@...
http://lists.busybox.net/mailman/listinfo/buildroot
Will Newton | 1 Dec 15:44 2010
Picon

[PATCH] package/openssh: Use HTTP instead of FTP for source download.

HTTP should be more firewall friendly.

Signed-off-by: Will Newton <will.newton@...>
---
 package/openssh/openssh.mk |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/package/openssh/openssh.mk b/package/openssh/openssh.mk
index 236a3a8..82c64d6 100644
--- a/package/openssh/openssh.mk
+++ b/package/openssh/openssh.mk
 <at>  <at>  -5,7 +5,7  <at>  <at> 
 #############################################################

 OPENSSH_VERSION = 5.6p1
-OPENSSH_SITE = ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable
+OPENSSH_SITE = http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable
 OPENSSH_CONF_ENV = LD="$(TARGET_CC)"
 OPENSSH_CONF_OPT = --libexecdir=/usr/lib --disable-lastlog --disable-utmp \
 		--disable-utmpx --disable-wtmp --disable-wtmpx --disable-strip
--

-- 
1.7.2.2
_______________________________________________
buildroot mailing list
buildroot@...
http://lists.busybox.net/mailman/listinfo/buildroot
Picon

ifplugd

Hello!

When i try to build this package for target system, i get this error (at configuration time).

..
checking for strspn... yes
checking pkg-config is at least version 0.9.0... yes
checking for LIBDAEMON... yes
configure: error: missing --with-initdir=DIR
..

I think that this is little mistake in related Makefile, but i don't know that means option --with-initdir
in this case.

Best regards!
Evgeny Startsev.
bugzilla | 2 Dec 08:48 2010
Picon

[Bug 2875] New: Kernel doesn't build Ext2 support out-of-the-box

https://bugs.busybox.net/show_bug.cgi?id=2875

           Summary: Kernel doesn't build Ext2 support out-of-the-box
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: Other
        AssignedTo: unassigned@...
        ReportedBy: tuukka.pasanen@...
                CC: buildroot@...
   Estimated Hours: 0.0

Because kernel doesn't build Ext2 support out-of-the-box if you choose i386 for
default config you can use iso-image without minor tuning of kernel .config
file. This should work like initrd thing.

--

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Ben | 2 Dec 10:15 2010
Picon
Picon

BR2_VERSION missing in .config BR 2010.11

Hi,

I use BR2 version 2010.11. When I just extract the stable version and run
"make menuconfig", change nothing and save the config, the BR2_VERSION
string is missing in .config file.

Ben
Yann E. MORIN | 2 Dec 10:22 2010
Picon

Re: BR2_VERSION missing in .config BR 2010.11

Ben, All,

On Thursday 02 December 2010 10:15:35 Ben wrote:
> I use BR2 version 2010.11. When I just extract the stable version and run
> "make menuconfig", change nothing and save the config, the BR2_VERSION
> string is missing in .config file.

Please see: git log 2d239bb..75efd6b

Where and how do you use BR2_VERSION ?

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.  |
'------------------------------^-------^------------------^--------------------'
bugzilla | 2 Dec 14:44 2010
Picon

[Bug 2881] New: Can't build project statically with external toolchain

https://bugs.busybox.net/show_bug.cgi?id=2881

           Summary: Can't build project statically with external toolchain
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned@...
        ReportedBy: serj.kalichev@...
                CC: buildroot@...
   Estimated Hours: 0.0

Created attachment 2749
  --> https://bugs.busybox.net/attachment.cgi?id=2749
Don't copy shared libraries to the target dir if BR2_PREFER_STATIC_LIB defined

Hello

Buildroot version: 2010.11

I tried to build minimal busybox-only project for using as initramfs. I use
external buildroot toolchain. The buildroot copy the .so libraries from
external toolchain to the target dir unconditionally. But I build busybox
statically and don't need shared libraries (the size of resulted image is too
big with unneeded libraries).

The attached patch use BR2_PREFER_STATIC_LIB to find out if the project prefer
static linking and if the static linking is preferred don't copy shared
libraries to the target dir.

--

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Chris Kerios | 2 Dec 17:27 2010
Picon

Help - Buildroot-2010.11 Don't know what changed

Hi,
I am working with the 2010.11 release on a PC-104 Geode LX w/Compact
Flash card. Fedora 14.

I built a minimal system with all the defaults, no external toolchain:

Kernel = 2.6.36.1
uClibc = .9.31.x with .9.31.x.config file
Busybox = 1.17.x with 1.17.x.config file
gcc = 4.3.x
bootloader selected = grub

I have not added any files/applications to be built, so all that is
being built is the toolchain, kernel, grub and busybox.  Everything
downloads and builds fine!

The problem is when I copy to flash and boot the system it comes up as
read-only!  I copy things to the flash as root and preserve all
permissions, etc.  I've looked at the mailing list and long ago the
threads said to have the entry in inittab remount the filesystem as RW
and it should correct the problem.  The issue is my default inittab
file has this entry in it so I don't understand why I am seeing this.

If I execute the command manually from the command line after logging
in, it mounts the filesystem back as RW just fine.  Also, if I include
a "rw" on my kernel line in grub.conf the filesystem comes in as RW.

Is this a busybox issue?  I am using all buildroot defaults.  Any
thoughts or ideas of things I can check?

Thanks in advance,
Chris
Lionel Landwerlin | 2 Dec 17:31 2010
Picon

Re: Help - Buildroot-2010.11 Don't know what changed

On Thu, Dec 2, 2010 at 5:27 PM, Chris Kerios <ckerios@...> wrote:
> Hi,
> I am working with the 2010.11 release on a PC-104 Geode LX w/Compact
> Flash card. Fedora 14.
>
> I built a minimal system with all the defaults, no external toolchain:
>
> Kernel = 2.6.36.1
> uClibc = .9.31.x with .9.31.x.config file
> Busybox = 1.17.x with 1.17.x.config file
> gcc = 4.3.x
> bootloader selected = grub
>
> I have not added any files/applications to be built, so all that is
> being built is the toolchain, kernel, grub and busybox.  Everything
> downloads and builds fine!
>
> The problem is when I copy to flash and boot the system it comes up as
> read-only!  I copy things to the flash as root and preserve all
> permissions, etc.  I've looked at the mailing list and long ago the
> threads said to have the entry in inittab remount the filesystem as RW
> and it should correct the problem.  The issue is my default inittab
> file has this entry in it so I don't understand why I am seeing this.
>
> If I execute the command manually from the command line after logging
> in, it mounts the filesystem back as RW just fine.  Also, if I include
> a "rw" on my kernel line in grub.conf the filesystem comes in as RW.
>
> Is this a busybox issue?  I am using all buildroot defaults.  Any
> thoughts or ideas of things I can check?
>

I'm not sure, but it sounds like a kernel default behavior. On my
2.6.23 is boot nfs readonly unless I add "rw" to the kernel command
line.
Haven't you changed the kernel config file ?

Regards,

--
Lionel Landwerlin
Chris Kerios | 2 Dec 17:52 2010
Picon

Re: Help - Buildroot-2010.11 Don't know what changed

On Thu, Dec 2, 2010 at 11:31 AM, Lionel Landwerlin
<llandwerlin@...> wrote:
> On Thu, Dec 2, 2010 at 5:27 PM, Chris Kerios <ckerios@...> wrote:
>> Hi,
>> I am working with the 2010.11 release on a PC-104 Geode LX w/Compact
>> Flash card. Fedora 14.
>>
>> I built a minimal system with all the defaults, no external toolchain:
>>
>> Kernel = 2.6.36.1
>> uClibc = .9.31.x with .9.31.x.config file
>> Busybox = 1.17.x with 1.17.x.config file
>> gcc = 4.3.x
>> bootloader selected = grub
>>
>> I have not added any files/applications to be built, so all that is
>> being built is the toolchain, kernel, grub and busybox.  Everything
>> downloads and builds fine!
>>
>> The problem is when I copy to flash and boot the system it comes up as
>> read-only!  I copy things to the flash as root and preserve all
>> permissions, etc.  I've looked at the mailing list and long ago the
>> threads said to have the entry in inittab remount the filesystem as RW
>> and it should correct the problem.  The issue is my default inittab
>> file has this entry in it so I don't understand why I am seeing this.
>>
>> If I execute the command manually from the command line after logging
>> in, it mounts the filesystem back as RW just fine.  Also, if I include
>> a "rw" on my kernel line in grub.conf the filesystem comes in as RW.
>>
>> Is this a busybox issue?  I am using all buildroot defaults.  Any
>> thoughts or ideas of things I can check?
>>
>
> I'm not sure, but it sounds like a kernel default behavior. On my
> 2.6.23 is boot nfs readonly unless I add "rw" to the kernel command
> line.
> Haven't you changed the kernel config file ?
>
> Regards,
>
> --
> Lionel Landwerlin
>

Hi Lionel,
Yes, I have a modified kernel (2.6.32.14) config file that I have been
using from my beginning with buildroot starting with the 2010.05 and
08 releases.  I basically am using that config file and then answering
N to all the deltas when buildroot/linux kernel detects the
differences in the config file between the releases and prompts me
before the kernel build.  I am configuring for NFSv3 in the kernel but
am not asking buildroot to build nfs-utils at this time if you think
that might make a difference here.  Although, I am hard pressed to see
where NFS comes in as it's not even being started at bootup time.  I
didn't see anything in my kernel config building about setting up a
read-only filesystem.  Are you thinking something is buried in my
kernel config?

Maybe, but I am running on buildroot 08 without this problem.
Although, I am building all my app packages under that one and maybe
something is overriding it and masking the original problem???

Chris

Gmane