From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Announce: modutils 2.4.26 is available
Date: Thu, 30 Oct 2003 23:35:34 +1100 [thread overview]
Message-ID: <5608.1067517334@ocs3.intra.ocs.com.au> (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.26.tar.gz Source tarball, includes RPM spec file
modutils-2.4.26-1.src.rpm As above, in SRPM format
modutils-2.4.26-1.i386.rpm Compiled with gcc 2.96 20000731,
glibc 2.2.2.
modutils-2.4.26-1.ia64.rpm Compiled with gcc 2.96-ia64-20000731,
glibc-2.2.3.
patch-modutils-2.4.26.gz Patch from modutils 2.4.25 to 2.4.26.
Changelog extract
* Ignore SHT_MIPS_DWARF sections. Alvaro Martinez Echevarria.
* Add -malign-double to cflags for 64 bit builds.
* Fix zlib linking problems. Maciej W. Rozycki.
* Remove hard coded limits on length of modules.conf lines.
* Alias updates. Red Hat.
* Makefile fix for parallel build using bison. Andreas Haumer.
* Document difference between patterns and modules in modprobe.
Frank Murphy.
* Suppress module not found message on modprobe -q. Frank Murphy.
* Add module name to some messages. Red Hat.
* Add amd64 support. i386 now defaults to combined 32/64 bit.
Arnd Bergmann.
* Older glibc versions had a wrong name for R_390_GOTOFF32.
Arnd Bergmann.
* Run known directories in the correct historical order. Red Hat.
* Upgrade config.sub, config.guess to glibc 2.3.2.
* Add sh64 support. Benedict Gaster.
* Only build sys_oim.o when COMPAT_2_0 is set, it breaks with ia64 and
recent glibc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE/oQWWi4UHNye0ZOoRAlDuAKCOxVla9fBCgjRe+hPuEMAnovkRdgCfW2QM
VFTy2ByssHs8KpTUC+cKASA=
=9yWv
-----END PGP SIGNATURE-----
reply other threads:[~2003-10-30 12:36 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=5608.1067517334@ocs3.intra.ocs.com.au \
--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®