Re: [ptxdist] awk bug in some make dependency scripts?

["Andreas Bießmann" <biessmann@corscience.de>]

On 13.11.2012 21:02, Michael Olbrich wrote:
> Hi,
> 
> On Tue, Nov 13, 2012 at 03:35:40PM +0100, Andreas Bießmann wrote:
>> On 12.11.2012 12:47, Michael Olbrich wrote:
>>> On Mon, Nov 12, 2012 at 10:02:06AM +0100, Andreas Bießmann wrote:
>>>> On 09.11.2012 17:28, Michael Olbrich wrote:
>>>>> On Fri, Nov 09, 2012 at 03:20:55PM +0100, Andreas Bießmann wrote:

<snip>

>> These following lines show my test-case with the real repository. The
>> repository is first built completely (so just the rebuild is required).
>> The rebuild of kernel and datasource-driver is triggered explicitly,
>> dependency for printer-driver is met implicitly. To show the content of
>> kernel-modules.ipkg I delete the 'extra' dir in NFS-root before and
>> check it after the build.
>> The difference in order of targets built is sticking out and until now
>> always reproducible (just switch the awk version and do the sequence).
>>
>> ---8<---
>> with gawk 4.0 (sudo aptitude install gawk/squeeze-backports)
>> rm -rf platform-responder2/root/lib/modules/3.4.18/extra/
>> ./p drop kernel.compile
>> ./p drop datasource-driver.compile
>> ./p go
>>
>> target: kernel.compile
>> target: kernel.install
>> target: kernel.install.pack
>> target: kernel.install.post
>> target: kernel.targetinstall
>> target: printer-driver.extract.post
>> target: printer-driver.prepare
>> target: printer-driver.compile
>> target: printer-driver.install
>> target: printer-driver.install.pack
>> target: printer-driver.install.post
>> target: printer-driver.targetinstall
>> target: printer-driver.targetinstall.post
>> target: datasource-driver.extract.post
>> target: datasource-driver.prepare
>> target: datasource-driver.compile
>> target: datasource-driver.install
>> target: datasource-driver.install.pack
>> target: datasource-driver.install.post
>> target: datasource-driver.targetinstall
>> target: datasource-driver.targetinstall.post
>> target: kernel.targetinstall.post
>>
>> ls -la platform-responder2/root/lib/modules/3.4.18/extra -> OK
>> ----
>> with gawk 3.1.x (sudo aptitude install gawk/stable)
>>
>> rm -rf platform-responder2/root/lib/modules/3.4.18/extra/
>> ./p drop kernel.compile
>> ./p drop datasource-driver.compile
>> ./p go
>>
>> target: kernel.compile
>> target: kernel.install
>> target: kernel.install.pack
>> target: kernel.install.post
>> target: kernel.targetinstall
>> target: kernel.targetinstall.post
>> target: datasource-driver.extract.post
>> target: datasource-driver.prepare
>> target: datasource-driver.compile
>> target: datasource-driver.install
>> target: datasource-driver.install.pack
>> target: datasource-driver.install.post
>> target: datasource-driver.targetinstall
>> target: datasource-driver.targetinstall.post
>> target: printer-driver.extract.post
>> target: printer-driver.prepare
>> target: printer-driver.compile
>> target: printer-driver.install
>> target: printer-driver.install.pack
>> target: printer-driver.install.post
>> target: printer-driver.targetinstall
>> target: printer-driver.targetinstall.post
>>
>> ls -la platform-responder2/root/lib/modules/3.4.18/extra -> NOT OK
>> --->8---
>>
>> Any other pointers?
> 
> Hmmm, what order do you get if you run "./p targetinstall kernel" instead
> of "./p go"?

Well, does not build the drivers at all. And it is explicable cause
(shame on me) I missed the explicit dependency kernel.targetinstall.port
-> driver.targetinstall. My small example, however, had this rule so I
could not reproduce the behaviour with it.
Many thanks to you Michael and Tim Niemeyer who pushed me in the right
direction.

I wonder if we can add an implicit rule to build <package>.targetinstall
before kernel.targetinstall.post if we depend on KERNEL. So we could get
rid of the explicit rule in a driver.

Best regards

Andreas Bießmann

-- 
ptxdist mailing list
ptxdist@pengutronix.de