Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Compiler and linker flags ignored when building probe runner #104
While updating the Debian package for FFI-Platypus, I noticed that probe/bin/dlrun gets built without the compiler/linker flags we set for package builds in the environment.
I now came up with a patch which collects the *FLAGS and uses them in lib/FFI/Probe/Runner/Builder.pm. Not sure if this is the best/correct method but it seems to work.
Alas no pull request as this is against 0.74 and doesn't apply cleanly against git HEAD. - The patch is here:
Hrm. I may need some help in understanding how this problem manifests itself. MakeMaker does not typically respond to those environment variables, (at least not directly, I think
Yeah, it's all a bit complicated :) EUMM can be fed these variables, e.g. when building FFI-Platypus I get
where parts are inserted by our build machinery (debhelper's perl_makemaker build system) from the environment. The environment looks something like
The values from
EUMM writes all kinds of things from %Config and from the invocation with OPTIMIZE and LD to the Makefile, and the actual compile and linking steps of the library look like
I don't know if there is a way to trick EUMM into writing a Makefile that builds "external" stuff like the probe runner in the same way as its "own" stuff, that's why I fiddled around with %ENV directly; maybe there are better ways …
This looks very good, thank you! I see, with V=1, all flags in the cc calls.
There are just two minor (new) issues left: One is, to quote lintian (our package checker):
And indeed, the generated probe.pl contains:
The other point is
for 0.74 I've changed this to
Now the docs claim to use
Ok, just a doc update then :)
The stuff in the
Fixed the doco here: 4d0416a, sorry for change, I think