l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2005 Jan 12 07:56

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Debian Package Tools
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Debian Package Tools

On Tuesday 11 January 2005 09:54, Ken Bloom wrote:
> On Tue, 11 Jan 2005 00:24:41 -0800
> Richard Harke <rharke@earthlink.net> wrote:
> > On Monday 10 January 2005 22:42, Ken Bloom wrote:
> > > On Mon, 10 Jan 2005 20:19:17 -0800
> > >
> > > > > $ debian/rules setup
> > > >
> > > > I tried this but I get the "no rule for target" error
> > > > There are some comments in the rules file about unpacking and
> > > > building. I guess the steps are to be carried out manually. The
> > > > prep.sh script appears to unpack but does not apply patches.
> > > > Interestingly, prep.sh does contain a "subroutine" for patching
> > > > but it is not called.
> > >
> > > What package are you trying to do this to?
> >
> > This is glibc for ia64
> I'm working with this from the maintainers' svn repository at
> http://svn.debian.org/wsvn/pkg-glibc/glibc-package/trunk/debian/?rev=0&sc=0
> 1. I checked the build dependancies in debian/control. There's nothing
> in there that looks like a build system. (e.g. dbs or cdbs) This means
> that everything is self-contained in the debian/directory
> 2. There is a file debian/rules.d/tarball.mk (debian/rules will include
> this file)
> 3. In that file, there is a rule
> unpack: $(stamp)unpack
> $(stamp)unpack: $(DEB_TARBALL) $(patsubst %,$(stamp)%,$(GLIBC_OVERLAYS))
>         touch $(stamp)unpack
> so you want to run
> $ debian/rules unpack
> 4. Now for the patches, there's another file debian/rules.d/dpatch.mk
> (debian/rules will include this file)
> It has 2 rules: patch and unpatch
> so you want to run also
> $ debian/rules patch
> (If you're doing lots of things with patches, you may find the unpatch
> target useful)
Thanks a lot.
I ran both the unpack and patch targets and now I have the code tree
under the build-tree sub-directory.
A few months back, I played around with this but I sometimes by-passed
the debian procedures and the result was very confusing.
The problem I'm having is that it won't load the libGLcore.so module
for the nvidia driver when I startx. This causes KDE to fail. Since it
involves the nvidia binary only driver, I don't think they will consider
a bug report.
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.