Bug#427907: [hppa] git-core selftest failure with -O2 and -O1, -O0 works

2007-06-07 Thread Gerrit Pape
Package: gcc-4.1
Version: 4.1.2-11

See
 
http://buildd.debian.org/fetch.cgi?pkg=git-corever=1%3A1.5.2.1-1arch=hppastamp=1180881720file=log

I can reproduce this in paer's sid chroot as follows:

$ apt-get source git-core
Reading package lists... Done
Building dependency tree... Done
Need to get 1513kB of source archives.
Get:1 http://mirrors.kernel.org sid/main git-core 1:1.5.2.1-1 (dsc) [798B]
Get:2 http://mirrors.kernel.org sid/main git-core 1:1.5.2.1-1 (tar) [1404kB]
Get:3 http://mirrors.kernel.org sid/main git-core 1:1.5.2.1-1 (diff) [109kB]
Fetched 1513kB in 0s (1660kB/s)   
gpg: Signature made Sun Jun  3 05:44:52 2007 MDT using DSA key ID BC70A6FF
gpg: Can't check signature: public key not found
dpkg-source: extracting git-core in git-core-1.5.2.1
dpkg-source: unpacking git-core_1.5.2.1.orig.tar.gz
dpkg-source: applying ./git-core_1.5.2.1-1.diff.gz
$ cd git-core-1.5.2.1/
$ make CFLAGS=-O2 /dev/null  (cd t  sh t6026-merge-attr.sh)
GIT_VERSION = 1.5.2.1
* new build flags or prefix
[...]
* failed 1 among 6 test(s)
$ make CFLAGS=-O0 /dev/null  (cd t  sh t6026-merge-attr.sh)
* new build flags or prefix
/usr/bin/ld: warning: libcrypto.so.0.9.7, needed by
/usr/lib/gcc/hppa-linux-gnu/4.1.3/../../../libcurl.so, may conflict with 
libcrypto.so.0.9.8
/usr/bin/ld: warning: libcrypto.so.0.9.7, needed by
/usr/lib/gcc/hppa-linux-gnu/4.1.3/../../../libcurl.so, may conflict with 
libcrypto.so.0.9.8
Writing perl.mak for Git
*   ok 1: setup
*   ok 2: merge
*   ok 3: check merge result in index
*   ok 4: check merge result in working tree
*   ok 5: custom merge backend
*   ok 6: custom merge backend
* passed all 6 test(s)
$ 

I suspect the compiler's doing bad optimization, all other archs built
successfully.

Thanks, Gerrit.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#427907: [hppa] git-core selftest failure with -O2 and -O1, -O0 works

2007-06-07 Thread Matthias Klose
probably related to #427398.

Gerrit Pape writes:
 Package: gcc-4.1
 Version: 4.1.2-11
 
 See
  
 http://buildd.debian.org/fetch.cgi?pkg=git-corever=1%3A1.5.2.1-1arch=hppastamp=1180881720file=log
 
 I can reproduce this in paer's sid chroot as follows:
 
 $ apt-get source git-core
 Reading package lists... Done
 Building dependency tree... Done
 Need to get 1513kB of source archives.
 Get:1 http://mirrors.kernel.org sid/main git-core 1:1.5.2.1-1 (dsc) [798B]
 Get:2 http://mirrors.kernel.org sid/main git-core 1:1.5.2.1-1 (tar) [1404kB]
 Get:3 http://mirrors.kernel.org sid/main git-core 1:1.5.2.1-1 (diff) [109kB]
 Fetched 1513kB in 0s (1660kB/s)   
 gpg: Signature made Sun Jun  3 05:44:52 2007 MDT using DSA key ID BC70A6FF
 gpg: Can't check signature: public key not found
 dpkg-source: extracting git-core in git-core-1.5.2.1
 dpkg-source: unpacking git-core_1.5.2.1.orig.tar.gz
 dpkg-source: applying ./git-core_1.5.2.1-1.diff.gz
 $ cd git-core-1.5.2.1/
 $ make CFLAGS=-O2 /dev/null  (cd t  sh t6026-merge-attr.sh)
 GIT_VERSION = 1.5.2.1
 * new build flags or prefix
 [...]
 * failed 1 among 6 test(s)
 $ make CFLAGS=-O0 /dev/null  (cd t  sh t6026-merge-attr.sh)
 * new build flags or prefix
 /usr/bin/ld: warning: libcrypto.so.0.9.7, needed by
 /usr/lib/gcc/hppa-linux-gnu/4.1.3/../../../libcurl.so, may conflict with 
 libcrypto.so.0.9.8
 /usr/bin/ld: warning: libcrypto.so.0.9.7, needed by
 /usr/lib/gcc/hppa-linux-gnu/4.1.3/../../../libcurl.so, may conflict with 
 libcrypto.so.0.9.8
 Writing perl.mak for Git
 *   ok 1: setup
 *   ok 2: merge
 *   ok 3: check merge result in index
 *   ok 4: check merge result in working tree
 *   ok 5: custom merge backend
 *   ok 6: custom merge backend
 * passed all 6 test(s)
 $ 
 
 I suspect the compiler's doing bad optimization, all other archs built
 successfully.
 
 Thanks, Gerrit.
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]