On Tue, Aug 9, 2011 at 4:36 AM, Ian Lynagh wrote:
> On Mon, Aug 08, 2011 at 06:44:29PM -0700, Evan Laforge wrote:
>>
>> So... remove it all?
>
> I've done so.
Yay, thanks!
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://
On Mon, Aug 08, 2011 at 06:44:29PM -0700, Evan Laforge wrote:
>
> So... remove it all?
I've done so.
Thanks
Ian
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
On 09/08/2011 02:44, Evan Laforge wrote:
So the simplest thing to do is remove all the version stuff. That
means that if you want to run hsc2hs with a version of ghc which is
not the one linked in /usr/bin, you also can't run the hsc2hs linked
in /usr/bin, but have to get the one out of the ghc
>> Should I try to send a patch for the remove all backward compatibility
>> thing? Or one for the specific #include problem I've been having?
>
> I've lost track of all the details here. But perhaps there's some
> historical cruft lying around because hsc2hs used to call GHC to compile its
> C f
On 07/08/2011 02:18, Evan Laforge wrote:
On Sat, Jul 30, 2011 at 9:25 PM, Ian Lynagh wrote:
But I also think we may as well just remove most of these conditionals.
The GHC< 4.09 tests can surely be removed, and likewise the GHC< 6.3
tests. Personally I'd remove the GHC< 6.10 test too, but pe
> On Sat, Jul 30, 2011 at 9:25 PM, Ian Lynagh wrote:
>> But I also think we may as well just remove most of these conditionals.
>> The GHC < 4.09 tests can surely be removed, and likewise the GHC < 6.3
>> tests. Personally I'd remove the GHC < 6.10 test too, but perhaps that
>> will be more conten
On Sat, Jul 30, 2011 at 9:23 PM, Edward Z. Yang wrote:
> No, I don't think this diagnosis is correct. hsc2hs is outputting
> preprocessor
> directives into hs files that GHC will then process. Inspect your .hs file,
Not for me it's not, it's putting preprocessor directives into a C
file that t
On Sat, Jul 30, 2011 at 09:10:21PM +, Evan Laforge wrote:
> On Sat, Jul 30, 2011 at 8:32 PM, Edward Z. Yang wrote:
> > This is supposed to get defined as a command line argument to the
> > preprocessor,
> > see compiler/main/DriverPipeline.hs. Are you saying you don't see it when
> > you
>
No, I don't think this diagnosis is correct. hsc2hs is outputting preprocessor
directives into hs files that GHC will then process. Inspect your .hs file,
at least for me, I don't see #INCLUDE pragmas output at all, with latest
hsc2hs (old versions just didn't output any ifdefs, so we'd hit the p
On Sat, Jul 30, 2011 at 8:32 PM, Edward Z. Yang wrote:
> This is supposed to get defined as a command line argument to the
> preprocessor,
> see compiler/main/DriverPipeline.hs. Are you saying you don't see it when you
> run hsc2hs? Maybe someone else is calling a preprocessor but missing some o
This is supposed to get defined as a command line argument to the preprocessor,
see compiler/main/DriverPipeline.hs. Are you saying you don't see it when you
run hsc2hs? Maybe someone else is calling a preprocessor but missing some of
these arguments...
Edward
___
So when I upgrade from 6.10 to 6.12 a LONG time ago, there was a bug
where hsc2hs would emit INCLUDE pragmas and ghc didn't like that. So
I hacked around it with an extra grep -v step in the Makefile. I
always meant to go fix it for real in hsc2hs and finally I came back
to that TODO item. I too
12 matches
Mail list logo
