Re: Library Question
Am Samstag, 14. Mai 2011 schrieb Rainer Dorsch: I declared victory too early. Am Freitag, 13. Mai 2011 schrieb Rainer Dorsch: rd@blackbox:/scratchbox/users/rd/home/rd/20110506/navit-0.2.0+dfsg.1$ grep freetype debian/rules DEB_MAKE_ENVVARS = LDFLAGS=-rpath=/opt/freetype-navit rd@blackbox:/scratchbox/users/rd/home/rd/20110506/navit-0.2.0+dfsg.1$ Seems to be not sufficient to get a rpath into navit. Does anybody know how to find out where I need to add the rpath? Are the any suspects under the enviroment varialbes in an autotools build process? I added a patch for Makefile.am . Works now. Many thanks again, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Re: Library Question
I declared victory too early. Am Freitag, 13. Mai 2011 schrieb Rainer Dorsch: rd@blackbox:/scratchbox/users/rd/home/rd/20110506/navit-0.2.0+dfsg.1$ grep freetype debian/rules DEB_MAKE_ENVVARS = LDFLAGS=-rpath=/opt/freetype-navit rd@blackbox:/scratchbox/users/rd/home/rd/20110506/navit-0.2.0+dfsg.1$ Seems to be not sufficient to get a rpath into navit. Does anybody know how to find out where I need to add the rpath? Are the any suspects under the enviroment varialbes in an autotools build process? Thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Re: Library Question
Am Mittwoch, 11. Mai 2011 schrieb Paul Wise: On Tue, May 10, 2011 at 5:00 AM, Rainer Dorsch rdor...@web.de wrote: Can you give a few hints what I need to change in the freetype/debian/rules file to create a libfreetype6-navit package? I would think: - for the private directory: changing the prefix in ./configure - for the package name: dh_strip --dbg-package=libfreetype6 to dh_strip -- dbg-package=libfreetype6-navit Anything else? I haven't looked at freetype, but you probably will need to modify/rename anything that refers to the libfreetype6 package name, including .install files, shlibs/symbols files, control file and more. Worked well. Hmmwhat is the advantage of an rpath compared to a wrapper script with an LD_LIBRARY_PATH? The advantage is that you don't need to create a wrapper script and adjust the build system for it. I added rd@blackbox:/scratchbox/users/rd/home/rd/20110506/navit-0.2.0+dfsg.1$ grep freetype debian/rules DEB_MAKE_ENVVARS = LDFLAGS=-rpath=/opt/freetype-navit rd@blackbox:/scratchbox/users/rd/home/rd/20110506/navit-0.2.0+dfsg.1$ That also worked :-) Paul, that was excellent mentoring. Thank you. Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Re: Library Question
On Tue, May 10, 2011 at 5:00 AM, Rainer Dorsch rdor...@web.de wrote: Can you give a few hints what I need to change in the freetype/debian/rules file to create a libfreetype6-navit package? I would think: - for the private directory: changing the prefix in ./configure - for the package name: dh_strip --dbg-package=libfreetype6 to dh_strip -- dbg-package=libfreetype6-navit Anything else? I haven't looked at freetype, but you probably will need to modify/rename anything that refers to the libfreetype6 package name, including .install files, shlibs/symbols files, control file and more. Hmmwhat is the advantage of an rpath compared to a wrapper script with an LD_LIBRARY_PATH? The advantage is that you don't need to create a wrapper script and adjust the build system for it. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktinjfumeuoqnjmuaubheo9gqchq...@mail.gmail.com
Re: Library Question
Am Montag, 9. Mai 2011 schrieb Paul Wise: On Sun, May 8, 2011 at 5:42 PM, Rainer Dorsch rdor...@web.de wrote: No, navit is a third party application, which I want to package on maemo. Nokia does not ship any version of Navit (they ship the proprietary OVI maps). Freetype belongs to the core system which is shipped by Nokia, which I do not want to change, since I fear that it breaks other stuff. But applying the patch in question specifically, I might consider it as an option... Yes, I understand, Debian would not introduce such a hack (although e.g. libdb comes in a number of versions, libdb4.7, libdb4.8, libdb5.0,...). But I am more looking for a tactical short term solution on which I can iterate and improve (e.g. why should I replace the Nokia freetype, when I do not yet know, that this would fix the problem). Yeah, this situation is similar to backporting. If you are unable to workaround the freetype bug in navit or use an older version of navit that works with that version of freetype, then try this: Since the ABI is the same for both versions of freetype, I would suggest introducing a libfreetype6-navit package that contains the newer freetype library in a private directory and adding an rpath to navit pointing at that directory: http://en.wikipedia.org/wiki/Rpath_(linking) Can you give a few hints what I need to change in the freetype/debian/rules file to create a libfreetype6-navit package? I would think: - for the private directory: changing the prefix in ./configure - for the package name: dh_strip --dbg-package=libfreetype6 to dh_strip -- dbg-package=libfreetype6-navit Anything else? Hmmwhat is the advantage of an rpath compared to a wrapper script with an LD_LIBRARY_PATH? This is better than static linking since you can upgrade libfreetype6-navit separately to navit. Cool, I was not aware of this effort. If GPS and modem support will be added, the have a usable base system, I am really impressed of this effort :-) The biggest challenge are probably the missing hardware drivers (which prohibit e.g. to update the maemo distribution with new kernels). In addition the freesmartphone.org distribution SHR (based on OpenEmbedded) has a port to the N900 (in the early stages): http://shr-project.org/trac/wiki/Devices/NokiaN900 Wow, did not see this one before, but I like pkg-n900 better :-) There is also an Android port: http://www.nitdroid.com/ That one I saw before. I am more interested in a debian based system, than in android right now (given, that it does not work much better than the debian based systems). Many thanks for your comments and links, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ #!/usr/bin/make -f export DH_COMPAT=4 SHELL = /bin/bash CFLAGS = -Wall -g ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) CFLAGS += -O0 else CFLAGS += -O2 endif ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS))) INSTALL_PROGRAM += -s endif # Use soft-float and thumb mode if it enabled. ifneq (,$(findstring thumb,$(DEB_BUILD_OPTIONS))) CFLAGS += -mthumb endif export CFLAGS configure: configure-stamp configure-stamp: dh_testdir tar -xjf freetype-2.3.9.tar.bz2 patch -p0 security-CVE-2009-0946.patch patch -p0 armel-asm-declaration.patch cd freetype-2.3.9 ./configure --prefix=/usr --sysconfdir=/etc touch configure-stamp build: configure-stamp build-stamp build-stamp: dh_testdir $(MAKE) -C freetype-2.3.9 touch build-stamp clean: dh_testdir dh_testroot rm -f build-stamp configure-stamp rm -rf freetype-2.3.9 rm -fr objs/.libs dh_clean install: build dh_testdir dh_testroot dh_clean -k dh_installdirs $(MAKE) -C freetype-2.3.9 install DESTDIR=$(CURDIR)/debian/tmp binary-indep: build install binary-arch: build install dh_testdir dh_testroot dh_makeshlibs -V dh_installchangelogs dh_install --sourcedir=debian/tmp -v dh_strip --dbg-package=libfreetype6 dh_link dh_fixperms dh_makeshlibs -V dh_installdeb dh_shlibdeps dh_gencontrol dh_md5sums dh_builddeb binary: binary-indep binary-arch .PHONY: build clean binary-indep binary-arch binary install configure signature.asc Description: This is a digitally signed message part.
Re: Library Question
Paul, I think I did not describe accurately enough, what I want to do and what boundary condidtions are there. Am Sonntag, 8. Mai 2011 schrieb Paul Wise: Since this is about maemo you can do whatever is allowed there. In Debian we would make an update to freetype with a patch targetting the fix, if the issue is severe enough. yes, I understand. In this case it sounds like Navit is being backported? If so the backport would probably be made to depend on a freetype backport. I'm not that familiar with maemo so No, navit is a third party application, which I want to package on maemo. Nokia does not ship any version of Navit (they ship the proprietary OVI maps). Freetype belongs to the core system which is shipped by Nokia, which I do not want to change, since I fear that it breaks other stuff. But applying the patch in question specifically, I might consider it as an option... I doubt we would introduce a freetype2.3.11 nor statically link navit to freetype. Yes, I understand, Debian would not introduce such a hack (although e.g. libdb comes in a number of versions, libdb4.7, libdb4.8, libdb5.0,...). But I am more looking for a tactical short term solution on which I can iterate and improve (e.g. why should I replace the Nokia freetype, when I do not yet know, that this would fix the problem). PS: You may be interested in joining this effort to port Debian to the Nokia N900: http://wiki.debian.org/pkg-n900 Cool, I was not aware of this effort. If GPS and modem support will be added, the have a usable base system, I am really impressed of this effort :-) The biggest challenge are probably the missing hardware drivers (which prohibit e.g. to update the maemo distribution with new kernels). Many thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Re: Library Question
On Sun, May 8, 2011 at 5:42 PM, Rainer Dorsch rdor...@web.de wrote: No, navit is a third party application, which I want to package on maemo. Nokia does not ship any version of Navit (they ship the proprietary OVI maps). Freetype belongs to the core system which is shipped by Nokia, which I do not want to change, since I fear that it breaks other stuff. But applying the patch in question specifically, I might consider it as an option... Yes, I understand, Debian would not introduce such a hack (although e.g. libdb comes in a number of versions, libdb4.7, libdb4.8, libdb5.0,...). But I am more looking for a tactical short term solution on which I can iterate and improve (e.g. why should I replace the Nokia freetype, when I do not yet know, that this would fix the problem). Yeah, this situation is similar to backporting. If you are unable to workaround the freetype bug in navit or use an older version of navit that works with that version of freetype, then try this: Since the ABI is the same for both versions of freetype, I would suggest introducing a libfreetype6-navit package that contains the newer freetype library in a private directory and adding an rpath to navit pointing at that directory: http://en.wikipedia.org/wiki/Rpath_(linking) This is better than static linking since you can upgrade libfreetype6-navit separately to navit. Cool, I was not aware of this effort. If GPS and modem support will be added, the have a usable base system, I am really impressed of this effort :-) The biggest challenge are probably the missing hardware drivers (which prohibit e.g. to update the maemo distribution with new kernels). In addition the freesmartphone.org distribution SHR (based on OpenEmbedded) has a port to the N900 (in the early stages): http://shr-project.org/trac/wiki/Devices/NokiaN900 There is also an Android port: http://www.nitdroid.com/ -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimdnbpxd2s6hy2_6a6bwubcw2_...@mail.gmail.com
Re: Library Question
Since this is about maemo you can do whatever is allowed there. In Debian we would make an update to freetype with a patch targetting the fix, if the issue is severe enough. In this case it sounds like Navit is being backported? If so the backport would probably be made to depend on a freetype backport. I'm not that familiar with maemo so I doubt we would introduce a freetype2.3.11 nor statically link navit to freetype. PS: You may be interested in joining this effort to port Debian to the Nokia N900: http://wiki.debian.org/pkg-n900 -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktinaeqfonzvw3proy3lmnkrjpx7...@mail.gmail.com
