[Buildroot] I think I'm in love! And other newbie-type questions...

[Buildroot] I think I'm in love! And other newbie-type questions...

[Jean-Claude Gervais]

Hi,

	I do CM (configuration management) for an embedded software development
company. That means I have to create tools and procedures to make it
possible to re-produce software we have already shipped or will be
shipping.

	Reading Buildroot's documentation, I am amazed at the ingenuity of the
solution and really pleased that it may permit me to accomplish the
goals I mentioned. Thank you for creating such a useful project.

I do have a question:

After running the 'make menuconfig' and selecting a number of options, I
ran 'make' which proceeded to crank away for a number of hours.

At the end though it did not complete because of what appears to be a
missing file - the kernel .config file. More specifically

cp: missing destination file operand after
`/home/jgervais/Desktop/sandboxes/buildroot/project_build_arm/uclibc/linux-2.6.22.10/.config'

This sort of makes sense to me because although I did specify some
kernel options, I don't remember actually running the projected kernel's
'make menuconfig' which would have permitted me to essentially set all
the kernel options.

I read more of the documentation but could not find how this should be
handled although it may be quite evident when you are more experienced.

So my question is - What do I need to do to configure the kernel?

I believe once that is done, I will only need to type make and let the
buildroot procedure continue where it left off.

If there is a document that explains all this, can you please point me
towards it?

Thank you
J

PS - I'll make an effort to not be so long-winded next time.

[Buildroot] I think I'm in love! And other newbie-type questions...

[Janne Kario]

Jean-Claude Gervais wrote:

> cp: missing destination file operand after
> `/home/jgervais/Desktop/sandboxes/buildroot/project_build_arm/uclibc/linux-2.6.22.10/.config'

I'm facing the same problem with buildroot-20071015.tar.bz2 snapshot. I 
do think it is a genuine bug because after running 'make menuconfig' in 
the kernel directory manually, I still get the same error message.

j

[Buildroot] I think I'm in love! And other newbie-type questions...

[Jean-Claude Gervais]

Hi Janne,

By reading the mailing list archives, I think I understand the problem;
When configuring Buildroot, you must specify the path to your
kernel .config file.

This is in the Buildroot 'make menuconfig' options 

Kernel --->
    () .config file

If the value between parentheses is empty, then you must supply the path
to the .config file you want to use.

At least I think that's it.
Hope that helps.
J

On Wed, 2007-11-14 at 22:19 +0200, Janne Kario wrote:
> Jean-Claude Gervais wrote:
> 
> > cp: missing destination file operand after
> > `/home/jgervais/Desktop/sandboxes/buildroot/project_build_arm/uclibc/linux-2.6.22.10/.config'
> 
> I'm facing the same problem with buildroot-20071015.tar.bz2 snapshot. I 
> do think it is a genuine bug because after running 'make menuconfig' in 
> the kernel directory manually, I still get the same error message.
> 
> j
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot

[Buildroot] I think I'm in love! And other newbie-type questions...

[Janne Kario]

Jean-Claude Gervais wrote:
> Hi Janne,
> 
> By reading the mailing list archives, I think I understand the problem;
> When configuring Buildroot, you must specify the path to your
> kernel .config file.

You were 10 minutes ahead of me in reading the mailing lists. :)

I managed to buildroot compile using 'make defconfig'. Apparently, it 
uses some default kernel configuration (currently running kernel?). 
Furthermore buildroot comes with a bunch of default configurations for 
different boards so typing something like 'make atngw100_defconfig' 
would create default buildroot suitable for Atmel NGW100.

I haven't read any of the buildroot documentation (perhaps I should) but 
I think whenever you manage to build a working kernel configuration for 
your device you take the .config file and save it so that you can build 
new updated rootfs with more recent kernel version using the exact same 
configuration.

I'm not trying to accomplish anything yet. Just playing with this 
awesome stuff.

j

[Buildroot] Anyone familiar with PLX PCI driver? Otherwise, general driver question...

[Sean Parker]

Hello -

  Does anyone have specific experience with loading a
PLX-born driver into uCLinux? I'm trying to get it to load
but it refuses and don't know the specific things to check
as to why... (I do have insmod available and can execute it
in the command line of the embedded system. it says "... no
symbols ... (stripped?)...module not loaded")

  Otherwise, any advice would be appreciated about the
GENERAL differences, if any, between loading a module in
uCLinux vs. "normal system linux" (i.e. RH) Any links/book
references welcome. Differences such as gcc command line
params, module directories, busybox issues, insmod/rmmod,
etc.

  My next step is to load try the Hello World example on
this site, but I'm not only looking for specific task
results but general knowledge as well.

  Thanks
    Sean Parker





      ____________________________________________________________________________________
Get easy, one-click access to your favorites. 
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs 

[Buildroot] Anyone familiar with PLX PCI driver? Otherwise, general driver question...

[Ivan Kuten]

You may want to try insmod/rmmod from module-init-tools package (not included in buildroot)
and check if your module get loaded.

Regards,
Ivan


> Hello -
>
>   Does anyone have specific experience with loading a
> PLX-born driver into uCLinux? I'm trying to get it to load
> but it refuses and don't know the specific things to check
> as to why... (I do have insmod available and can execute it
> in the command line of the embedded system. it says "... no
> symbols ... (stripped?)...module not loaded")
>