Your message dated Sun, 10 Feb 2008 11:23:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line atlas: FTBFS: prompts during build
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: atlas
version: 3.6.0-21.2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080205 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
Relevant part:
> dpkg-source: building atlas in atlas_3.6.0-21.2.dsc
> debian/rules build
> [ -e debian/i386/base/applied_sys ] || ! [ -e debian/i386/base/patch_sys ]
> || \
> patch -p1 < debian/i386/base/patch_sys
> touch debian/i386/base/applied_sys
> dh_testdir
> make killall arch=Linux_3dnow_static
> make[1]: Entering directory `/build/user/atlas-3.6.0'
> make -f Make.top killall arch=Linux_3dnow_static
> make[2]: Entering directory `/build/user/atlas-3.6.0'
> Make.top:2: Make.Linux_3dnow_static: No such file or directory
> make[2]: *** No rule to make target `Make.Linux_3dnow_static'. Stop.
> make[2]: Leaving directory `/build/user/atlas-3.6.0'
> make[1]: *** [killall] Error 2
> make[1]: Leaving directory `/build/user/atlas-3.6.0'
> make: [bin/Linux_3dnow_static/Make.inc] Error 2 (ignored)
> chmod +x debian/config.expect
> [ -n "" ] || . debian/i386/3dnow/env ; \
> ARCH_DIR=Linux_3dnow_static CACHE_SIZE= BIT=1 DEFAULTS=y \
> TDNCOMP=y debian/config.expect
> spawn make
> make[1]: Entering directory `/build/user/atlas-3.6.0'
> gcc-4.3 -o xconfig config.c
> /tmp/ccIA2tMk.o: In function `CmndResults':
> config.c:(.text+0x936): warning: the use of `tmpnam' is dangerous, better
> use `mkstemp'
> ./xconfig
> ATLAS3.6.0 configure started.
>
> 160
> 159
> 158
> 157
> 156
> 155
> 154
> 153
> 152
> 151
> 150
> 149
> 148
> 147
> 146
> 145
> 144
> 143
> 142
> 141
> 140
> 139
> 138
> 137
> 136
> 135
> 134
> 133
> 132
> 131
> 130
> 129
> 128
> 127
> 126
> 125
> 124
> 123
> 122
> 121
> 120
> 119
> 118
> 117
> 116
> 115
> 114
> 113
> 112
> 111
> 110
> 109
> 108
> 107
> 106
> 105
> 104
> 103
> 102
> 101
> 100
> 099
> 098
> 097
> 096
> 095
> 094
> 093
> 092
> 091
> 090
> 089
> 088
> 087
> 086
> 085
> 084
> 083
> 082
> 081
> 080
> 079
> 078
> 077
> 076
> 075
> 074
> 073
> 072
> 071
> 070
> 069
> 068
> 067
> 066
> 065
> 064
> 063
> 062
> 061
> 060
> 059
> 058
> 057
> 056
> 055
> 054
> 053
> 052
> 051
> 050
> 049
> 048
> 047
> 046
> 045
> 044
> 043
> 042
> 041
> 040
> 039
> 038
> 037
> 036
> 035
> 034
> 033
> 032
> 031
> 030
> 029
> 028
> 027
> 026
> 025
> 024
> 023
> 022
> 021
> 020
> 019
> 018
> 017
> 016
> 015
> 014
> 013
> 012
> 011
> 010
> 009
> 008
> 007
> 006
> 005
> 004
> 003
> 002
> 001
> Enter number at top left of screen [0]: ^J
> ===============================================================================
> IMPORTANT
> ===============================================================================
> Before going any further, check
> http://math-atlas.sourceforge.net/errata.html
> This is the ATLAS errata file, which keeps a running count of all known
> ATLAS bugs and system problems, with associated workarounds or fixes.
> IF YOU DO NOT CHECK THIS FILE, YOU MAY BE COMPILING A LIBRARY WITH KNOWN
> BUGS.
>
> Have you scoped the errata file? [y]: ^J
> Configure will ask a series of questions, in one of two forms. The first
> form
> of question is a menu of choices. One option in almost all menus is
> 'Other/UNKNOWN'. If you are unsure of the answer, always choose this option.
> The second form of question is a single line, with a default answer shown in
> square braces. If you hit return without typing anything, this default
> answer
> will be used. Again, if you are unsure of the answer, simply accept the
> default.
>
> ATLAS can detect almost everything it needs to know, so choosing the default
> or 'Other/UNKNOWN' will at worst simply extend the install time (if you tell
> config the answer to something ATLAS can skip some tests).
>
> Configure makes no changes to the state of things until all questions have
> been asked and answered. Therefore, if you get confused and want to start
> over, feel free to break out of this program (CTRL-C, CTRL-BREAK, etc)
> and start again. Alternatively, if you make a mistake you can finish the
> configure process, and then edit the created make include file by hand to fix
> the mistake manually (the name and location of this file will be printed
> out at the end of configure).
>
> If you have problems during configure or installation, consult the file
> 'ATLAS/README/TroubleShoot.txt'.
>
> Are you ready to continue? [y]: ^JProbing to make operating system
> determination:
> Operating system configured as Linux
>
> Probing for architecture:
> Architecture is set to ATHLON
>
>
> Probing for supported ISA extensions:
> AltiVec: NO.
> AltiVec: NO.
> SSE2: NO.
> SSE1: NO.
> 3DNow2: DETECTED!
>
> ATLAS has detected that your machine has 3DNow! capability, and ATLAS
> can use these instructions to dramatically speed up single precision
> operations. However, 3DNow! does not use IEEE compliant arithmetic;
> in particular, it does not handle NaNs or Infinities at all (operations
> on them are essentially undefined), and it does not handle overflow or
> underflow correctly. There may be other discrepencies as well. Therefore,
> only enable 3DNow! if you are very sure that these shortcomings in
> accuracy do not concern you. In general, getting the answer very fast
> is no substitute for getting the *correct* answer, so just say no if
> you are at all unsure.
> Use 3DNow! for computation? [n]: y^J
> ATLAS can provide SMP support for the Level 3 BLAS via Posix threads.
> If you choose to build a threaded library, ATLAS will compile all
> aspects of the library (including the serial components) with the
> threaded compiler/link flags. Most machines can use the serial
> library even when it is compiled with threaded options, but this
> is not guaranteed to work, so if you want a true serial library,
> answer no to threading below.
> enable Posix threads support? [y]: n^JNumber of CPUs: 1
>
> Required cache flush detected as : 8388608 bytes
> Looking for compilers (this may take a while):
> /usr/bin/gcc : v4.2.3
> gfortran -fomit-frame-pointer -O rejected
> F77 = gfortran -O
> CC = /usr/bin/gcc -fomit-frame-pointer -O3 -funroll-all-loops
> MCC = /usr/bin/gcc -fomit-frame-pointer -O
>
> FINDING tar, gzip, AND gunzip
> tar : /bin/tar
> gzip : /bin/gzip
> gunzip : /bin/gunzip
>
>
> ATLAS has default parameters for OS='Linux' and system='ATHLON'.
> If you want to just trust these default values, you can use express setup,
> drastically reducing the amount of questions you are required to answer
>
> use express setup? [y]: ^J
>
>
>
> You need to choose a name which represents this architecture (eg. UltraSparc,
> Dec21164, etc). Do not use a generic name (eg. solaris, linux), which might
> apply to different hardware. This architecture name will be appended to the
> name of the created make include file, and appear in all subdirectories, so
> don't make it longer than you like to type. The name should follow the rules
> for file names (so don't use punctuation and spaces, for instance).
>
> Enter Architecture name (ARCH) [Linux_ATHLON3DNow2]:
> Linux_3dnow_static^J<arch> set to 'Linux_3dnow_static'
>
>
>
> ATLAS probed the system and determined that the following amount of memory
> (in kilobytes) would be required to completely flush the cache of your
> system. However, this amount of memory may cause swapping if you don't
> have enough physical memory available. Some timers may use 3 times this
> much memory purely for cache flushing (not including operands being timed).
> So, if this value looks too large, decrease it (meaning ATLAS may not tune
> itself perfectly since some operands will be cache resident), otherwise
> hit enter to install with default. If this causes the ATLAS timers to
> swap, you can always reinstall and supply a smaller value for this entry.
>
> Enter Maximum cache size (KB) [8192]: ^J
> The ATLAS install process is heavily file-based, and this can cause major
> reliability problems when interacting with an overloaded or malfunctioning
> remotely mounted filesystem. ATLAS therefore has a mechanism in place to
> allow for a delay before a file is declared to not be there, so that
> slow NFS (i.e., waiting for amd timout) problems can be overcome, or for
> handling slightly differing clocks between server/client. This problem is
> magnified if doing cross-compilation. In the question below, we ask how
> much of a delay, in seconds, ATLAS should tolerate between file creation
> and appearance. If you are installing on a local filesystem (eg. /tmp) or
> a smooth-running NFS system, answer 0; for a moderately loaded NFS server,
> you
> may want a value in the 10 second range, and for cross-compiling systems or
> NFS servers experiencing errors, you may want to go as high as a couple
> of minutes (120).
> Enter File creation delay in seconds [0]: ^J
>
> I'm going to ask you for information about your Fortran 77 compiler. ATLAS
> does not need Fortran77 to build, so if you don't have a Fortran compiler,
> the install can still be completed successfully. However, ATLAS built
> without
> a Fortran compiler will not be callable from Fortran (i.e., the user should
> use the C interface), and we will not be able to do full testing, since some
> of
> the tester code is written in Fortran77.
>
>
>
> I'm going to ask you for information about your Fortran 77 compiler. ATLAS
> does not need Fortran77 to build, so if you don't have a Fortran compiler,
> the install can still be completed successfully. However, ATLAS built
> without
> a Fortran compiler will not be callable from Fortran (i.e., the user should
> use the C interface), and we will not be able to do full testing, since some
> of
> the tester code is written in Fortran77.
>
> F77 = 'gfortran -O' doesn't seem to work for me.
> Enter 1 to enter a different F77, 0 to continue with none [1]: couldn't
> execute "kill": no such file or directory
> while executing
> "exec kill -TERM $i"
> invoked from within
> "expect -re "ready to continue?" {send "\n" ; exp_continue} \
> "Enter number at top left of screen" {send "\n" ; exp_continue} \
> "ENTER TO CONTINUE" {..."
> (file "debian/config.expect" line 6)
> make: *** [bin/Linux_3dnow_static/Make.inc] Error 1
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
> Build killed with signal TERM after 240 minutes of inactivity
The full build log is available from:
http://people.debian.org/~lucas/logs/2008/02/05
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
Version: 3.6.0-21.3
--- End Message ---
