All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nuutti Kotivuori <naked@iki.fi>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: tcng version 9l
Date: Sun, 29 Feb 2004 21:18:19 +0000	[thread overview]
Message-ID: <87k72537qc.fsf@iki.fi> (raw)

Werner Almesberger wrote:
> Since I cleaned up so many things for Gentoo yesterday, here's one
> for Debian 3.0. The main problems were:

I still have one more problem with latest Debian unstable. This is the
failure message I am getting:

cc -g -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -I../shared -Iklib -Iklib/include -Iulib/iproute2/include -I. -DVERSION=\"`cat ../VERSION`\" -DTOPDIR=\"/home/naked/src/tcng/tcng\"  -DTCC_CMD=\"/home/naked/src/tcng/tcng/bin/tcc\" -DKFULLVERSION=\"2.4.25\" -DKFULLVERSIONNUM=`printf "0x%02x%02x%02x" 2 4 25` -DIVERSION=\"010824\"   -c -o tcsim.o tcsim.c
In file included from /usr/include/bits/sigcontext.h:28,
                 from /usr/include/signal.h:326,
                 from tcsim.c:15:
/usr/include/asm/sigcontext.h:79: error: parse error before '*' token
/usr/include/asm/sigcontext.h:82: error: parse error before '}' token

Which is caused by having klib/include in the include path, and it
overriding what linux/compiler.h is. If I add:

#define __user
#define __kernel

to tcsim/klib/include/linux/compiler.h, everything works perfectly and
tests pass (Passed all 1534 tests (24 conditional tests skipped)).

-- Naked

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-02-29 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 21:18 Nuutti Kotivuori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-09 15:02 [LARTC] Re: tcng version 9l Werner Almesberger

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=87k72537qc.fsf@iki.fi \
    --to=naked@iki.fi \
    --cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.