Re: [preliminary PATCH] Parrot C Compiler Wrapper

2002-04-01 Thread Nicholas Clark
On Sat, Mar 30, 2002 at 04:37:54PM -0800, Brent Dax wrote: Nicholas Clark: # Patching file Makefile.in using Plan A... # Hunk #1 succeeded at 112. # Hunk #2 failed at 143. Weird. Line endings, perhaps. This line has appeared in Makefile.in, which doesn't seem to be in your patch: # XXX

[preliminary PATCH] Parrot C Compiler Wrapper

2002-03-30 Thread Brent Dax
This patch adds a new utility to Parrot and modifies Makefile.in to use it. The utility is for wrapping C compilers and other tools we use, so we can avoid putting the logic in the Makefile and can potentially use totally different commands on different platforms. The patch is by no means ready

Re: [preliminary PATCH] Parrot C Compiler Wrapper

2002-03-30 Thread Josh Wilmes
I've been thinking along these lines, but I'd decided on a different approach. I think that it's better to keep the magic to a minimum. Rather than relying on extensions, I was thinking about having a different wrapper for each task: - lib.pl: build static library from object files

Re: [preliminary PATCH] Parrot C Compiler Wrapper

2002-03-30 Thread Nicholas Clark
On Sat, Mar 30, 2002 at 02:12:46AM -0800, Brent Dax wrote: If you have a Unix box and ten spare minutes, please apply this to a fresh checkout of Parrot, run 'make test', and tell me how well it works. FreeBSD did not enjoy it: 0 Patch did not apply cleanly: Patching file Makefile.in using

RE: [preliminary PATCH] Parrot C Compiler Wrapper

2002-03-30 Thread Brent Dax
Nicholas Clark: # On Sat, Mar 30, 2002 at 02:12:46AM -0800, Brent Dax wrote: # # If you have a Unix box and ten spare minutes, please apply this to a # fresh checkout of Parrot, run 'make test', and tell me how well it # works. # # FreeBSD did not enjoy it: # # 0 Patch did not apply cleanly: #