lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GUB and mipsel architecture


From: Federico Bruni
Subject: GUB and mipsel architecture
Date: Mon, 17 May 2010 08:45:37 +0200

Some months ago I asked if anybody managed to compile LilyPond in a
computer which has a MIPS architecture:
http://lists.gnu.org/archive/html/lilypond-user/2009-12/msg00127.html 

In the meanwhile I bought a MIPSel netbook (Lemote Yeeloong) and
successfully compiled lilypond in gNewSense 3 (based on Debian stable).

I'm wondering if it is worth having a mipsel package on lilypond.org
(when 2.14 comes out, maybe).
I'd be happy to do it, if I can. A chance to help and learn something
new.

Here's what I've done:

git clone git://github.com/janneke/gub.git
cd gub
bin/gub lilypond-installer

But I have a problem with librestrict (attached librestrict.log):

#########################################################################

Tail of target/tools/log/librestrict.log >>>>>>>>
    ./xstatconv.c:224: error: 'struct stat' has no member named '__pad2'
    ./xstatconv.c:266: error: 'struct stat' has no member named
'__unused4'
    ./xstatconv.c:269: error: 'struct stat' has no member named
'__unused5'
    Command barfed:
cd /home/fede/src/gub/target/tools/build/librestrict-1.9.a && gcc -W
-Wall -fno-stack-protector -I. -fPIC -shared -o librestrict-stat.so
restrict-stat.c || gcc -W -Wall  -I. -fPIC -shared -o
librestrict-stat.so restrict-stat.c
<<<<<<<< Tail of target/tools/log/librestrict.log

*** Failed target: tools::librestrict

##########################################################################

Just in case, I attach also target/tools/build/librestrict-1.9.a/xstatconv.c

How can I fix it?

Thanks,
Federico


PS (a report on a different subject)
I've read that you have changed the ./configure in 2.13.21
In previous versions, when I run ./autogen.sh, ./configure failed to recognise 
my architecture,
even though some information were printed on terminal (can't remember)
and especially: `uname -m mips64`
Since this version I don't have this warning.
Maybe next time I can try removing the --build=mips64 option and see what 
happen.

Attachment: librestrict.log
Description: Text Data

Attachment: xstatconv.c
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]