9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: comeau@panix.com (Greg Comeau)
To: 9fans@9fans.net
Subject: Re: [9fans] porting help please
Date: Wed,  9 Sep 2009 08:36:13 +0000	[thread overview]
Message-ID: <h862ka$n2c$1@panix1.panix.com> (raw)
In-Reply-To: <1d5d51400909080844q1bee4c3s114ccc5e51ce52f5@mail.gmail.com>

In article <1d5d51400909080844q1bee4c3s114ccc5e51ce52f5@mail.gmail.com>,
Fernan Bolando <fernanbolando@mailc.net> wrote:
>...error: initializer is not a constant: F0_Prelude_46primLeave
>--h file ---
>#define VAP_TAG  1
>#define WORDSHIFT  5
>#define WORDSIZE   (1<<WORDSHIFT)
>#define WORDMASK   (WORDSIZE-1)
>#define NS         (WORDSIZE>>3)
>#define ZAP_BIT    (1L<<(WORDSIZE-1))
>-- c file ----
>unsigned F0_Prelude_46primLeave[] = {
>  CAPTAG(FN_Prelude_46primLeave,1)
>#ifdef PROFILE
>, useLabel(PROF_primLeave)
>, 0
>, 0
>, 0
>#endif

The initializers to some things need to be constants.
In your case, it appears that either CAPTAG or useLabel (or both)
have ended up not being #define'd.  Probably the header they are
#define'd in is not being #include'd (you don't show it above,
but then you don't show enough of your code to even reproduce it).

On a relate note, you can see the results of preprocessing
from pcc by using the -E and/or -P options, that way you
can see whether the macro ended up getting substituted
and what it was substituted to -- or not in your case.
Some compilers also have options which will emit the trail of
files #include'd but I don't see that option for pcc.
--
Greg Comeau / 4.3.10.1 with C++0xisms now in beta!
Comeau C/C++ ONLINE ==>     http://www.comeaucomputing.com/tryitout
World Class Compilers:  Breathtaking C++, Amazing C99, Fabulous C90.
Comeau C/C++ with Dinkumware's Libraries... Have you tried it?



  reply	other threads:[~2009-09-09  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 15:44 Fernan Bolando
2009-09-09  8:36 ` Greg Comeau [this message]
2009-09-09  8:36 ` Greg Comeau

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='h862ka$n2c$1@panix1.panix.com' \
    --to=comeau@panix.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).