Thread: [Cobolforgcc-devel] Old cobolforgcc Source

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Would it be of any value to the project (and plans) to use the
existing CVS head and try to get it to build with the current gcc
release?

-Tom

Tom Browder
Niceville, Florida
USA

Tom,

That would be extremely useful, but it would not be a job for the
faint-hearted. As an example, I can't get vanilla GCC to build on my PC
at the moment on my PC.

My intent is to start with "treelang" and add functionality to that. The
have kept treelang up to date while I have been away.

Regards,
Tim Josling

On Sun, 2007-12-30 at 15:38 -0600, Tom Browder wrote:
> Would it be of any value to the project (and plans) to use the
> existing CVS head and try to get it to build with the current gcc
> release?
> 
> -Tom
> 
> Tom Browder
> Niceville, Florida
> USA
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Cobolforgcc-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobolforgcc-devel

On Jan 9, 2008 1:21 AM, tim <te...@me...> wrote:
> Tom,
>
> That would be extremely useful, but it would not be a job for the
> faint-hearted. As an example, I can't get vanilla GCC to build on my PC

Well, that keeps life from being dull, right!  I'll see what happens.

Happy New Year!

-Tom

On Jan 9, 2008 1:21 AM, tim <te...@me...> wrote:
> Tom,
>
> That would be extremely useful, but it would not be a job for the
> faint-hearted. As an example, I can't get vanilla GCC to build on my PC
> at the moment on my PC.
>
> My intent is to start with "treelang" and add functionality to that. The
> have kept treelang up to date while I have been away.

Tim, I just noticed that you killed all the old cobol code on
sourceforge (and added the new lisp stuff), so does that mean I
shouldn't try to get the old to build with current gcc mainline?  I
can build the mainline treelang Ok (at least I could a few weeks ago).

BTW, the gcc I'm using for everything now (including Loki lib) is a
4.3 snapshot (4.3.0 20071109).  I've gotten it to build on some very
old hardware (running FC2) as well as newer stuff under Fedora 7.

-Tom

Tom,

It is still there in the repository. You can extract it using the cvs
tag "original-c-version".

Eg

cvs -z3
-d:pserver:ano...@co...:/cvsroot/cobolforgcc co  -r original-c-version  .

All on one line. Note the full stop at the end. I tested this so it
might work for you.

You can also browse it using cvs browse, under the COBOL directory.

By the way I am still making progress on the new version. The parser
generator using a special skeleton for bison to output lisp is working.
I am now working on the preprocessor (copy/replace verbs).

Regards,
Tim Josling

On Sat, 2008-01-12 at 06:04 -0600, Tom Browder wrote:
> On Jan 9, 2008 1:21 AM, tim <te...@me...> wrote:
> > Tom,
> >
> > That would be extremely useful, but it would not be a job for the
> > faint-hearted. As an example, I can't get vanilla GCC to build on my PC
> > at the moment on my PC.
> >
> > My intent is to start with "treelang" and add functionality to that. The
> > have kept treelang up to date while I have been away.
> 
> Tim, I just noticed that you killed all the old cobol code on
> sourceforge (and added the new lisp stuff), so does that mean I
> shouldn't try to get the old to build with current gcc mainline?  I
> can build the mainline treelang Ok (at least I could a few weeks ago).
> 
> BTW, the gcc I'm using for everything now (including Loki lib) is a
> 4.3 snapshot (4.3.0 20071109).  I've gotten it to build on some very
> old hardware (running FC2) as well as newer stuff under Fedora 7.
> 
> -Tom

On Jan 12, 2008 4:28 PM, tim <te...@me...> wrote:
...
> It is still there in the repository. You can extract it using the cvs
> tag "original-c-version".
...
> cvs -z3 -d:pserver:ano...@co...:/cvsroot/cobolforgcc co  -r original-c-version  .

Ok, that works so I'll use it to work on building
--enable-languages=c,cobol,treelang

-Tom

Tom,

Just one point to be aware of. If you are going to make a substantial
contribution (beyond a few lines of code) then we will need to arrange
a copyright assignment to the Free Software Foundation by yourself for
the work. 

This is so they can sue people who try to steal the code. 

That's normally not a problem, but they also require a disclaimer from
your employer or school or college. This is if you are employed or
studying.

Regards,
Tim Josling

On Mon, 2008-01-14 at 06:42 -0600, Tom Browder wrote:
> On Jan 12, 2008 4:28 PM, tim <te...@me...> wrote:
> ...
> > It is still there in the repository. You can extract it using the cvs
> > tag "original-c-version".
> ...
> > cvs -z3 -d:pserver:ano...@co...:/cvsroot/cobolforgcc co  -r original-c-version  .
> 
> Ok, that works so I'll use it to work on building
> --enable-languages=c,cobol,treelang
> 
> -Tom

Tom,

I should have said: It would be great to get the old version running on
the current GCC code... at the right tim we can create a branch in cvs
and give you commit access to the repository.

ActuallY I am using git for tracking my developments. If you are up to
speed with git, which is a very powerful tool, I can send you my git
repository. I need to find somewhere that hosts git developments I
think.

Regards,
Tim Josling

On Tue, 2008-01-15 at 07:15 +1100, tim wrote:
> Tom,
> 
> Just one point to be aware of. If you are going to make a substantial
> contribution (beyond a few lines of code) then we will need to arrange
> a copyright assignment to the Free Software Foundation by yourself for
> the work. 
> 
> This is so they can sue people who try to steal the code. 
> 
> That's normally not a problem, but they also require a disclaimer from
> your employer or school or college. This is if you are employed or
> studying.
> 
> Regards,
> Tim Josling
> 
> On Mon, 2008-01-14 at 06:42 -0600, Tom Browder wrote:
> > On Jan 12, 2008 4:28 PM, tim <te...@me...> wrote:
> > ...
> > > It is still there in the repository. You can extract it using the cvs
> > > tag "original-c-version".
> > ...
> > > cvs -z3 -d:pserver:ano...@co...:/cvsroot/cobolforgcc co  -r original-c-version  .
> > 
> > Ok, that works so I'll use it to work on building
> > --enable-languages=c,cobol,treelang
> > 
> > -Tom
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Cobolforgcc-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobolforgcc-devel

On Jan 14, 2008 2:25 PM, tim <te...@me...> wrote:
> Tom,
>
> I should have said: It would be great to get the old version running on
> the current GCC code... at the right tim we can create a branch in cvs

OK, Tim, I've started doing that--I put the old code into the gcc
mainline tree and am trying to build it.

...
> ActuallY I am using git for tracking my developments. If you are up to
> speed with git, which is a very powerful tool, I can send you my git

Hm, I started looking at git during its initial days when it was
announced that Linus and gcc crew were renouncing BitKeeper, but I
didn't follow up seriously.  I'm looking at bazaar at the moment, but
I think git is fairly easy to use for basic stuff.

I'll keep chugging with the old code and send patches if I'm
successful.  I can get your current stuff later.

I'm sure I have a release on file with FSF (with my legal name: Thomas
M. Browder, Jr.), but I'm not sure I have one for my company.  Is
there a specific form (I hunted around gcc.org but couldn't find one)?

-Tom