[Buildroot] 2.6.33.2 kernel headers patch

[Buildroot] 2.6.33.2 kernel headers patch

[Thomas Brandstetter]

Today I tried buildroot with the latest kernel headers. I got the following error with udev:


/buildroot/build_x86/output/staging/usr/include/scsi/scsi.h:152: error: expected specifier-qualifier-list before 'u8'
/buildroot/build_x86/output/staging/usr/include/scsi/scsi.h: In function 'scsi_varlen_cdb_length':
/buildroot/build_x86/output/staging/usr/include/scsi/scsi.h:163: error: 'struct scsi_varlen_cdb_hdr' has no member named 'additional_cdb_length'
make[2]: *** [scsi_serial.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/buildroot/build_x86/output/build/udev-114/extras/scsi_id'
make[1]: *** [all] Error 1
make[1]: Leaving directory `/buildroot/build_x86/output/build/


This error indicates, that the patch:

linux-2.6.32.11-scsi-use-__uX-types-for-headers-exported-to-user-space.patch

should also be applied to the latest kernel headers eq.

linux-2.6.33.2-scsi-use-__uX-types-for-headers-exported-to-user-space.patch

Can someone confirm this?

THX

Thomas

[Buildroot] 2.6.33.2 kernel headers patch

[Thomas Brandstetter]

Ok,

this is the third email from my side without any reply/feedback. Am I doing something wrong or is there a hidden "How to write an email to this mail archive list" paper I haven't seen?

If my writing is to harsh I apologize but this is frustrating.

Cheers

Thomas
 
On Apr 3, 2010, at 2:39 PM, Thomas Brandstetter wrote:

> Today I tried buildroot with the latest kernel headers. I got the following error with udev:
> 
> 
> /buildroot/build_x86/output/staging/usr/include/scsi/scsi.h:152: error: expected specifier-qualifier-list before 'u8'
> /buildroot/build_x86/output/staging/usr/include/scsi/scsi.h: In function 'scsi_varlen_cdb_length':
> /buildroot/build_x86/output/staging/usr/include/scsi/scsi.h:163: error: 'struct scsi_varlen_cdb_hdr' has no member named 'additional_cdb_length'
> make[2]: *** [scsi_serial.o] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[2]: Leaving directory `/buildroot/build_x86/output/build/udev-114/extras/scsi_id'
> make[1]: *** [all] Error 1
> make[1]: Leaving directory `/buildroot/build_x86/output/build/
> 
> 
> This error indicates, that the patch:
> 
> linux-2.6.32.11-scsi-use-__uX-types-for-headers-exported-to-user-space.patch
> 
> should also be applied to the latest kernel headers eq.
> 
> linux-2.6.33.2-scsi-use-__uX-types-for-headers-exported-to-user-space.patch
> 
> Can someone confirm this?
> 
> THX
> 
> Thomas
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] 2.6.33.2 kernel headers patch

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Brandstetter <thomas.brandstetter@me.com> writes:

Hi,

 Thomas> This error indicates, that the patch:

 Thomas> linux-2.6.32.11-scsi-use-__uX-types-for-headers-exported-to-user-space.patch

 Thomas> should also be applied to the latest kernel headers eq.

 Thomas> linux-2.6.33.2-scsi-use-__uX-types-for-headers-exported-to-user-space.patch

 Thomas> Can someone confirm this?

Yes - Fixed in git.

-- 
Bye, Peter Korsgaard

[Buildroot] 2.6.33.2 kernel headers patch

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Brandstetter <thomas.brandstetter@me.com> writes:

 Thomas> Ok,

 Thomas> this is the third email from my side without any
 Thomas> reply/feedback. Am I doing something wrong or is there a hidden
 Thomas> "How to write an email to this mail archive list" paper I
 Thomas> haven't seen?

 Thomas> If my writing is to harsh I apologize but this is frustrating.

I can understand that - But don't forget that buildroot is an open
source project with people working on it in their spare time. You'll
need to be more patient or assist yourself (E.G. for the issues you
reported you could have tested your proposed fixes and/or sent patches).

When using git rather than released versions, some amount of breakage is
bound to happen.

I believe this is pretty much like most other open source projects.

-- 
Bye, Peter Korsgaard

[Buildroot] 2.6.33.2 kernel headers patch

[Thomas Brandstetter]

You're totally right, but I thought there is something wrong with the mailing list because nobody wrote anything in reply :-)

I'm not a developer and I'm not very familiar with git. Is there a good documentation for Buildroot available how to send git patches via the command line?

Cheers Thomas


On Apr 7, 2010, at 9:25 AM, Peter Korsgaard wrote:

>>>>>> "Thomas" == Thomas Brandstetter <thomas.brandstetter@me.com> writes:
> 
> Thomas> Ok,
> 
> Thomas> this is the third email from my side without any
> Thomas> reply/feedback. Am I doing something wrong or is there a hidden
> Thomas> "How to write an email to this mail archive list" paper I
> Thomas> haven't seen?
> 
> Thomas> If my writing is to harsh I apologize but this is frustrating.
> 
> I can understand that - But don't forget that buildroot is an open
> source project with people working on it in their spare time. You'll
> need to be more patient or assist yourself (E.G. for the issues you
> reported you could have tested your proposed fixes and/or sent patches).
> 
> When using git rather than released versions, some amount of breakage is
> bound to happen.
> 
> I believe this is pretty much like most other open source projects.
> 
> -- 
> Bye, Peter Korsgaard

[Buildroot] 2.6.33.2 kernel headers patch

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Brandstetter <thomas.brandstetter@me.com> writes:

 Thomas> You're totally right, but I thought there is something wrong
 Thomas> with the mailing list because nobody wrote anything in reply
 Thomas> :-)

You can always check the archive if you're in doubt:

http://lists.busybox.net/pipermail/buildroot/

 Thomas> I'm not a developer and I'm not very familiar with git. Is
 Thomas> there a good documentation for Buildroot available how to send
 Thomas> git patches via the command line?

Buildroot is mainly a developer tool, but we do have documentation:

http://buildroot.net/buildroot.html
http://buildroot.net/git.html

The last has a link to the git homepage. There's very little buildroot
specific about how we use git, so a quick google search should find you
plenty of info (hint: we use the same approach like many other projects
like the Linux kernel, U-boot, ..).

The git commands you are looking for are:

git checkout -b <branch>
git commit
git format-patch -s master
git send-email --to buildroot at uclibc.org 0*.patch

-- 
Bye, Peter Korsgaard