Package: rsync
Version: 3.0.9-4
Severity: serious
Tags: patch
Justification: fails to build from source
On squeeze, I failed to compile rsync/unstable from source:
dpkg-source -x rsync_3.0.9-4.dsc
cd rsync-3.0.9
dpkg-buildpackage -rfakeroot -b
[...] errors related to compiler not found.. but
Hi Paul,
Thanks for the quick reply. Strange then something must be wrong with my config.
$ ls -l /bin/sh
lrwxrwxrwx 1 root root 4 May 14 2010 /bin/sh - bash*
$ dpkg -l bash
ii bash 4.1-3
The GNU Bourne Again SHell
Attached dpkg-buildpackage stdout log and
You can ignore the DEBUG lines in config.log, it was me trying to
trace the problem by editing configure.sh.
The issue happened here:
configure.sh:2925: x86_64-linux-gnu-gcc -Wall `dpkg-buildflags --get
CFLAGS` -g -O2 conftest.c 5
x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or
On Mon 28 Jan 2013, StalkR wrote:
On squeeze, I failed to compile rsync/unstable from source:
dpkg-source -x rsync_3.0.9-4.dsc
cd rsync-3.0.9
dpkg-buildpackage -rfakeroot -b
[...] errors related to compiler not found.. but after a look at
config.log it was because not expanding
Control: severity -1 normal
On 28.01.2013 12:29, StalkR wrote:
You can ignore the DEBUG lines in config.log, it was me trying to
trace the problem by editing configure.sh.
The issue happened here:
configure.sh:2925: x86_64-linux-gnu-gcc -Wall `dpkg-buildflags --get
CFLAGS` -g -O2 conftest.c
Wierd, your build log shows different lines for the patch output than my
build log:
applying misc Debian patches
for i in debian/patches/*.patch debian/patches/*.diff; do if [ -s $i ]; then
echo $i ...; cat $i | (cd debian/buildtree; patch -p1) || exit 1; fi; done
Ok, thanks Adam, noted.
Paul, yes sorry for the confusion, after that I was trying upstream's
patches/detect-renamed.diff. I confirm I have the same sources and
same output as you without this patch.
On Mon, Jan 28, 2013 at 1:47 PM, Paul Slootman p...@debian.org wrote:
Wierd, your build log
On Mon 28 Jan 2013, StalkR wrote:
Paul, yes sorry for the confusion, after that I was trying upstream's
patches/detect-renamed.diff. I confirm I have the same sources and
same output as you without this patch.
OK, I think the problem lies there: you're applying patches and
confusing configure
No I reported the bug before applying any patch. After I moved on with
my stuff, which is unrelated.
Fresh download and unpack of rsync debian sources give the same error:
$ rm -rf rsync-3.0.9
$ dpkg-source -x rsync_3.0.9-4.dsc
$ cd rsync-3.0.9
$ dpkg-buildpackage -rfakeroot -b
[...]
On Mon, Jan 28, 2013 at 1:40 PM, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or directory
This means you don't have a sufficiently new version of dpkg-dev installed
which supports dpkg-buildflags.
What do you mean exactly by supports
On 28.01.2013 14:44, StalkR wrote:
On Mon, Jan 28, 2013 at 1:40 PM, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or directory
This means you don't have a sufficiently new version of dpkg-dev
installed
which supports dpkg-buildflags.
11 matches
Mail list logo
