Re: UNable to configure my package

all other source code (becoz i have made changes to them according to my requirement) that i have installed using make install, otherwise i wouldn't be able to make a deb package. thanks and regards varun Raphael Hertzog-3 wrote: > > On Wed, 26 Sep 2007, varun_shrivastava wrote: >

Unable to strip using dh_strip

hi i am trying to build a package using debhelper scripts, but it gives an error message dh_installdirs -a dh_install -a dh_link -a dh_compress -a dh_strip -a dh_fixperms -a dh_makeshlibs -plibfreetype6 -V'libfreetype6 (>> 6.3.10)' dh_shlibdeps -a dh_installdeb -a /scratchbox/tools/bin/instal

Re: Unable to strip using dh_strip

Justin Pryzby-43 wrote: > > > Can you set DH_DEBUG like at the head of the rulesfile and rerun? > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > thanks i added line export DH_DEBUG=1 on top of rules file b

Re: Unable to strip using dh_strip

Justin Pryzby-43 wrote: > > Well 2 things come to mind. Is scratchbox "install" compatibile with > debhelper? Also ls -la debian/libfreetype6/DEBIAN > > Removing "dh_strip" builds the package, it shouldn't have build if scratchbox have incompatible "install"? ls -la debian/libfreetype6/ dis

binary-or-shlib-defines-rpath error message

hi i am a newbee in packaging and trying out how to package some already available source packages i am trying to pack jpeg62_6b, the package builds successfully but running lintian shows "binary-or-shlib-defines-rpath ./usr/bin/cjpeg /usr/lib" the message is same for all binaries in /usr/bi

Re: binary-or-shlib-defines-rpath error message

Justin Pryzby-43 wrote: > > Is this the same package that caused dh_strip errors? > No its not. Justin Pryzby-43 wrote: > > You shouldn't set rpath to /usr/lib since it's in the default search > path. > I haven't set the path any where in the rules file. but i am trying to install it using

Re: binary-or-shlib-defines-rpath error message

hi Justin Pryzby-43 wrote: > > > packagename.shlibs is what gets installed to /v/l/d/i. shlibs.local > is an additional thing read by dpkg-shlibdeps for cases when someone > elses public library package doesn't include packagename.shlibs. In > this case dpkg wouldn't otherwise be able to fin

How a package will determine the dependencies

hi i have a library and want to package it But it has a configuration option as --enable-debug=yes/no So i need to make 2 packages as 1) libinput0 2) libinput0-debug So now if an application uses libinput, how the $(shlibs:Depends) variable get substituted, during application package being bui

Re: how to just copy files that don't need compiled? and set up a cron job?

hi try this mkdir -p $(CURDIR)/debian//opt/gsi-tools cp GSITools.pm $(CURDIR)/debian//opt/gsi-tools/ cp GSIManagementService.pl $(CURDIR)/debian//opt/gsi-tools bye varun -- View this message in context: http://www.nabble.com/how-to-just-copy-files-that-don%27t-need-compiled--

Re: How a package will determine the dependencies

hi actually the library uses g_log kind of debugging technique ie some #defines are there, so when log is enabled #defines get replaced by g_log(***), and when its disabled #defines get replaced by (void)0 But i have a bigger problem thats the library has one more option of --enable-sdl=yes/no ,

Re: How a package will determine the dependencies

Justin Pryzby-43 wrote: > > > Do you mean it adds stuff within a #ifdef to use SDL? Why is it so > huge? > > > yes it adds code not so huge under #ifdef SDL_ENABLE ... #endif Can we provide a virtual package libinput-virtual on which the applications will depend and the virtual packag

Re: How a package will determine the dependencies

Justin Pryzby-43 wrote: > > On Fri, Nov 02, 2007 at 08:13:22AM -0700, varun_shrivastava wrote: > You could have libinput0-debug provides:libinput0. > > However I still think the best way is to compile with debugging > symbols and move the symbols to separate files in

Executable's execute permission not getting set

hi I have one more question the package contains an executable file in /usr/bin but its permissions are set as -rw-r--r-- but it should be -r-x-r-x-r-x here is a part of my rules file 60 install: build 61 dh_testdir 62 dh_testroot 63 dh_clean -k 64

Re: Executable's execute permission not getting set

Cyril Brulebois wrote: > > Fixes ownership, and some permissions, but not in /usr/bin (see its > manpage). I guess your build system is somehow missing a chmod +x on the > generated binary. > > Cheers, > Cyril Brulebois > the executable installed has permissions set to +x but the package does