mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Announce: modutils 2.4.22 is available
Date: Mon, 25 Nov 2002 15:39:38 +1100	[thread overview]
Message-ID: <6714.1038199178@kao2.melbourne.sgi.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/modutils/v2.4

modutils-2.4.22.tar.gz          Source tarball, includes RPM spec file
modutils-2.4.22-1.src.rpm       As above, in SRPM format
modutils-2.4.22-1.i386.rpm      Compiled with gcc 2.96 20000731,
                                glibc 2.2.2.
modutils-2.4.22-1.ia64.rpm	Compiled with gcc 2.96-ia64-20000731,
				glibc-2.2.3.
modutils-2.4.22-1.sparc.rpm	Compiled for combined 32/64 sparc, with gcc
				2.95.4, glibc-2.2.5.
patch-modutils-2.4.22.gz        Patch from modutils 2.4.21 to 2.4.22.

Changelog extract

	* Avoid unaligned traps on alpha.  Ivan Kokshaysky.
	* Handle R_PPC64_NONE relocs, remove warnings.  Alan Modra.
	* Add DESTDIR to build (from SuSe).
	* Check for special characters in module name (from SuSe).
	* Check x86_64 for -mcmodel=kernel (from SuSe).
	* Add alias for osst (from SuSe).
	* Check for illegal mixture of gcc 2 and 3 (from RedHat).
	* Build libmodutils.a (from RedHat).
	* Selectively add aliases, above, below, prune entries (from Mandrake).
	* Add MODUTILS_MACROS (from Mandrake).
	* Remove more warnings.
	* Add Kerntypes to prune list.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999

iD8DBQE94amIi4UHNye0ZOoRAm03AJ0ZSirkpfWwpNO0bQnfs9kn2osEIgCcCh4w
sT7Y8Qc4EE7/cXAf9ult4VE=
=kpEp
-----END PGP SIGNATURE-----


                 reply	other threads:[~2002-11-25  4:32 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=6714.1038199178@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®