Re: [E-devel] core/efl-git compile fails....

[Tom H. <tom...@sa...>]

On 01/04/15 15:06, Stefan Schmidt wrote:
> Hello.
>
> On 01/04/15 15:54, Branko wrote:
>> Dne 01. 04. 2015 ob 14:57 je Stefan Schmidt zapisal(a):
>>> Hello.
>>>
>>> On 01/04/15 12:17, Branko wrote:
>>>> Can anyone shed some light into this ?
>>>>
>>>> For several days now I have git enlightenment-core failing to compile at
>>>> the efl stage with:
>>>>
>>>> /var/tmp/portage/dev-libs/efl-9999/temp/ccSTlBEh.ltrans2.ltrans.o: In
>>>> function `evas_image_load_file_data_tgv':
>>>> ccSTlBEh.ltrans2.o:(.text.evas_image_load_file_data_tgv+0x19): undefined
>>>> reference to `emile_image_data'
>>>> /var/tmp/portage/dev-libs/efl-9999/temp/ccSTlBEh.ltrans2.ltrans.o: In
>>>> function `evas_image_load_file_head_tgv':
>>>> ccSTlBEh.ltrans2.o:(.text.evas_image_load_file_head_tgv+0x16): undefined
>>>> reference to `emile_image_head'
>>>> /var/tmp/portage/dev-libs/efl-9999/temp/ccSTlBEh.ltrans2.ltrans.o: In
>>>> function `evas_image_load_file_close_tgv':
>>>> ccSTlBEh.ltrans2.o:(.text.evas_image_load_file_close_tgv+0x8): undefined
>>>> reference to `emile_image_close'
>>>> /var/tmp/portage/dev-libs/efl-9999/temp/ccSTlBEh.ltrans2.ltrans.o: In
>>>> function `evas_image_load_file_open_tgv':
>>>> ccSTlBEh.ltrans2.o:(.text.evas_image_load_file_open_tgv+0x19): undefined
>>>> reference to `emile_image_tgv_file_open'
>>>> collect2: error: ld returned 1 exit status
>>>> Makefile:18238: recipe for target 'bin/evas/evas_cserve2_slave' failed
>>> Hmm, so a problem with linking to emile which was merged recently into efl.
>>>
>>> I wonder why this happes for you as it does work fine for me and our
>>> autobuilder is also reporting now problems.
>>>
>>> What are the configure options you build it with?
>> It is part of "ixit" overlay in Gentoo.
>> build.log shows:
>>
>> ./configure --prefix=/usr --build=x86_64-pc-linux-gnu
>> --host=x86_64-pc-linux-gnu --mandir=/usr/share/man
>> --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
>> --localstatedir=/var/lib --disable-dependency-tracking
>> --disable-silent-rules --libdir=/usr/lib64 --with-crypto=openssl
>> --with-x --with-x11=xlib --with-opengl=full --enable-egl
>> --enable-wayland --enable-drm --enable-avahi --disable-cxx-bindings
>> --disable-doc --disable-fb --enable-fontconfig --disable-fribidi
>> --enable-gstreamer1 --disable-harfbuzz --disable-ibus --enable-nls
>> --disable-physics --enable-pulseaudio --enable-audio --disable-scim
>> --enable-sdl --disable-static --enable-systemd --disable-tslib
>> --enable-v4l2 --disable-xim --enable-xine --enable-image-loader-bmp
>> --enable-image-loader-eet --enable-image-loader-generic
>> --enable-image-loader-ico --enable-image-loader-jpeg
>> --enable-image-loader-psd --enable-image-loader-pmaps
>> --enable-image-loader-tga --enable-image-loader-wbmp
>> --enable-image-loader-gif --disable-image-loader-jp2k
>> --enable-image-loader-png --enable-image-loader-tiff
>> --disable-image-loader-webp --enable-image-loader-xpm --enable-cserve
>> --enable-libmount --enable-threads --enable-xinput22 --disable-gesture
>> --disable-gstreamer --disable-lua-old --disable-multisense
>> --disable-tizen --disable-xinput2 --disable-xpresent --disable-pixman
>> --disable-pixman-font --disable-pixman-rect --disable-pixman-line
>> --disable-pixman-poly --disable-pixman-image
>> --disable-pixman-image-scale-sample --with-profile=release
>> --with-glib=yes --with-tests=none
>> --enable-i-really-know-what-i-am-doing-and-that-this-will-probably-break-things-and-i-will-fix-them-myself-and-send-patches-aba
>
> OK, so this is a classical "i want to toggle every configure knob
> available" problem.
>
> If the maintainer of the overlay wants to do all this he is on its own
> and he would be your point of contact. Sorry, but we expect people that
> toggle all things things are able to help themselves. Look at the last
> --enable line...
>
> I can see that this is not your fault as you are simply using the
> overlay but it is also nothing we can help you directly with. The build
> works fine for the default configure settings, on our autobuilder which
> tests some more and on various developer machines.
>
> I see only two options for you here:
> 1) Report the problem to the package maintainer and let him deal with it
> 2) Build if without all these special configure options and come back to
> us for support once you no longer need to set
>
> --enable-i-really-know-what-i-am-doing-and-that-this-will-probably-break-things-and-i-will-fix-them-myself-and-send-patches-aba to make configure pass.

Even though he wrongfully declared that he really knows what he's doing 
and he's aware that this will probably break things, we should still not 
break things. :) If I had to guess, Cedric forgot to add the deps to 
something that's only compiled with these specific options.

--
Tom.