From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: [LARTC] tcng version 9d
Date: Tue, 14 Jan 2003 15:57:17 +0000 [thread overview]
Message-ID: <marc-lartc-104255991216416@msgid-missing> (raw)
... is on SourceForge:
http://tcng.sourceforge.net/dist/tcng-9d.tar.gz
md5sum 0f61201c657f1851d9d12ca897a4985e
(See also http://tcng.sourceforge.net/)
This is a maintenance release that fixes various compatibility
problems. It also recognizes more recent kernels.
The complete list of changes is below.
- Werner
----------------------------------- CHANGES -----------------------------------
Version 9d (14-JAN-2003)
------------------------
- updated kernel version example in tcng/README from 2.4.19 to 2.4.20
- configure is now compatible with 2.4.21 (pre-release, tested with pre3)
- tcsim -V now also prints the versions of the kernel and iproute2 used to
build it
- make "upload-sf" now runs md5sum after uploading
- README: changed tar xfI <file> to more compatible bzcat <file> | tar xf -
- generalized argument-fetching mechanism of sprintf, and split it into
sprintf.c and sprintf_generic.c
- removed extra % from sprintf's precision error message (updated
tests/sprintf)
- comtc's second pass now invokes tcc with the -n option, because some versions
of CPP don't allow -include with -fpreprocessed
- toys/comtc mis-converted stdin location tags when using cpp 2.96 (reported by
Martin A. Brown)
- tcsim executed original rtnl_close, closing an undefined file descriptor,
which sometimes upset flex, causing it to fail with "input in flex scanner
failed" (reported by "bauer")
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-01-14 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-104255991216416@msgid-missing \
--to=wa@almesberger.net \
--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