From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: [LARTC] tcng version 9h
Date: Fri, 07 Nov 2003 03:20:47 +0000 [thread overview]
Message-ID: <marc-lartc-106817537112349@msgid-missing> (raw)
... is on SourceForge:
http://tcng.sourceforge.net/dist/tcng-9h.tar.gz
md5sum 9b7c520f92b312a5a00da12bad35f57d
See also http://tcng.sourceforge.net/
This release upgrades to the current 2.4 kernels, fixes a few minor
glitches in the build system, and adds the options --no-manual and
--with-manual to configure, so that tcng can be build without the
documentation (also, configure uses --no-manual if it can't find
latex or dvips).
The complete list of changes is below.
- Werner
----------------------------------- CHANGES -----------------------------------
Version 9h (7-NOV-2003)
-----------------------
- tcc/ext/Makefile: dependencies now only include .c files compiled in that
directory, removing a warning when building RPMs
- split tcsim/Makefile into Makefile.unclean and Makefile.clean to avoid
rebuilding klib and ulib when cleaning up after configuration changes
- configure is compatible with 2.4.22 and 2.4.23 (pre-release, tested with
2.4.23-pre9)
- setup.klib generates linux/smp.h needed for 2.4.22
- tcsim/trace.c and tcsim/modules/sch_discard.c adjust ..._drop prototype for
interface change in 2.4.22
- setup.klib clears LANG before using sed on [^ -~]
- setup.klib adds "err" and "error_report" members to "struct sock" in
af_netlink.c (for 2.4.23)
- updated kernel version example in tcng/README from 2.4.21 to 2.4.22
- configure: added options --no-manual and --with-manual (abbreviations -m and
-M) to allow building tcng with or without the documentation (suggested by
"raptor")
- configure: automatically assumes --no-manual if either latex or dvips is not
in the PATH
--
_________________________________________________________________________
/ 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/
next reply other threads:[~2003-11-07 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 3:20 Werner Almesberger [this message]
2003-11-10 7:36 ` [LARTC] tcng version 9h Nelson E. Castillo
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-106817537112349@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