On Thu, Oct 19, 2000 at 09:32:23AM +0200, Othmar Pasteka wrote:
> hi,
>
> i have a bugreport for a package which is solved in a new
> version. and the bug report told me that it is fixed in the new
> package. it's a woody package but compiled for potato but
> shouldn't be a problem because it onl
On Sun, Oct 22, 2000 at 06:03:07PM +0100, Steve Dobson wrote:
> > > dh_testdir
> > > mkdir option1-build-dir
> > > cd option1-build-dir
> > > ../configure --with-one-set-of-options && $(MAKE)
> > > cd ..
> >
> > Only you can't have cd's on separate lines, be
On Sun, Oct 22, 2000 at 06:13:27PM +0200, Josip Rodin wrote:
> On Sun, Oct 22, 2000 at 10:07:12AM -0400, Adam C Powell IV wrote:
> > dh_testdir
> > mkdir option1-build-dir
> > cd option1-build-dir
> > ../configure --with-one-set-of-options && $(MAKE)
> > cd .
On Sun, Oct 22, 2000 at 10:07:12AM -0400, Adam C Powell IV wrote:
> > > I fail to see how to run configure twice, with different options in the
> > > build-stamp rule and then install both into the right place in the install
> > > rule (I just get identical stuff pacakged in two locations),
> >
> >
On Sun, Oct 22, 2000 at 06:03:07PM +0100, Steve Dobson wrote:
> > > dh_testdir
> > > mkdir option1-build-dir
> > > cd option1-build-dir
> > > ../configure --with-one-set-of-options && $(MAKE)
> > > cd ..
> >
> > Only you can't have cd's on separate lines, b
On Sun, Oct 22, 2000 at 06:13:27PM +0200, Josip Rodin wrote:
> On Sun, Oct 22, 2000 at 10:07:12AM -0400, Adam C Powell IV wrote:
> > dh_testdir
> > mkdir option1-build-dir
> > cd option1-build-dir
> > ../configure --with-one-set-of-options && $(MAKE)
> > cd
Josip Rodin wrote:
> On Sat, Oct 21, 2000 at 08:59:17PM +0100, Roger Leigh wrote:
> > I fail to see how to run configure twice, with different options in the
> > build-stamp rule and then install both into the right place in the install
> > rule (I just get identical stuff pacakged in two location
On Sun, Oct 22, 2000 at 10:07:12AM -0400, Adam C Powell IV wrote:
> > > I fail to see how to run configure twice, with different options in the
> > > build-stamp rule and then install both into the right place in the install
> > > rule (I just get identical stuff pacakged in two locations),
> >
>
On 20001021T205917+0100, Roger Leigh wrote:
> I have made a package with debhelper and dh_make, which produces a single
> binary deb. However, now I would like to make two binaries from the same
> packages, identical except for that each is built with different options
> to configure (one has suppo
Josip Rodin wrote:
> On Sat, Oct 21, 2000 at 08:59:17PM +0100, Roger Leigh wrote:
> > I fail to see how to run configure twice, with different options in the
> > build-stamp rule and then install both into the right place in the install
> > rule (I just get identical stuff pacakged in two locatio
On Sun, Oct 22, 2000 at 02:46:18PM +1100, Hamish Moffatt wrote:
> > > debian/rules:
> > > make install DESTDIR=`pwd`/debian/tmp
> >
> > BTW s/`pwd`/$(CURDIR)/
>
> Why not just
>
> make install DESTDIR=debian/tmp
>
> ? I've never understood why an absolute path is needed for that command.
It's
On Sat, Oct 21, 2000 at 08:59:17PM +0100, Roger Leigh wrote:
> I fail to see how to run configure twice, with different options in the
> build-stamp rule and then install both into the right place in the install
> rule (I just get identical stuff pacakged in two locations),
Well, it's simple reall
On Sat, Oct 21, 2000 at 08:44:15PM +0200, Falk Hueffner wrote:
> > > debian/rules:
> > > make install DESTDIR=`pwd`/debian/tmp
> >
> > BTW s/`pwd`/$(CURDIR)/
>
> Uhm, why?
Because using back quotes will fork for another shell command, whereas
CURDIR is a pre-made make variable holding the same t
On 20001021T205917+0100, Roger Leigh wrote:
> I have made a package with debhelper and dh_make, which produces a single
> binary deb. However, now I would like to make two binaries from the same
> packages, identical except for that each is built with different options
> to configure (one has supp
On Sun, Oct 22, 2000 at 02:46:18PM +1100, Hamish Moffatt wrote:
> > > debian/rules:
> > > make install DESTDIR=`pwd`/debian/tmp
> >
> > BTW s/`pwd`/$(CURDIR)/
>
> Why not just
>
> make install DESTDIR=debian/tmp
>
> ? I've never understood why an absolute path is needed for that command.
It's
On Sat, Oct 21, 2000 at 08:59:17PM +0100, Roger Leigh wrote:
> I fail to see how to run configure twice, with different options in the
> build-stamp rule and then install both into the right place in the install
> rule (I just get identical stuff pacakged in two locations),
Well, it's simple real
On Sat, Oct 21, 2000 at 08:44:15PM +0200, Falk Hueffner wrote:
> > > debian/rules:
> > > make install DESTDIR=`pwd`/debian/tmp
> >
> > BTW s/`pwd`/$(CURDIR)/
>
> Uhm, why?
Because using back quotes will fork for another shell command, whereas
CURDIR is a pre-made make variable holding the same
17 matches
Mail list logo
