Unhappy with cross-worlding

[Julian Elischer]

On 11/15/10 7:35 PM, Garrett Cooper wrote:
> On Mon, Nov 15, 2010 at 6:24 PM,<rank1seeker at gmail.com>  wrote:
>> So, I have Core 2 Duo, runing as i386.
>> I decided to go for amd64 (it's name, is so deceiving, that I've just
>> recently, accidentaly figured out, that it can be used, with intel CPUs,
>> too) :P
>>
>> 8.1 cross build i386 ->  amd64 has failed
>> World completes successfully, but kernel fails:
>>
>>     mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE
>> -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -
>>     I/usr/obj/amd64/usr/src/sys/GENERIC
>> /usr/src/sys/modules/amr/amr_linux/../../../dev/amr/amr_linux.c
>>     /usr/src/sys/modules/amr/amr_linux/../../../dev/amr/amr_linux.c:43:36:
>> error: machine/../linux/linux.h: No such file or directory
>>     /usr/src/sys/modules/amr/amr_linux/../../../dev/amr/amr_linux.c:44:42:
>> error: machine/../linux/linux_proto.h: No such file or directory
>>     mkdep: compile failed
>>     *** Error code 1
>>     1 error
>>     *** Error code 2
>>     1 error
>>     *** Error code 2
>>     1 error
>>     *** Error code 2
>>     2 errors
>>     *** Error code 2
>>     1 error
>>     *** Error code 2
>>     1 error
>>
>> Then, I've snapped and took an USB stick and did a binary 8.1 amd64 install
>> on it.
>> Booted from it and kernel compiled flawlessly
>>
>> PS:
>> Core 2 Duo - 8.1 GENERIC
>>     Kernel build time:
>>     10:30 -->  i386
>>     08:30 -->  amd64
>>
>>     Yes, without caching!
>>
>>
>> PORTS:
>> ------
>> > From i386, when created USB amd64, I wanted to compile some ports(i386 ->
>> amd64), for that USB stick, on my own.
>> Especially because of port's patches ...
>>
>> DESTIR has been set, as usual, but TARGET, was a no go!
>> Looking into documentation, only /usr/src, supports TARGET, used for cross
>> world compilation.
>> Also, after throwing an eye into /usr/ports/Mk ..., I've concluded that
>> ports, simply can't be cross world compiled, as they don't support it.
>>
>> This 2 problems should be fixed.
>      The best way to work with this is to create a chroot, set the
> appropriate variables (OSVERSION, UNAME_m, UNAME_r, etc), mount the
> /usr/ports via nullfs (if you dare) and then call chroot to access the
> chroot and build to your heart's content. There's an entry in the
> handbook somewhere that better describes how to do it from scratch,
> but my search skills are failing me and I don't have the full docs
> tree checked out.
>      But yes, building amd64 on i386 probably won't work too well :)...

It's supposed to  but hasn't for years.


> HTH,
> -Garrett
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
>