[gentoo-user] zlib and WOFF

[gentoo-user] zlib and WOFF

[luis jure]

i've been trying to install a recent version of media-sound/lilypond (music
typesetting software) for some time, but it always fails with this message:

/usr/lib64/libz.so: invalid ELF header
Could not find the zlib library which is needed to understand WOFF

i had this same problem some time ago, and after much trial and error i
managed to solve it, downgrading zlib to an older version (zlib-1.2.3-r1).
but having such an old version of zlib is inconvenient for other reasons.

any idea what's wrong here? who's the culprit? zlib? lilypond? me?

best,


lj

Re: [gentoo-user] zlib and WOFF

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 321 bytes --]

>
> i've been trying to install a recent version of media-sound/lilypond (music
> typesetting software) for some time, but it always fails with this message:
>
> /usr/lib64/libz.so: invalid ELF header
> Could not find the zlib library which is needed to understand WOFF
>
>
I'd re-emerge zlib - looks like its corrupted.

[-- Attachment #2: Type: text/html, Size: 494 bytes --]

Re: [gentoo-user] zlib and WOFF

[luis jure]

on 2011-04-24 at 14:31 Adam Carter wrote:

>> /usr/lib64/libz.so: invalid ELF header
>> Could not find the zlib library which is needed to understand WOFF
>>
>>
> I'd re-emerge zlib - looks like its corrupted.


as i said in my previous post, i can compile lilypond with zlib-1.2.3-r1,
but it fails with 1.2.5-r2 (i also tried the "dead" zlib-1.2.4). obviously
i unmerged and re-emerged different versions of zlib several times, always
with the same result. that's why i'm asking on the list. according to
google, no-one is having this problem... 


best,

lj

Re: [gentoo-user] zlib and WOFF

[Volker Armin Hemmann]

On Sunday 24 April 2011 01:07:57 luis jure wrote:
> i've been trying to install a recent version of media-sound/lilypond (music
> typesetting software) for some time, but it always fails with this message:
> 
> /usr/lib64/libz.so: invalid ELF header
> Could not find the zlib library which is needed to understand WOFF
> 
> i had this same problem some time ago, and after much trial and error i
> managed to solve it, downgrading zlib to an older version (zlib-1.2.3-r1).
> but having such an old version of zlib is inconvenient for other reasons.
> 
> any idea what's wrong here? who's the culprit? zlib? lilypond? me?
> 
> best,
> 
> 
> lj

http://bugs.gentoo.org/show_bug.cgi?id=311147

you might add yourself to that bug mentioning lillypond.

Another case of devs not thinking big enough.

Re: [gentoo-user] zlib and WOFF

[luis jure]

on 2011-04-24 at 13:48 Volker Armin Hemmann wrote:


> http://bugs.gentoo.org/show_bug.cgi?id=311147
>
>you might add yourself to that bug mentioning lillypond.

