RSS/Atom feed Twitter
Site is read-only, email is disabled

Building GEGL fails on 64 bit Linux system

This discussion is connected to the gegl-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

6 of 6 messages available
Toggle history

Please log in to manage your subscriptions.

Building GEGL fails on 64 bit Linux system scl 06 Feb 06:13
  Building GEGL fails on 64 bit Linux system Matteo F. Vescovi 06 Feb 08:39
   Building GEGL fails on 64 bit Linux system scl 06 Feb 17:31
    Building GEGL fails on 64 bit Linux system Matteo F. Vescovi 07 Feb 07:55
  Building GEGL fails on 64 bit Linux system Nicolas Robidoux 06 Feb 13:24
  [RESOLVED] Building GEGL fails on 64 bit Linux system scl 07 Feb 05:32
scl
2013-02-06 06:13:21 UTC (about 12 years ago)

Building GEGL fails on 64 bit Linux system

Hi,

I'm stuck on building GEGL on a 64 bit Debian Wheezy system. The autogen.sh and make step are ok, but make check shows some tests with flaws or failing:
run-edge-laplace-broken.xml.sh: little differences, but tolerated run-pixelize.xml.sh: little differences, but tolerated run-gamma.xml.sh: failing
Below you find the result of autogen and the failing part of make check. As I found out the reason is the glibc function 'powf' being inaccurate on 64-bit systems, see also the GEGL bugreport [1] and the links there.

I'd like to get the failing test passing and already tried the following without success:
- calling pow and casting to gfloat: #define powf(a,b) ((gfloat)pow(a,b)) - calling the GCC builtin powf function in gamma.c, if compiled on GCC: #ifdef __GNUC__
#define powf(a,b) __builtin_powf(a,b) #endif
- forcing the compiler to use another (hopefully working) math lib: export LIBS="-lm"
- forcing the compiler not to use a C99 compliant powf function: deactivate 'export CFLAGS="-std=gnu99"' - using a binary, older glibc (libc6_2.7-18lenny7_amd64.deb): even simple shell commands refuse to work now because of missing GLIBC symbols
- building an older glibc from scratch (glibc-2.11.3) and installing it to GEGLs $INSTALL_PREFIX: the glibc build fails for unmatching binutils and installing binutils-gold doesn't help.

Now I'm stuck and need your help. If somebody could give me the right clue (preferably this week, if possible) would be very fine.

Thanks in advance and kind regards,

Sven

[1] https://bugzilla.gnome.org/show_bug.cgi?id=666417

*************************** Result of autogen:
------------------
Optional features:
GEGL docs: yes
Build workshop: no
Build website: yes
SIMD: sse:yes mmx:yes
Vala support: yes

Optional dependencies: asciidoc: yes
enscript: yes
Ruby: yes
Lua: yes
Cairo: yes
Pango: yes
pangocairo: yes
GDKPixbuf: yes
JPEG: yes
PNG: yes
OpenEXR: yes
rsvg: yes
SDL: yes
openraw: yes
Jasper: yes
graphviz: yes
avformat: yes
V4L: no
spiro: yes
EXIV: yes
umfpack: yes

Failing part of make check: ---------------------------
make[4]: Entering directory
`/var/lib/jenkins/workspace/gegl-distcheck-master/tests/compositions' [...]
/var/lib/jenkins/workspace/gegl-distcheck-master/tests/compositions/reference/gamma.png and
/var/lib/jenkins/workspace/gegl-distcheck-master/tests/compositions/output/gamma.png differ
wrong pixels : 18160/31680 (57.32%) max Δe : 30.400
avg Δe (wrong) : 1.439(wrong) 0.825(total) FAIL: run-gamma.xml.sh
[...]
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory
`/var/lib/jenkins/workspace/gegl-distcheck-master/tests/compositions' make[3]: *** [check-am] Error 2
make[3]: Leaving directory
`/var/lib/jenkins/workspace/gegl-distcheck-master/tests/compositions' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory
`/var/lib/jenkins/workspace/gegl-distcheck-master/tests/compositions' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory
`/var/lib/jenkins/workspace/gegl-distcheck-master/tests' make: *** [check-recursive] Error 1

Matteo F. Vescovi
2013-02-06 08:39:00 UTC (about 12 years ago)

Building GEGL fails on 64 bit Linux system

Hi!

On Wed, Feb 6, 2013 at 7:13 AM, scl wrote:

I'm stuck on building GEGL on a 64 bit Debian Wheezy system.

[...]

Now I'm stuck and need your help. If somebody could give me the right clue (preferably this week, if possible) would be very fine.

Is there any particular reason why you're not using the Debian official package of GEGL in Wheezy suite? It's updated to 0.2.0, last stable upstream release.

Cheers.

Matteo F. Vescovi
Debian Maintainer
GnuPG KeyID: 83B2CF7A
Nicolas Robidoux
2013-02-06 13:24:10 UTC (about 12 years ago)

Building GEGL fails on 64 bit Linux system

TTBOMK, http://run-edge-laplace-broken.xml is kept there as a reminder that something needs to be looked into. This is what the "broken" suffix means.

scl
2013-02-06 17:31:43 UTC (about 12 years ago)

Building GEGL fails on 64 bit Linux system

On 06.02.13 at 09:39 AM Matteo F. Vescovi wrote:

Is there any particular reason why you're not using the Debian official package of GEGL in Wheezy suite? It's updated to 0.2.0, last stable upstream release.

>
> Matteo F. Vescovi
> Debian Maintainer

Hi Matteo,

yes there is a reason: the failing build is on our buildbot which always builds from the latest git master sources. As I see the GEGL 0.2.0 packages at packages.debian.org are also for amd64 and ia64 architectures. I can't imagine that Debian maintainers never faced such failures in such a central library like glibc. How did you Debian guys solve such problems?

Kind regards,

Sven

scl
2013-02-07 05:32:52 UTC (about 12 years ago)

[RESOLVED] Building GEGL fails on 64 bit Linux system

Thanks to pippin and Massimo the bug is fixed. It turned out that different versions of libjpeg was causing it. Using a PNG image in the test proves more stable.

Kind regards,

Sven

Matteo F. Vescovi
2013-02-07 07:55:16 UTC (about 12 years ago)

Building GEGL fails on 64 bit Linux system

Hi!

On Wed, Feb 6, 2013 at 6:31 PM, scl wrote:

As I see the GEGL 0.2.0 packages at packages.debian.org are also for amd64 and ia64 architectures. I can't imagine that Debian maintainers never faced such failures in such a central library like glibc. How did you Debian guys solve such problems?

Well, I must admit we never faced such issue; and we build for 14 architectures ;-)
Probably we've been really lucky till now :-P

Nice to know the issue has been fixed.

Cheers.

Matteo F. Vescovi
Debian Maintainer
GnuPG KeyID: 83B2CF7A