9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] Go on Plan9/Arm
Date: Fri, 19 Oct 2012 20:45:59 +0200	[thread overview]
Message-ID: <17b30d8d59e8737bf9eb9bd36f897ea8@proxima.alt.za> (raw)

Now that the sheevaplug is running again, I thought I'd try compiling
Go on it, see how far I'd get.

It seems not very far at all and I'm sure I'm just not seeing the wood
for the trees.  Compilation stops when int32 isn't defined:

bangle% ./make.rc
# Building C bootstrap tool.
cmd/dist

# Building compilers and Go bootstrap tool for host, plan9/arm.
lib9
libbio
libmach
/usr/lucio/Project/go/include/plan9/../mach.h:37 /usr/lucio/Project/go/include/plan9/mach.h:5 /usr/lucio/Project/go/src/libmach/5obj.c:35 syntax error, last name: int32
go tool dist: FAILED: /bin/5c -FTVw -I/usr/lucio/Project/go/include/plan9 -I/usr/lucio/Project/go/include/plan9/arm -I /usr/lucio/Project/go/src/libmach -o $WORK/5obj.5 /usr/lucio/Project/go/src/libmach/5obj.c: '/usr/lucio/Project/go/pkg/obj/plan9_arm/libmach.a' does not exist
/usr/lucio/Project/go/include/plan9/../mach.h:37 /usr/lucio/Project/go/include/plan9/mach.h:5 /usr/lucio/Project/go/src/libmach/5.c:36 syntax error, last name: int32
/usr/lucio/Project/go/include/plan9/../mach.h:37 /usr/lucio/Project/go/include/plan9/mach.h:5 /usr/lucio/Project/go/src/libmach/5db.c:33 syntax error, last name: int32
go tool dist: FAILED: /bin/5c -FTVw -I/usr/lucio/Project/go/include/plan9 -I/usr/lucio/Project/go/include/plan9/arm -I /usr/lucio/Project/go/src/libmach -o $WORK/5.5 /usr/lucio/Project/go/src/libmach/5.c: '/usr/lucio/Project/go/pkg/obj/plan9_arm/libmach.a' does not exist
/usr/lucio/Project/go/include/plan9/../mach.h:37 /usr/lucio/Project/go/include/plan9/mach.h:5 /usr/lucio/Project/go/src/libmach/6.c:36 syntax error, last name: int32
go tool dist: FAILED: /bin/5c -FTVw -I/usr/lucio/Project/go/include/plan9 -I/usr/lucio/Project/go/include/plan9/arm -I /usr/lucio/Project/go/src/libmach -o $WORK/5db.5 /usr/lucio/Project/go/src/libmach/5db.c: '/usr/lucio/Project/go/pkg/obj/plan9_arm/libmach.a' does not exist
go tool dist: FAILED: /bin/5c -FTVw -I/usr/lucio/Project/go/include/plan9 -I/usr/lucio/Project/go/include/plan9/arm -I /usr/lucio/Project/go/src/libmach -o $WORK/6.5 /usr/lucio/Project/go/src/libmach/6.c: '/usr/lucio/Project/go/pkg/obj/plan9_arm/libmach.a' does not exist

What I don't understand is where the 386 compilation finds the int32
definition missing in arm.  I looked in the obvious places and my guess
is that the "go" tool does not use the same rules to search for header
files.  No doubt I'm wrong :-|

Any ideas?  It's latish here and my thought processes have slowed
down...

++L




             reply	other threads:[~2012-10-19 18:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 18:45 lucio [this message]
2012-10-19 19:46 ` Charles Forsyth
2012-10-20  4:34   ` lucio
2012-10-20  6:52   ` lucio
2013-03-21 16:54     ` Jeremy Jackins
2013-03-21 17:23       ` Francisco J Ballesteros
2013-03-21 17:29         ` Francisco J Ballesteros
2013-03-21 18:24           ` Jeremy Jackins
2013-03-21 17:23       ` lucio

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17b30d8d59e8737bf9eb9bd36f897ea8@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).