[Gambas-user] gambas on gentoo

[Dominique Michel]

Le Wed, 5 Feb 2014 20:38:40 +0100,
Dominique Michel <dominique.michel at ...3298...> a écrit :

> Le Tue, 4 Feb 2014 09:13:08 +0100,
> Dominique Michel <dominique.michel at ...3298...> a écrit :
> 
> > Hi all,
> > 
> > First, thank you for gambas. Even if a Linux system is more
> > complicated, it remain me my old time with an Amiga in the eighties.
> > Simple, powerful and efficient.
> > 
> > gambas is not in portage currently, and it is an old bug report with
> > an ebuild at https://bugs.gentoo.org/show_bug.cgi?id=302136

Some more questions.
gb.gtk depend on cairo. Doest it mean gb.cairo is mandatory if I want
gb.gtk?

gb.media depend on gstreamer-video. On gentoo, it is, among other
video plugins:
gst-plugins-dts: for MPEG-1/2 video encoding
gst-plugins-x264: plugin for gstreamer ??
gst-plugins-xvid: for XviD (MPEG-4) video encoding/decoding
gst-plugins-xvideo: plugin for gstreamer ??
Which one is the good one?

Thanks,
Dominique
> > 
> > I just updated the ebuild to gambas-3.5.2. When installing it, I get
> > the following warnings from portage:
> 
> More important, another user get the following error:
> 
> I got a lot of "symbol lookup
> error: /var/tmp/portage/dev-lang/gambas-3.5.2/image//usr/lib64/gambas3/gb.image.so:
> undefined symbol: pow" Therefor gambas it's unusable for me.
> 
> ||
> || Unable to compile gb.desktop
> || Unable to compile gb.eval.highlight
> || Unable to compile gb.gui.base
> || Unable to compile gb.form
> || Unable to compile gb.form.dialog
> || Unable to compile gb.form.mdi
> || Unable to compile gb.db.form
> || Unable to compile gb.report
> || Unable to compile gb.chart
> || Unable to compile gb.net.pop3
> || Unable to compile gb.memcached
> || Unable to compile gb.map
> || Unable to compile gambas3
> ||
> 
> I added -lm to ldflags in makefile but with no use. 
> 
> #endquote
> 
> Do you know which dependency is missing, and if not, what more is
> needed to know it?
> 
> Dominique
> 
> > 
> >  * QA Notice: Package triggers severe warnings which indicate that
> > it
> >  *            may exhibit random runtime failures.
> >  * jit_codegen.cpp:6649:33: warning: dereferencing type-punned
> > pointer will break strict-aliasing rules [-Wstrict-aliasing]
> > 
> > 
> >  * QA Notice: Package triggers severe warnings which indicate that
> > it
> >  *            may exhibit random runtime failures.
> >  * framebufferobject.c:108:2: warning: implicit declaration of
> > function 'GenerateMipmapEXT' [-Wimplicit-function-declaration]
> >  * framebufferobject.c:169:2: warning: implicit declaration of
> > function 'GetRenderbuffe
> > 
> > and
> > 
> >  * QA Notice: This package installs one or more .desktop files that
> > do not
> >  * pass validation.
> >  * 
> >  * 	/usr/share/applications/gambas3.desktop: error: (will be
> >    fatal in the future): value "gambas3.png" for key "Icon" in group
> >    "Desktop Entry" is an icon name with an extension, but there
> > should be no extension as described in the Icon Theme Specification
> > if the value is not an absolute path
> >  * 	/usr/share/applications/gambas3.desktop: warning: value
> >    "Application;Development;" for key "Categories" in group "Desktop
> >    Entry" contains a deprecated value "Application"
> >  * 
> > 
> > A question: When compiling, is it possible that elibtoolize and
> > eautoreconf only scan what is needed to be able to run a gambas
> > software, and after that, to only compile and install that part of
> > gambas (I think the interpreter and its libraries). And when
> > installed, to make separated builds for each other components?
> > 
> > My concern is that portage compile every thing, and as the gambas
> > executables depends on the interpreter and the lib, it is no need to
> > recompile and reinstall every thing in most cases, if not all cases,
> > when the interpreter and the libs are recompiled by portage during a
> > system update.
> > 
> > Such an update is a 3 steps process: 1) the updated packages are
> > updated by portage, 2) the obsoleted packages are removed, and 3)
> > revdep-rebuild check the reverse dependencies in the installed
> > system and tell portage to reinstall the broken packages from their
> > sources. In case of 3), it would be a waste of time and energy to
> > recompile the whole gambas if just one of its executable or lib get
> > broken, and it would be much better if I can make several ebuilds
> > instead of only one.
> > 
> > Also, I am trying now to get a live ebuild to work from the svn, and
> > it would obviously be more important with it if can spilt the ebuild
> > into several ones.
> > 
> > Best regards,
> > Dominique
> > 
> > ------------------------------------------------------------------------------
> > Managing the Performance of Cloud-Based Applications
> > Take advantage of what the Cloud has to offer - Avoid Common
> > Pitfalls. Read the Whitepaper.
> > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Gambas-user mailing list
> > Gambas-user at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/gambas-user
> 
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> Gambas-user mailing list
> Gambas-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-user