From: Ariel Rios <ariel@gnu.org>
Subject: Error building guile on the ipaq
Date: 10 Apr 2003 14:56:58 -0500 [thread overview]
Message-ID: <1050004618.18388.26.camel@tosca.elektra.com.mx> (raw)
I';ve tryed to compile guile for the ipaq and I got the following error:
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I./.. -I../libguile-ltdl -g -O2
-Wall -Wmissing-prototypes -c gc_os_dep.c -Wp,-MD,.deps/gc_os_dep.TPlo
-fPIC -DPIC -o .libs/gc_os_dep.lo
gc_os_dep.c:365: parse error before `--'
make: *** [gc_os_dep.lo] Error 1
I tryed to add the armv41 definition like this with no luck:
#if defined(LINUX) && defined(armv41)
# define ARM32
# define mach_type_known
# endif
Any help? Running uname gives me:
guest@skiffcluster2:~/ariel@gnu.org/guile-1.6.3/libguile$ uname -a
Linux skiffcluster2.handhelds.org 2.4.0-test1-ac7-rmk1-crl2 #15 Fri Jun
16 11:24:53 EDT 2000 armv4l unknown
ariel
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-04-10 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 19:56 Ariel Rios [this message]
2003-04-10 22:48 ` Error building guile on the ipaq Marius Vollmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1050004618.18388.26.camel@tosca.elektra.com.mx \
--to=ariel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).