[Pkg-osg-devel] Bug: #690878 "pkg-config reports wrong path"
Alberto Luaces
aluaces at udc.es
Mon Nov 19 19:32:57 UTC 2012
"Manuel A. Fernandez Montecelo" writes:
[...]
Thanks a lot for the pointers. Indeed, I tested my patch and it worked,
but as I said, I felt it was too much hacky. I knew that a fresh look
at the rules would reveal a much cleaner approach. I had completely
forgotten about the target installation directory through DESTDIR.
(continues)
>
>
>>> On the other hand, lintian throws a lot of
>>>
>>> W: openscenegraph: hardening-no-fortify-functions
>>>
>>> Since I am not fresh in this one, I can't remember if I set correctly
>>> the hardening flags or if this is allowable. Any ideas?
>
[...]
> I think that these are not needed for dh v9, but we will need them
> with previous levels/versions:
> +DPKG_EXPORT_BUILDFLAGS = 1
> +include /usr/share/dpkg/buildflags.mk
>
> Also, take a look at the debian/rules that I posted in the previous
> mail, specially the one for aqsis because of the quirk of CMake not
> using CPP flags (and thus missing "-D_FORTIFY_SOURCE=2" and other
> stuff, if not injected by us in CFLAGS and CXXFLAGS).
>
> And "-Wl,-Bsymbolic" might be dangerous IIRC... in general, don't take
> my examples as the holy grail, just as examples :-)
>
Ok, I will follow your examples. I had already taken into account that
CMake problem, and in fact I am already adding CPPFLAGS into CFLAGS.
However, if lintian throws those warnings for me and not for you,
something has to be different between those packages. I will inspect
more carefully at the compilation flags.
Regards,
--
Alberto
More information about the Pkg-osg-devel
mailing list