From: Tom Rini <tom_rini@mentor.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH 2/2] libc-package.bbclass: should not rm scsi/*.h
Date: Mon, 17 Jan 2011 08:44:34 -0700 [thread overview]
Message-ID: <4D3463E2.9070102@mentor.com> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB685AFA1B328@shsmsx502.ccr.corp.intel.com>
On 01/15/2011 04:50 AM, Cui, Dexuan wrote:
> Koen Kooi wrote:
>> Op 15 jan 2011, om 12:23 heeft Dexuan Cui het volgende geschreven:
>>
>>> {e}glibc should install the scsi/*.h files, which are needed by hal.
>>> Currently hal can build because eglibc-initial (which has its own
>>> do_install) installs the files. In future eglibc will have its own
>>> sysroot, so hal
>>> won't build.
Unrelated, is it on the roadmap already to upgrade things to use
devicekit rather than hal?
>>> BTW: in OE side, eglibc's do_install also doesn't remove the files.
>>
>> As some background info: There's a conflict between
>> linux-libc-headers-dev and libc-dev when installing on the target. In
>> OE we do this instead:
>>
>> koen@dominion:/OE/org.openembedded.dev$ grep scsi
>> recipes/linux-libc-headers/ -rn
>> recipes/linux-libc-headers/linux-libc-headers_2.6.32.bb:23: rm -f
>> ${D}${exec_prefix}/include/scsi/scsi.h
>> recipes/linux-libc-headers/linux-libc-headers_2.6.31.bb:23: rm -f
>> ${D}${exec_prefix}/include/scsi/scsi.h
>> recipes/linux-libc-headers/linux-libc-headers_2.6.34.bb:42: rm -f
>> ${D}${exec_prefix}/include/scsi/scsi.h
> My understanding is:
> Linux kernel should not export these files: in OE side see 91d3d92a acked by you. :-)
> So {e}glibc should supply the files -- previously poky did supply, but 7379ee77 removed the files -- I think this is incorrect.
>
> BTW: in poky, we can see linux-libc-headers_2.6.36.bb also correctly removes the file.
Correct. The kernel (incorrectly) re-introduced exporting <scsi/scsi.h>.
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2011-01-17 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 11:23 [PATCH 0/2] upgrade libc-package.bbclass; add libgcc Dexuan Cui
2011-01-15 11:23 ` [PATCH 1/2] libgcc: use the new recipe (rather than gcc-runtime) to install libgcc_s.so* and crt*.o Dexuan Cui
2011-01-15 11:37 ` Koen Kooi
2011-01-15 11:55 ` Cui, Dexuan
2011-01-15 13:12 ` Koen Kooi
2011-01-15 23:34 ` Richard Purdie
2011-01-16 6:13 ` Cui, Dexuan
2011-01-17 5:08 ` Cui, Dexuan
2011-01-15 11:23 ` [PATCH 2/2] libc-package.bbclass: should not rm scsi/*.h Dexuan Cui
2011-01-15 11:39 ` Koen Kooi
2011-01-15 11:50 ` Cui, Dexuan
2011-01-17 15:44 ` Tom Rini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D3463E2.9070102@mentor.com \
--to=tom_rini@mentor.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox