So I tried to reproduce some of the pathes you have by the following:
sudo mkdir /usr/src
sudo ln -s /usr/local/include /usr/src/include
sudo ln -s /usr/local/include/lzma.h /usr/include/lzma.h
sudo ln -s /usr/local/include/lzma.h /usr/include/lzma/lzma.h
After Neither of these worked perl Build
but running
C_INCLUDE_PATH=/usr/local/include/ perl Build
did the trick. Or so I thought. after compiling for 10 more minutes it
stopped with this:
Undefined symbols for architecture x86_64:
"_lzma_code", referenced from:
_LZMADecode in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
_LZMAPostEncode in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
_LZMAEncode in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
"_lzma_end", referenced from:
_LZMASetupDecode in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
_LZMASetupEncode in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
_LZMACleanup in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
"_lzma_lzma_preset", referenced from:
_TIFFInitLZMA in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
_LZMAVSetField in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
"_lzma_memusage", referenced from:
_LZMADecode in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
"_lzma_stream_decoder", referenced from:
_LZMAPreDecode in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
_LZMADecode in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
"_lzma_stream_encoder", referenced from:
_LZMAVSetField in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
_LZMAPreEncode in libwxtiff-3.0.a(wxtiff_tif_lzma.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
make: ***
[/Users/gabor/.cpanm/work/1410554102.71137/Alien-wxWidgets-0.65/wxWidgets-3.0.0/bld/lib/libwx_osx_cocoau_core-3.0.0.0.0.dylib]
Error system: make all: 512 at Build line 60.
Probably unrelated, but when running perl Build.PL I got
Possible precedence issue with control flow operator at
lib/Alien/wxWidgets/Utility.pm line 77.
line 77 is : return $^O =~ /MSWin32/ and $cc =~ /^cl/i;'
which is indeed not really good. after copying that line to a.pl
B::Deparse tells me:
perl -MO=Deparse,-p a.pl
((return ($^O =~ /MSWin32/)) and ($cc =~ /^cl/i));
So the second condition is lost.
Gabor
On Fri, Sep 12, 2014 at 8:36 PM, Steve Cookson <steve.cook...@sca-uk.com>
wrote:
>
> Hi Gabor,
>
> On 12/09/14 13:03, Gabor Szabo wrote:
>>
>> OTOH
>>
>> $ locate lzma.h
>> /usr/local/Cellar/xz/5.0.5/include/lzma/lzma.h
>> /usr/local/Cellar/xz/5.0.5/include/lzma.h
>> /usr/local/include/lzma.h
>>
>> so it is really on the system but apparently Alien::wxWidgets did not
find it.
>
> I get:
>
> image@image-TAICHI21A:~$ locate lzma.h
> /usr/include/lzma.h
> /usr/include/lzma/lzma.h
> /usr/src/linux-headers-3.13.0-24/include/linux/decompress/unlzma.h
> /usr/src/linux-headers-3.13.0-24-generic/include/config/decompress/lzma.h
> /usr/src/linux-headers-3.13.0-24-generic/include/config/have/kernel/lzma.h
> /usr/src/linux-headers-3.13.0-24-generic/include/config/rd/lzma.h
> /usr/src/linux-headers-3.13.0-29/include/linux/decompress/unlzma.h
> /usr/src/linux-headers-3.13.0-29-generic/include/config/decompress/lzma.h
> /usr/src/linux-headers-3.13.0-29-generic/include/config/have/kernel/lzma.h
> /usr/src/linux-headers-3.13.0-29-generic/include/config/rd/lzma.h
> /usr/src/linux-headers-3.13.0-30/include/linux/decompress/unlzma.h
> /usr/src/linux-headers-3.13.0-30-generic/include/config/decompress/lzma.h
> /usr/src/linux-headers-3.13.0-30-generic/include/config/have/kernel/lzma.h
> /usr/src/linux-headers-3.13.0-30-generic/include/config/rd/lzma.h
> /usr/src/linux-headers-3.13.0-32/include/linux/decompress/unlzma.h
> /usr/src/linux-headers-3.13.0-32-generic/include/config/decompress/lzma.h
> /usr/src/linux-headers-3.13.0-32-generic/include/config/have/kernel/lzma.h
> /usr/src/linux-headers-3.13.0-32-generic/include/config/rd/lzma.h
> /usr/src/linux-headers-3.13.0-35/include/linux/decompress/unlzma.h
> /usr/src/linux-headers-3.13.0-35-generic/include/config/decompress/lzma.h
> /usr/src/linux-headers-3.13.0-35-generic/include/config/have/kernel/lzma.h
> /usr/src/linux-headers-3.13.0-35-generic/include/config/rd/lzma.h
>
> So I guess the difference is /local/. I'll look to see why mys system
looks there, but maybe you could just do a symlink?
>
> regards
>
> Steve.
