Le 12/09/12 15:54, Tor Lillqvist a écrit :
Well after removing the CC=clang predefine, the build is now proceeding
further, so if it completes, and/or when it stops, I'll rerun
config/make leaving cairo enabled and post the config_host.mk here.
Alex
Le 12/09/12 15:54, Tor Lillqvist a écrit :
Hi Tor,
>> I wonder if you are (unintentionally) building 64-bit code? There
>> might well be some bug in the configure.in, so that when you
>> pre-define CC as just "clang", then the option that tells it to
>> generate 32-bit code doesn't get used.
>
>
> I wonder if you are (unintentionally) building 64-bit code? There
> might well be some bug in the configure.in, so that when you
> pre-define CC as just "clang", then the option that tells it to
> generate 32-bit code doesn't get used.
Furthermore, you pre-defined CC but not CXX, so it is possib
> Tried again, and at least now, it stops somewhere else, so one step further.
That said, the error messages you showed were really strange and
unexpected. Could you post the config_host.mk you get for a
configuration where it does attempt to build cairo, thanks.
I wonder if you are (unintentiona
Le 12/09/12 15:28, Michael Stahl a écrit :
>
>> --disable-rsvg
>
> this doesn't exist and should be --disable-librsvg
> (you should get a warning from configure about it)
Ah, my bad, thanks for that, but certainly no error from what I can see,
it was just silently ignored.
Tried again, and at
On 12/09/12 15:20, Alexander Thurgood wrote:
> Despite my best attempts not to have the module cairo built, it is still
> trying and failing with the following messsage :
> I'm using the following autogen.sh switches :
> --disable-rsvg
this doesn't exist and should be --disable-librsvg
(you shou
