[Pkg-osg-devel] Bug: #690878 "pkg-config reports wrong path"

[Manuel A. Fernandez Montecelo]

Brr, too many things at this time of the night, hope to get things
right this time :-(

2012/11/15 Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>:
> That is, the "root" of the target system is set to "debian/tmp", the
> application is then installed in prefix "/usr" in the target system,
> thus "debian/tmp/usr", and the *.install files will get things right
> by using "debian/install" as root of the target system, instead of

I meant: by using _"debian/tmp"_ as root of the target system...

> having to override it with "dh_install -a --sourcedir=debian/tmp/usr".

IIRC, "debian/tmp" is the default one, and so one does not have to
override/set it explicitly.

> Does this sound right?  Did I explain myself?
>
> The changes needed would be then:
> -        $(MAKE) -C build/osgstatic DESTDIR=$(CURDIR)/debian/tmp/usr install
> +        $(MAKE) -C build/osgstatic DESTDIR=$(CURDIR)/debian/tmp/usr install
>  -       $(MAKE) -C build/osg DESTDIR=$(CURDIR)/debian/tmp install
>  +      $(MAKE) -C build/osg DESTDIR=$(CURDIR)/debian/tmp install

Did the modifications (adding/removing "/usr") in the wrong lines, should be:
-        $(MAKE) -C build/osgstatic DESTDIR=$(CURDIR)/debian/tmp/usr install
+        $(MAKE) -C build/osgstatic DESTDIR=$(CURDIR)/debian/tmp install
-       $(MAKE) -C build/osg DESTDIR=$(CURDIR)/debian/tmp/usr install
+      $(MAKE) -C build/osg DESTDIR=$(CURDIR)/debian/tmp install




>> 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?

Sorry, when I wrote this I had only looked at the version in my disk,
not the latest changes to the repository that you made in august,
that's why I went on and on explaining what you already know :o)

BTW, since the changes in august are after the freeze, and as I
explained, I am not 100% sure if they will accept the switch of
debhelper compat as part of the freeze-exception, but we can try
instead of revert if you prefer.

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 :-)


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>