crochet builds failing miserably for some day now with latest sources
Tim Kientzle
tim at kientzle.com
Wed May 22 14:54:49 UTC 2013
On May 22, 2013, at 7:49 AM, Tim Kientzle wrote:
>
> On May 21, 2013, at 10:22 PM, Werner Thie wrote:
>
>> On 5/22/13 4:24 AM, Tim Kientzle wrote:
>>> On May 21, 2013, at 9:02 AM, Werner Thie wrote:
>>>
>>>> Hi all
>>>>
>>>> My last image for the BBone is
>>>>
>>>> 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r250696M: Thu May 16 14:18:30 CEST 2013
>>>>
>>>> I'm not able to build a complete image since then with newer sources, the build is regularly failing with
>>>>
>>>> ….
>>>> make: illegal option -- J
>>>
>>> There's been some discussion of this on the
>>> freebsd-current@ mailing list. It seems to occur
>>> when you have an old 'make' binary in the 'obj'
>>> tree.
>>>
>>> First try removing just the old make binary:
>>>
>>> $ rm /home/wthie/proj/crochet-freebsd/work/obj/usr/local/src/make.i386/make
>>>
>>> and if that is insufficient, try deleting Crochet's
>>> 'work' directory and doing a completely clean build
>>> from scratch:
>>>
>>> $ rm -rf /home/wthie/proj/crochet-freebsd/work
>>
>> Hi Tim
>>
>> Sorry, this occurs WITH a completely clean crochet with the ./crochet-freebsd/work directory removed before
>>
>> /bin/sh crochet.sh -c config.sh
>>
>> I suspected a problem in the cross dev area and rebuild xdev with
>>
>> make xdev XDEV=arm XDEV_ARCH=armv6
>>
>> which went through no problem, but as you stated, crochet uses the xdev tools only for uboot builds.
>>
>> From UPDATING in the source tree I see, that bmake is now favored over make as per 16th May. Is this the suspected change?
>
> I believe so. I have not had this problem here, but I'm running
> a relatively recent 10-CURRENT.
>
> You should ask on freebsd-current about this. I suspect the
> root problem affects people building 10-CURRENT on
> FreeBSD 9.
A couple of folks on freebsd-current seem to have tied this
to the -j switch used when building. (Why use of -j eventually
leads to a complaint about -J is still a mystery.)
Could you try editing lib/freebsd.sh to remove the
-j ${WORLDJOBS}
option from the buildworld command and see if that changes
anything?
Tim
More information about the freebsd-arm
mailing list