Am 08/22/12 16:02, schrieb Chris Rees:
> On 22 August 2012 14:32, O. Hartmann <ohart...@mail.zedat.fu-berlin.de> wrote:
>> On 08/22/12 15:05, Chris Rees wrote:
>>> On 22 August 2012 08:18, O. Hartmann <ohart...@zedat.fu-berlin.de> wrote:
>>>> Am 08/21/12 22:53, schrieb Bernhard Fröhlich:
>>>>> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann 
>>>>> <ohart...@zedat.fu-berlin.de> wrote:
>>>>>
>>>>>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477
>>>>>> recompiling the VBox kernel module:
>>>>>>
>>>>>> ===>   Cleaning for virtualbox-ose-kmod-4.1.18_1
>>>>>> ===>   virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile
>>>>>> on FreeBSD < 8.2.
>>>>>> *** [all] Error code 1
>>>>>>
>>>>>> Stop in /usr/ports/emulators/virtualbox-ose-kmod.
>>>>>>
>>>>>> The port compiled prior to the updates of today.
>>>>>>
>>>>>> oh
>>>>>
>>>>> What is the question? We have deprecated < 8.2 almost five months ago 
>>>>> because of the memobj r0 rewrite. You're the first who complains about 
>>>>> this so I'm pretty sure it was the correct decision to move forward. 
>>>>> Please also keep in mind that 8.1 is already EOL.
>>>>>
>>>>
>>>> I do not understand your complains about my mail to the list. For your
>>>> information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as I
>>>> know, considered not to be deprecated by now. If I'm wrong in that, sorry.
>>>
>>> Can you give us the output of make -C
>>> /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please?
>>
>> 1000017
>>
>>>
>>> I think your version of sys/param.h could be out of date.
>>>
>>> Chris
>>
>>
>>
>> As soon as I'm sitting in front of the machine again. But I doubt that
>> the sys/param.h is out of date, since that box has been recompiling
>> FreeBSD 10.0-CURRENT now for almost every day.
> 
> Hm, does that mean that the output you gave me earlier was not from
> the same machine?

No, it is the same box. I tried another FBSD 10.0-CURRENT box today at
my lab and had success ... but see below ...

> 
>> When the problem occured, the change to CLANG 3.2-Beta has just been
>> introduced, installed with "make buildworld installkernel". This
>> procedere also triggers (via /etc/src.conf)
>>
>> PORTS_MODULES=          "x11/nvidia-driver"
>> PORTS_MODULES+=         "emulators/virtualbox-ose-kmod"
> 
> Please remove the quotes! [1]

Better that way?
PORTS_MODULES=          emulators/virtualbox-ose-kmod x11/nvidia-driver

> 
>> the build of the modules for the nvidia GPU and Vbox kernel module.
>>
>> Thanks for your response,
> 
> Something really weird is happening here.  All that is happening is
> that the Makefile is testing against OSVERSION;

I guess this is the result of my unpatience! Usually, I install a new
kernel, reboot it into single user mode, install world and do the
mergemaster stuff.

This time, I still ran the old kernel (but even FreeBSD 10.0-CURRENT)
and made a installworld. The musterius error occured, when the kernel
mod for VBox was about to be compiled.

I updated today my lab's box and since this machine also sucked in the
new CLANG 3.2 stuff, I was really careful about what would happen. I
compiled the system, installed the kernel, booted into single user mode
and did the installworld with all mounted filesystems (and service
ldconfig start issued) - and had no problems!

I did the same today on the faulty box, also no problems after the new
compiled system was properly installed.

I guess I made a conceptional bad mistake and maybe something got
inconsistent due to the new compiler/LLVM stuff? A naiv suggestion.

I guess it is a waste of time to investigate this further - except there
is a hidden issue ...


> 
> .if ${OSVERSION} < 802000
> BROKEN=         Does not compile on FreeBSD < 8.2
> .endif
> 
> Since the result from make -VOSVERSION shows that your OSVERSION is
> indeed above 802000, I am completely at a loss as to what's going on
> :(
> 
> Chris
> 
> [1] http://www.bayofrum.net/~crees/scripts/dont-quote.mk

Thanks for the patience,

Oliver
















Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to