reading the thread, i don't think it's the same bug. anyway, i'll follow
your advise (and stroller's) and i'll file a bug both for zlib and
lilypond. i'll also ask at the lilypond mailing list.

best,

lj

Re: [gentoo-user] zlib and WOFF

[Stroller]

On 24/4/2011, at 5:07am, luis jure wrote:
> ...
> any idea what's wrong here? who's the culprit? zlib? lilypond? me?

I looked at Lilypond myself a week or two ago, and installed their binary package under OS X.

Whilst glancing at their documentation again now the wording I'm finding is not so strong, I had the impression that Lilypond was a bit finicky and difficult to compile. Again, I can't immediately find the reference, but I thought that it was sufficiently demanding in terms of environment and versioning that they provided a VM for development purposes.

I would guess that the fault is simply versioning. I would suggest filing a bug, but also trying to resolve this though the Lilipond IRC channel &/or mailing list - Lilipond's developers may well have seen this before.

Stroller.

Re: [gentoo-user] zlib and WOFF

[Enrico Weigelt]

* luis jure <ljc@internet.com.uy> wrote:

> /usr/lib64/libz.so: invalid ELF header
> Could not find the zlib library which is needed to understand WOFF

Do you have an multilib installation (32 and 64 bit libraries) ?


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@metux.de
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------

Re: [gentoo-user] zlib and WOFF

[luis jure]

on 2011-05-07 at 12:58 Enrico Weigelt wrote:

>Do you have an multilib installation (32 and 64 bit libraries) ?

no, it's pure 64 bits. 

i found out what the problem was at Gentoo's Bugzilla [1]. 

for some reason the file /usr/lib64/libz.so is a text file, the solution
was linking it to the real .so file at /lib64/libz.so (or /lib64/libz.so.1
in my case). after that lilypond builds just fine.

best,

lj


[1] http://bugs.gentoo.org/show_bug.cgi?id=334835

Re: [gentoo-user] zlib and WOFF

[Stroller]

Necro bump!


On 8 May 2011, at 02:31, luis jure wrote:
> …
> for some reason the file /usr/lib64/libz.so is a text file, the solution
> was linking it to the real .so file at /lib64/libz.so (or /lib64/libz.so.1
> in my case). after that lilypond builds just fine.

This isn't the best fix, IMO. AIUI these bugs have been closed WONTFIX in favour of bug #4411 for years. [1] [2]

Seems to me like next time you re-emerge zlib your symlink will get overwritten.

You don't give the full error message your original post, but I saw it for myself yesterday (sorry I no longer have it handy) and it is in fact fontforge that gives this error, as it's called during Lilypond's build process.

This is now logged as bug 367425 [3], and there is a patch for fontforge there.

For the benefit of posterity and anyone else who discovers this bug via google (this is not aimed specifically at Luis), IMO the correct fix for this is:

   mkdir -p /usr/local/portage/media-gfx/fontforge/files
   cp /usr/portage/media-gfx/fontforge/fontforge-20110222.ebuild /usr/local/portage/media-gfx/fontforge/
   wget https://bugs.gentoo.org/attachment.cgi?id=273709 
   cp "attachment.cgi?id=273709" /usr/local/portage/media-gfx/fontforge/files/fontforge-20110222-zlib.so.patch

Open a text editor add one line to the fontforge-20110222.ebuild you just created in the local overlay:

  src_prepare() {
        epatch "${FILESDIR}/${P}-lxkbui.patch"
+      epatch "${FILESDIR}/${P}-zlib.so.patch"
        if use doc; then

Check your accept keywords for the eBuild, and:

   ebuild /usr/local/portage/media-gfx/fontforge/fontforge-20110222.ebuild manifest
   emerge -1 fontforge

Finally, report your success at bug 367425.

This permits you to test the ebuild for lilypond-2.14.1 at bug 370273. [4]

Stroller.




[1] https://bugs.gentoo.org/show_bug.cgi?id=4411
[2] https://bugs.gentoo.org/show_bug.cgi?id=290974
[3] https://bugs.gentoo.org/show_bug.cgi?id=367425
[4] https://bugs.gentoo.org/show_bug.cgi?id=370273

Re: [gentoo-user] zlib and WOFF

[luis jure]

on 2011-06-26 at 22:06 Stroller wrote:

>This isn't the best fix, IMO. 

i completely agree. by "solution" i meant a quick and dirty fix that
allowed me in the short term to build lilypond.

>IMO the correct fix for this is:

yes, i tried emerging fontforge with the patch you proposed and after that
lilypond compiled OK. thanks!!!


>Finally, report your success at bug 367425.

done.

thank you!

Re: [gentoo-user] zlib and WOFF

[Stroller]

On 27 June 2011, at 13:21, luis jure wrote:
> ...
> yes, i tried emerging fontforge with the patch you proposed and after that
> lilypond compiled OK. thanks!!!
> 
>> Finally, report your success at bug 367425.
> 
> done.

Thanks!

Did you try Lilypond 2.14.1?

If so it'd be great if you could report success at bug 370273.
https://bugs.gentoo.org/show_bug.cgi?id=370273

Stroller.

Re: [gentoo-user] zlib and WOFF

[luis jure]

on 2011-06-27 at 20:17 Stroller wrote:


> Did you try Lilypond 2.14.1?

yes, it worked perfectly all right.

reported success already.

great work, thank you!!