9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] some pcc questions
Date: Fri, 20 Apr 2012 18:01:33 +0200	[thread overview]
Message-ID: <CAK8RtFouE=21a0XZJmSK=QPqU3Xq7R69-w3WN+oAnQqPUUdWAA@mail.gmail.com> (raw)

Hi all

I have some problems that I sometimes run into while trying to port
stuff. One is that some files just "freezes" the compilation process
(but load goes down to 0 so it is not just labour intensive, but
rather that it just "sticks" there without doing anything) and when I
exit the compilation (by pressing "delete") I get different error
messages every time.

Is there a way to track down what is really happening in those cases
in order to solve them?


The second issue that I have been meaning to ask the list is about pcc
and bitfields - are they supported or is this some sort of can of
worms I have stepped into?

Here I have a more specific issue with compiling GNU m4: Compiling the
gnulib and all other files except src/builtin.c works fine with APE
libs and pcc, but builtin.c fails due to bitfields.
At the other side of the spectrum, a modern GNU m4 (including
src/builtin.c) can be compiled with the old GCC port, but there the
GCC-ported APE-libs are too old (vsnprintf etc not supported), so it
fails at the final linking phase since lots of stuff are not provided
by the C library.

Personally, I would prefer to crack that particular nut with pcc than
to go for an updated APE libs port to GCC so if there are specific
changes that can be done to bitfields in order to get it working, it
would be very interesting to hear about them...

some more details on why I even would bother doing such a thing:
http://code.google.com/p/ports2plan9/wiki/GNUonPlan9



             reply	other threads:[~2012-04-20 16:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20 16:01 Jens Staal [this message]
2012-04-20 16:24 ` cinap_lenrek
2012-04-20 16:29   ` cinap_lenrek
2012-04-20 17:31   ` Charles Forsyth
2012-04-23  6:30 ` Jens Staal
2012-04-23 13:23   ` Comeau At9Fans
2012-04-23 13:19 ` Comeau At9Fans
     [not found] ` <CAE9W7-gU72RNgbs6Pcuxp5KEtXBUsApZNGzNiEpvTgLtbL7wjw@mail.gmail.c>
2012-04-23 13:42   ` erik quanstrom
2012-04-23 14:37     ` Bakul Shah

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='CAK8RtFouE=21a0XZJmSK=QPqU3Xq7R69-w3WN+oAnQqPUUdWAA@mail.gmail.com' \
    --to=staal1978@gmail.com \
    --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).