[Vm-dev] Problem with building the PharoVM: cairo tar -J option invalid

[phil at highoctane.be]

No, it does not.

One has to put /opt/local/bin in front of its path in .profile to get
these in priority.
Which I do not do since I do not want Xcode and other chains use
MacPorts instead of the native BSD tools when doing iOS/Cocoa
development.

I one does only Pharo on the machine, no issue, but I do have 3 or 4
toolchains for different platforms in my box.

Phil

2013/2/25 Esteban Lorenzano <estebanlm at gmail.com>:
>
> mmm... but the port install shouldn't update the paths?
>
> On Feb 24, 2013, at 4:56 PM, "phil at highoctane.be" <phil at highoctane.be> wrote:
>
>>
>> Just a note on a gotcha:
>>
>> port install gnutar
>>
>> will install tar but depending on how one's PATH is set, which tar
>> must answer the right one or it will fail.
>>
>> So, I did:
>>
>> export PATH=/opt/local/bin:$PATH
>>
>> before the
>>
>> make
>>
>> in build/
>>
>> I got a Pharo.app in results now :-)
>>
>> Still, the getImage.sh in image/ still contains wrong pathes.
>>
>> These are the ones that seem to work (yes, it should point to the files thing).
>>
>> PREBUILT_IMAGE_URL="https://ci.inria.fr/pharo/view/VM/job/Cog-Git-Tracker/lastSuccessfulBuild/artifact/vmmaker-image.zip"
>> URL="https://ci.inria.fr/pharo/view/1.4/job/Pharo-1.4/lastSuccessfulBuild/artifact/"
>> VERSION="Pharo-1.4"
>>
>> Maybe the ImageConfiguration.st could benefit from having:
>>
>>   stream << '"Configuration for Building Pharo
>> ---------------------------------------------------"'; cr.
>>        stream << 'PharoVMBuilder build.'; cr.
>>
>>
>> Thanks for the helping hand!
>>
>> Phil
>>
>>
>>
>>
>> 2013/2/24 Esteban Lorenzano <estebanlm at gmail.com>:
>>>
>>> Hi,
>>>
>>> you need a
>>>
>>> port install gnutar
>>>
>>> you can find this info in HOWTOBUILD file :)
>>>
>>> Esteban
>>>
>>> On Feb 24, 2013, at 12:26 PM, "phil at highoctane.be" <phil at highoctane.be> wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> I was looking at the fixes in the VM (crashes in the last week).
>>>>
>>>> Now, on OSX, I see that there are things (cairo, freetype, ...) loaded
>>>> based on a pkg-config something.
>>>>
>>>> But at one point (when "unpacking cairo" when doing make), I got this:
>>>>
>>>> [  2%] Built target freetype2
>>>> [  3%] Built target FT2Plugin
>>>> [  4%] Built target pkg-config
>>>> [  5%] Built target libpng
>>>> [  6%] Built target pixman
>>>> [  6%] Unpacking cairo ...
>>>> tar: l'option -- J est invalide
>>>> Pour en savoir davantage, faites: << tar --help >> ou << tar --usage >>.
>>>> make[2]: *** [thirdparty/cairo/cairo-1.12.6/touch.cmake] Error 64
>>>> make[1]: *** [thirdParty/cairo/CMakeFiles/cairo.dir/all] Error 2
>>>> make: *** [all] Error 2
>>>>
>>>>
>>>> Never got anything like that in the previous builds. So, I wonder.
>>>>
>>>> I did a PharoVMBuilder build in the latest generator image.
>>>>
>>>> Cmake didn't complained in build/ but make does...
>>>>
>>>> Any idea?
>>>>
>>>> Phil
>>>
>>>
>
>