From: Gaius Mulley <gaius@glam.ac.uk>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
deuling@de.ibm.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Unbounded array support implemented (for Modula-2)
Date: Wed, 01 Aug 2007 14:01:00 -0000 [thread overview]
Message-ID: <87bqdrweab.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <m3d4y85xma.fsf@codesourcery.com> (Jim Blandy's message of "Tue, 31 Jul 2007 09:47:09 -0700")
Jim Blandy <jimb@codesourcery.com> writes:
> I don't know how much work this is, but if there were some way you
> could get GNU Modula-2 into Fedora Core or Fedora Extras, I think that
> might increase your audience a bit. These days, if I can't install
> something by typing 'sudo yum install foo', I move on to something
> else.
yes true, I'm currently (when I'm near a fast machine) trying to build
GNU Modula-2 as a cross compiler for the avr as a Debian package.
Debian's package build mechanism is pretty awesome - but it eats dual
core, sata II machines for breakfast.. I've recently looked at the
Debian host GCC package - and I'm aiming to release gm2 grafted onto a
gcc-4.1.2. Although it will probably be a much simplified package
build as opposed to the GCC Debian package - just to reduce time to
market etc. I'm hoping Debian's 'alien' package should turn it into a
RPM successfully.
> (By the way, what's entailed in getting GNU Modula-2 into the main GCC
> sources?)
truthfully I'm not sure of the exact procedure to get it into the
main GCC trunk. However I know that I can place gm2 into the GCC svn
tree as a branch and then attempt to keep pack-porting the new patches
from the trunk to the gm2 branch. I suppose if enough people found it
useful and interesting maybe it would make it into the main truck..
Also I suspect that as patches get submitted to GCC for support for
various gm2 features (unbounded arrays, set types) this might provide
a little leverage to integrate the two.
regards,
Gaius
next prev parent reply other threads:[~2007-08-01 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 7:07 Gaius Mulley
2007-07-26 7:36 ` Markus Deuling
2007-07-27 12:26 ` Gaius Mulley
2007-07-27 20:22 ` Eli Zaretskii
2007-07-30 8:29 ` Gaius Mulley
2007-07-30 23:34 ` Jim Blandy
2007-07-31 3:01 ` Jim Blandy
2007-07-31 16:47 ` Gaius Mulley
2007-07-31 16:48 ` Jim Blandy
2007-08-01 14:01 ` Gaius Mulley [this message]
2007-07-31 19:18 ` Jim Blandy
2007-10-16 16:59 ` Gaius Mulley
2007-10-16 22:04 ` Jim Blandy
2007-07-26 22:58 ` Pierre Muller
2007-07-27 13:17 ` Gaius Mulley
2007-07-27 13:28 ` Pierre Muller
2007-07-28 0:59 ` Jim Blandy
2007-07-30 6:29 ` Gaius Mulley
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=87bqdrweab.fsf@j228-gm.comp.glam.ac.uk \
--to=gaius@glam.ac.uk \
--cc=deuling@de.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@codesourcery.com \
/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