From: Konstantin Boldyshev <konst@linuxassembly.org>
To: "linux-assembly@vger.kernel.org" <linux-assembly@vger.kernel.org>
Subject: new asmutils are on the way
Date: Wed, 08 Feb 2006 09:26:29 +0300 [thread overview]
Message-ID: <43E98F15.8090808@linuxassembly.org> (raw)
In-Reply-To: <42CD8095.8000109@linuxassembly.org>
Hello everyone!
Now that everybody thinks they are dead, here they are... :)
asmutils are switching to the latest nasm (0.98.39 afaik) and will (try to)
use its features, so that version will be required to compile the project.
If there are any contributions, please send them asap (I hope
to release new version during next weekend), but first check
http://linuxassembly.org/asmutils/ChangeLog
--
Regards,
Konstantin.
next prev parent reply other threads:[~2006-02-08 6:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200506292204.j5TM4mLj024638@zeus2.kernel.org>
2005-06-29 23:37 ` TT6: High-quality custom logos and business identities Richard Cooper
2005-06-30 1:13 ` James Colannino
2005-07-01 22:31 ` Steffen Solyga
2005-07-01 22:33 ` Hendrik Visage
2005-07-02 5:28 ` Frank Kotler
2005-07-03 6:15 ` Daniel Bonekeeper
2005-07-08 5:28 ` Richard Cooper
2005-07-04 16:30 ` Does anyone still read this list? Agner Fog
2005-07-03 17:17 ` TT6: High-quality custom logos and business identities jko
2005-06-30 3:09 ` Herbert Poetzl
2005-07-06 11:57 ` Konstantin Boldyshev
2005-07-06 20:03 ` linuxassembly.org - asmutils Frank Kotler
2005-07-07 19:20 ` Konstantin Boldyshev
2006-02-08 6:26 ` Konstantin Boldyshev [this message]
2006-02-08 12:57 ` new asmutils are on the way Frank Kotler
2006-02-08 22:22 ` Konstantin Boldyshev
2006-02-11 0:51 ` Frank Kotler
2006-02-13 16:40 ` Konstantin Boldyshev
2006-02-21 15:41 ` asmutils 0.18 released Konstantin Boldyshev
2006-02-21 16:00 ` Jan Wagemakers
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=43E98F15.8090808@linuxassembly.org \
--to=konst@linuxassembly.org \
--cc=linux-assembly@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;
as well as URLs for NNTP newsgroup(s).