I realize this is a really old thread, but I happen to be building xcb
myself at the moment, and ran into the same issue. So I did as was suggested
-- built python 2.6.4 with a HOST target and installed it in /host_usr.
That worked fine for my build -- however, having it in /host_usr, and having
/host_usr first in $PATH, breaks sb-conf. Once I figured out that was the
problem, I removed it from /host_usr and sb-conf went back to working fine
again. I'm also not sure how having it in /host_usr would work, as far as
getting it into everyone's scratchbox environment (even if having it there
didn't break sb-conf).
I don't want people to have to build it themselves, in all their targets, so
is there any reason not to just go ahead and install it alongside the 2.3
one that comes with core (ie., into /scratchbox/tools/{bin,include,lib}? I
can name the 2.6 executable in bin python2.6 so it doesn't conflict with the
2.3 one, since I only need 2.6 specifically for building xcb-proto/xcb (and
I can point them to the 2.6 one for their build).
Thanks,
Diane
On Tue, Sep 23, 2008 at 2:51 AM, Jussi Hakala <jussi.hak...@movial.fi>wrote:
> Daniel Bainton wrote:
>
>> If that's the case, we have to fix it...
>>>
>>
>> Just do a "echo $PATH" in SB. I doubt /host_usr is before the devkits
>> and core for you either. Isn't there a bug for this? Atleast it's been
>> mentioned in IRC... :)
>>
>
> Fixed in the vcs head.
>
> Yeah, the bugzilla is still offline...
>
> Regards,
>
> Jussi
>
>
> _______________________________________________
> Scratchbox-users mailing list
> Scratchbox-users@lists.scratchbox.org
> http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
>
_______________________________________________
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
