I think I see where the problem was. Below is a compilation of engage
w/o emotion. It screams for Emotion.h and aborts. Looking closely, it
seems to come from
/usr/include/ewl/ewl_media.h:4:21
and this is perhaps because I built EWL with emotion support. So if I
understand correctly now, if I build EWL w/o emotion the rest of the
apps bar eclair should build fine. ;-)
Now that's some good news.
[SNIP]
icon.c:435: warning: assignment makes pointer from integer without a cast
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../lib -I/usr/local/include
-I../lib -I/usr/local/include -I/usr/X11R6/include
-I/usr/local/include -I/usr/X11R6/include -I/usr/include
-I/usr/include -I/usr/include/ewl -I/usr/local/include
-I/usr/X11R6/include -O2 -g -pipe -m32 -march=i386 -mtune=pentium4
-MT engage-window.o -MD -MP -MF ".deps/engage-window.Tpo" -c -o
engage-window.o `test -f 'window.c' || echo './'`window.c; \
then mv -f ".deps/engage-window.Tpo" ".deps/engage-window.Po"; else rm
-f ".deps/engage-window.Tpo"; exit 1; fi
In file included from /usr/include/ewl/Ewl.h:327,
from config.c:8:
/usr/include/ewl/ewl_media.h:4:21: Emotion.h: No such file or directory
config.c: In function `od_config_menu_init':
config.c:252: warning: passing arg 3 of `ewl_embed_evas_set' makes
pointer from integer without a cast
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../lib -I/usr/local/include
-I../lib -I/usr/local/include -I/usr/X11R6/include
-I/usr/local/include -I/usr/X11R6/include -I/usr/include
-I/usr/include -I/usr/include/ewl -I/usr/local/include
-I/usr/X11R6/include -O2 -g -pipe -m32 -march=i386 -mtune=pentium4
-MT engage-tray.o -MD -MP -MF ".deps/engage-tray.Tpo" -c -o
engage-tray.o `test -f 'tray.c' || echo './'`tray.c; \
then mv -f ".deps/engage-tray.Tpo" ".deps/engage-tray.Po"; else rm -f
".deps/engage-tray.Tpo"; exit 1; fi
make[3]: *** [engage-config.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/home/didier/rpmbuild/BUILD/engage-0.0.9/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/didier/rpmbuild/BUILD/engage-0.0.9/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/didier/rpmbuild/BUILD/engage-0.0.9'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.23780 (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.23780 (%build)
--
With kind regards,
Didier.
------------
Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe
Didier F.B Casse
PhD candidate, Singapore Synchrotron Light Source (SSLS)
National University of Singapore.
On 6/1/05, Nathan Ingersoll <[EMAIL PROTECTED]> wrote:
> No, it's a build option for EWL. There shouldn't be any issues
> compiling without that support, I know it builds fine without it on my
> OS X systems.
>
> On 6/1/05, Andrew Elcock <[EMAIL PROTECTED]> wrote:
> > Didier Casse wrote:
> > > On 6/1/05, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> > >
> > >>On Wed, 25 May 2005 11:23:33 +0800 Didier Casse <[EMAIL PROTECTED]>
> > >>babbled:
> > >>
> > >>
> > >>>Hi all,
> > >>> I'm pleased to announce that I've been sponsored by Tom
> > >>>'spot' Callaway (from RedHat) to push DR17+EFL in the Fedora Core
> > >>>Extras repository. I've been granted CVS access to it. I've yet to go
> > >>>for a formal review process of my packages. Well I've got to cleanup
> > >>>the packages first.
> > >>>
> > >>>But the important thing is that we made a step forward. If everything
> > >>>goes well with proper timing, DR17 should be available for FC4 users
> > >>>directly from Yum. i.e. the extras would be enable by default in the
> > >>>FC4 /etc/yum.conf file.
> > >>
> > >>cool :) nice nice. all happy.
> > >
> > >
> > > But there's a bad news to it also. Instead of saying EFLs, I should
> > > now say some EFLs. :-(
> > >
> > > emotion BuildRequires /usr/bin/xine-config which is provided in FC by
> > > the package xine-lib-devel. Well this xine-lib-devel or xine-lib or
> > > associated package libfame is NOT and will NOT get into either Fedora
> > > Core CDs or FC extras repository due to legal/patent issues.
> > >
> > > It means that apps that depend on emotion or BuildRequires:
> > > emotion-devel will not make it to FC extras and still has to stay in a
> > > 3rd party repository.
> > >
> > > So stuff like
> > >
> > > eclair.spec
> > > emotion.spec
> > > engage.spec
> > > e_utils.spec
> > > ewl.spec
> > > examine.spec
> > >
> > > will not make it to FC extras unless BuildRequires: emotion-devel
> > > becomes optional. But so far when i removed the emotion-devel Build
> > > Requirement, the above packages (bar emotion of course) failed to
> > > compile.
> > >
> > >
> >
> > do engage, ewl, e_utils and examine really require emotion?
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by Yahoo.
> > Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> > Search APIs Find out how you can build Yahoo! directly into your own
> > Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> > _______________________________________________
> > enlightenment-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> >
>
--
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
