[CFT] Calculating dependencies inside chroots

olli hauer ohauer at gmx.de
Sun Sep 29 14:43:13 EDT 2013


On 2013-09-29 20:25, Joe Marcus Clarke wrote:
> On 9/29/13 1:15 PM, olli hauer wrote:
>> On 2013-09-29 17:06, Chris Rees wrote:
>>> On 17/09/2013 21:58, olli hauer wrote:
>>>> On 2013-09-17 22:21, Chris Rees wrote:
>>>>> On 2013-09-17 21:12, olli hauer wrote:
>>>>>> A small test build is running just now,
>>>>>>
>>>>>> to overcome the xz issue I temporary disabled the folllowing in bsd.port.mk
>>>>>>
>>>>>> #.if defined(USE_XZ) && ( (${OSVERSION} >= 900000 && ${OSVERSION} <
>>>>>> 900012) || ${OSVERSION} < 800505 )
>>>>>> #EXTRACT_DEPENDS+=  ${LOCALBASE}/bin/xz:${PORTSDIR}/archivers/xz
>>>>>> #.endif
>>>>>>
>>>>>>
>>>>>> Since there where some other ports like db42 added to the mix where db48 is
>>>>>> definded per etc/env/build.8.4-amd... I suspect there is something missing.
>>>>>>
>>>>>> However, during the build self the defined db48 is used and not db42.
>>>>> Probably the ordering of buildenvNoHost and buildenv :(
>>>>>
>>>>> I'm going to have to give up for tonight I'm afraid, but I'll hopefully have it fixed soon.
>>>>>
>>>>> Chris
>>>>
>>>> Will do some short tests and swap back because I have to run some builds for production tonight ...
>>>> (it would be really helpful to save time by switching off the ports regression tests, they are consuming meanwhile 50+% of the build time ...)
>>>>
>>>> First result: ff HOST_WORKDIR set to default '' and the xz check is enabled again in bsd.port.mk, then the xz issue is present again.
>>>>
>>>>
>>>> The deinstallation will free 46 MB
>>>> [1/1] Deleting perl-5.14.4...Removing stale symlinks from /usr/bin...
>>>>       Removing /usr/bin/perl
>>>>       Removing /usr/bin/perl5
>>>> Done.
>>>> Cleaning up /etc/make.conf... Done.
>>>> Cleaning up /etc/manpath.config... Done.
>>>>    done
>>>>
>>>> === Checking filesystem state
>>>>
>>>> === Checking filesystem state after all packages deleted
>>>> ================================================================
>>>> build of /usr/ports/lang/perl5.14 ended at Tue Sep 17 20:56:51 UTC 2013
>>>>
>>>> ==> /tb/8.4-amd64-porter/tmp/make.log1 <==
>>>> ===>  xz-5.0.4 is already in the base system.
>>>> *** Error code 1
>>>>
>>> OK, so I've finally worked it out, after being able to give it a bit of thought.
>>>
>>> The src bit isn't mounted inside the chroot, so buildenv can't get uname, and from inspection I'm guessing it is blank.
>>>
>>> I now mount src inside the chroot-- please try a final patch...
>>>
>>> http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-8.diff
>>>
>>> Thanks massively for your time testing this.
>>>
>>
>>
>> Hi Chris,
>>
>> patch8 applied to tinderbox HEAD but I get the same issue with xz.
>> I tried a port that was build a minute before without the patch
>>
>> rm -f $tb/pakages/$build/All/cvs2svn*
>>
>> # rebuild devel/cvs2svn
>>
>> ==> /tb/a/builds/8.4-amd64-porter/tmp/make.log1 <==
>> ===>  xz-5.0.4 is already in the base system.
>> *** Error code 1
>> Stop in /a/ports/archivers/xz.
>>
>>
>> Inspecting the mount points during the build with without the patch.
>>
>> # withot patch
>> #
>> /dev/md10                            /data/tb/jails                                        ufs       rw,nosuid,async,noatime         2 2
>> /dev/md11                            /data/tb/a/builds                                     ufs       rw,nosuid,async,noatime         2 2
>> /usr/svn_ports                       /data/tb/a/builds/8.4-amd64-porter/a/ports            nullfs    ro              0 0
>> /z2/FreeBSD_src/RELENG_8_4/src       /data/tb/a/builds/8.4-amd64-porter/usr/src            nullfs    ro              0 0
>> devfs                                /data/tb/a/builds/8.4-amd64-porter/dev                devfs     rw,multilabel   0 0
>> /mirror/distfiles                    /data/tb/a/builds/8.4-amd64-porter/distcache          nullfs    rw              0 0
>> /data/tb/a/ccache/8.4-amd64          /data/tb/a/builds/8.4-amd64-porter/ccache             nullfs    rw              0 0
>> /data/tb/a/options/8.4-amd64-porter  /data/tb/a/builds/8.4-amd64-porter/var/db/ports       nullfs    rw              0 0
>> #
>> # missing mountpoints with patch
>> linprocfs                            /data/tb/a/builds/8.4-amd64-porter/compat/linux/proc  linprocfs rw              0 0
>> procfs                               /data/tb/a/builds/8.4-amd64-porter/proc               procfs    rw              0 0
>>
>>
>>
>> # with patch
>> #
>> /dev/md10                            /data/tb/jails                                        ufs      rw,nosuid,async,noatime         2 2
>> /dev/md11                            /data/tb/a/builds                                     ufs      rw,nosuid,async,noatime         2 2
>> /usr/svn_ports                       /data/tb/a/builds/8.4-amd64-porter/a/ports            nullfs   ro              0 0
>> /z2/FreeBSD_src/RELENG_8_4/src       /data/tb/a/builds/8.4-amd64-porter/usr/src            nullfs   ro              0 0
>> devfs                                /data/tb/a/builds/8.4-amd64-porter/dev                devfs    rw,multilabel   0 0
>> /mirror/distfiles                    /data/tb/a/builds/8.4-amd64-porter/distcache          nullfs   rw              0 0
>> /data/tb/a/ccache/8.4-amd64          /data/tb/a/builds/8.4-amd64-porter/ccache             nullfs   rw              0 0
>> /data/tb/a/options/8.4-amd64-porter  /data/tb/a/builds/8.4-amd64-porter/var/db/ports       nullfs   rw              0 0
>>
>> # additional mountpoint
>> /z2/FreeBSD_src/RELENG_8_4/src       /data/tb/jails/8.4-amd64/src                          nullfs   rw              0 0
>>
>>
>> I've uploaded the xz and neon log, they can be found here
>> http://people.freebsd.org/~ohauer/logs/xz-5.0.4.log
>> http://people.freebsd.org/~ohauer/logs/neon29-0.29.6_4.log
>>
>> Maybe they help to find the issue.
>>
>> Perhaps something is broken in my setup.
>> Is the build running on your system in case HOST_WORKDIR is set?
> 
> For xz, you're trying to build it on 8.4, but it _is_ already in the base system (OSVERSION >= 800505).  The error you're seeing is expected.
> 
> Neon built fine, but those mount points need to be sorted out.
> 

Hi Joe,

the strange thing is I see the xz error only with the apllied patch.

What is the best place to add 'mount -p' commands into tinderbox?

I tried a couple of places but the output is not in the logs except
from lib/buildscript but inside the jail no mountpoints are displayed.

-- 
olli


More information about the tinderbox-list mailing list