Hi Alain,
I guess you are hit by well known issue in GCC's CPP on Solaris. Just
verify here:
https://gcc.gnu.org/ml/gcc/2014-08/msg00114.html
solution in this case is simple: use configure option to set different
non buggy CPP as a CPP for GHC.
Please let me know if this is the culprit,
Thanks,
Karel
On 12/31/15 08:09 AM, Alain O'Dea wrote:
On SmartOS GHC flag warnings show up like this:
/tmp/ghc72341_0/ghc_1.hscpp:7:16: Warning:
-fffi is deprecated: use -XForeignFunctionInterface or pragma {-#
LANGUAGE ForeignFunctionInterface #-} instead
It appears that this line in DriverPipeline leads to the correct
filename in warnings on Ubuntu, but not on SmartOS:
src_opts <- liftIO $ getOptionsFromFile dflags0 output_fn
https://github.com/ghc/ghc/blob/bb7f2e33197e667eb694bd1243f125c722a0a868/compiler/main/DriverPipeline.hs#L865
How does the intermediate hscpp filename get restored to a correct
filename if warnings are generated during a re-read of the pragmas after
having preprocessed the file?
Full investigation notes are here (rambling and unedited):
https://gist.github.com/AlainODea/98141991849093285c52
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
