From: Scott Mansfield <thephantom@mac.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Compiling TCNG (tcsim)
Date: Sun, 16 Nov 2003 05:18:45 +0000 [thread overview]
Message-ID: <marc-lartc-106896023028510@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106894240419206@msgid-missing>
Hello Nelson,
It looks like you grabbed and unpacked the kernel sources but didn't do
a 'make config' (or 'make xconfig'). IIRC you need to do this at least
once in a new kernel source tree because these programs create the asm
symlink and some extra config headers in include/config and
include/linux/modules.
Also, make sure /usr/include/linux and /usr/include/asm point to your
correct kernel source tree.
Cheers,
Scott
On Nov 15, 2003, at 4:18 PM, Nelson E. Castillo wrote:
> Hi,
>
> I really would like to use tcng.
> (it seems it's the right place to ask...)
>
> I try to build it like this:
>
> $ cd tcsim
> $ wget ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2.4.22.tar.bz2
> $ bzcat linux-2.4.22.tar.bz2 | tar xf -
>
> $ ln -s linux-2.4.22 linux
>
> $ wget
> ftp://ftp.inr.ac.ru/ip-routing/iproute2-2.4.7-now-ss010824.tar.gz
> $ tar xfz iproute2-2.4.7-now-ss010824.tar.gz
> $ cd ..
> $ ./configure
>
> Reading configuration defaults from ./config
> building tcsim: yes
> Kernel source: /home/admin/tcng/tcsim/linux
> Kernel version: 2.4.22
> iproute2 source: /home/admin/tcng/tcsim/iproute2
> iproute2 version: 010824
> Host byte order: little endian
> tcc command: /home/admin/tcng/bin/tcc
> building the manual: NO
> install directory: /usr/local
>
> $ make
>
> (snip)
>
> make -f Makefile.unclean tcsim
> make[2]: Entering directory `/home/admin/tcng/tcsim'
> cc -g -Wall -Wstrict-prototypes -Wmissing-prototypes
> -Wmissing-declarations -I../shared -Iklib -Iklib/include
> -Iulib/iproute2/include -I. -DVERSION=\"`cat ../VERSION`\"
> -DTOPDIR=\"/home/admin/tcng\" -DTCC_CMD=\"/home/admin/tcng/bin/tcc\"
> -DKFULLVERSION=\"2.4.22\" -DKFULLVERSIONNUM=`printf "0x%02x%02x%02x" 2
> 4 22` -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:14:
> /usr/include/asm/sigcontext.h:79: error: parse error before '*' token
> /usr/include/asm/sigcontext.h:82: error: parse error before '}' token
> make[2]: *** [tcsim.o] Error 1
> make[2]: Leaving directory `/home/admin/tcng/tcsim'
> make[1]: *** [tcsim] Error 2
> make[1]: Leaving directory `/home/admin/tcng/tcsim'
> make: *** [all] Error 1
>
> Any clue?
>
> I'm including a detailed report with the versions of the packages.
>
> I updated my system.... Now I run Debian unstable.
> What system is tcng being developed on?
>
> Thanks,
> Nelson.-
>
> --
> http://geocities.com/arhuaco
>
> The first principle is that you must not fool yourself
> and you are the easiest person to fool.
> -- Richard Feynman.
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-11-16 5:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 0:18 [LARTC] Compiling TCNG (tcsim) Nelson E. Castillo
2003-11-16 5:18 ` Scott Mansfield [this message]
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=marc-lartc-106896023028510@msgid-missing \
--to=thephantom@mac.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox