Package: klic Version: 3.003-gm1-2.1 Severity: serious Hello,
There was a problem while autobuilding your package: > Automatic build of klic_3.003-gm1-2.1 on avidan by sbuild/i386 0.49 > Build started at 20060805-1115 > ****************************************************************************** ... > spawn ./Configure > # > # WELCOME TO KLIC SYSTEM CONFIGURATION SCRIPT > # > # Copyright 1994 Institute for New Generation Computer Technology > # Read COPYRIGHT for detailed information > # > # In this script, I'll ask you for several options you can make. > # Default values are presented in brackets as in [default]. > # If the default is OK, simply hit CR. > # Otherwise, type in whatever is your option. > # When you want to specify nothing, type in "none". > # > > > > # This is version of KLIC contains its sequential core, > # a distributed parallel implementation and a shared memory parallel > # implementation that works either on Sparc-based system with Solaris > # 2.X or Alpha-based system with DEC OSF/1 with gcc. > # > # The sequential core is mandatory. > # Installation of parallel implementations is optional. > > > Configure also for parallel implementations? (yes or no) > [no] # Found gcc in /usr/bin/gcc. > # I'd recommend using gcc for installing KLIC, as it's been tested > # mainly with gcc. > > > Which C compiler to use? [gcc] > > # During the installation procedure, the runtime library for the KLIC system > # will be compiled using gcc. > # > # You can choose optimization and debug flags for this compilation now > # (I'll ask you about setting for compiling user programs later). > > > Which optimization level to use? [2] > Which debug flags to use? [-g] > > # When KL1 programs are compiled, they are compiled into C code and then > # compiled into executable using gcc. You can specify optimization level > # and debug flag for gcc in the command line argument for the KLIC compiler. > # > # You can here select flags that'll be only set for optimized compilation, > # that is, flags that'll be supplied only when you specified -O# when you > # run the KLIC compiler. > > > Which additional optimization flags to use? [-fomit-frame-pointer] > > # You can specify addtional flags for gcc. > # If "-pipe" is available, specify it here. > > > Which C compiler flags to use? [none] > > # If you want to link Fortran code w/ KLIC code, please reply > # to the following questions. > > > Which Fortran compiler to use? [none] > > # KLIC will normally use gcc for linkage also, > # but you can specify a different linker. > > > May I use gcc for linkage also? (yes or no) > [yes] > # link command is used during the system compilation. > # I'd recommend to use sumbolic link if your system supports. > > > Which link command to use? [ln -s] > > # For KLIC to support asynchronous stream I/O, the system should > # deliver signals such as SIGIO or SIGPOLL when I/O becomes possible. > # However, some systems (such as Linux 1.0) does not support this. > > > Does your system support I/O ready signals? (yes or no) > [yes] > # The KLIC system will be installed under certain directories. > # You have to be able to write into that directory for installation. > # Also, the installed files under the directory should be visible from > # all the KLIC users (only yourself for a private installation). > # > # First, the root of the installation directory tree. > > > Which installation root directory to use? [/usr/local] /usr > > > # By default, KLIC system will be installed in the subdirectories of > # the directory you specified (/usr). > # In the default setting, subdirectories used are: > # /usr/bin: for user command (klic) > # /usr/lib: for subprograms and libraries > # /usr/include: for header files > > > May I use the default setting? (yes or no) > [yes] !!! You do not have write access to /usr/bin !!! > Which user command directory to use? [/usr/bin] > !!! You do not have write access to /usr/lib !!! > Which library directory to use? [/usr/lib] > !!! You do not have write access to /usr/include !!! > Which include file directory to use? [/usr/include] > > # Specify directories for library archives. > # Default library directories are: /lib /usr/lib /usr/local/lib > > Do you want to change the default? (yes or no) > [no] > Which default include file directory directory to use? [/usr/include] > > # Specify library archive files. > # Default library archives are: libm libnsl > > Do you want to change the default? (yes or no) > [no] > # Using library file(s): /usr/lib/libm.a /usr/lib/libnsl.a > > # Specify directories for header files at KL1 program compilation. > # Default include directory for compiling KLIC are: /usr/include > > Do you want to change the default? (yes or no) > [no] > # KLIC has a multi-window tracer using X window. > > Do you want to use X-based multi-window tracer? (yes or no) [no] touch > configure-stamp > dh_testdir > # Add here commands to compile the package. > cd klic-3.003 && /usr/bin/make > make[1]: Entering directory `/build/buildd/klic-3.003-gm1/klic-3.003' > make[1]: *** No targets specified and no makefile found. Stop. > make[1]: Leaving directory `/build/buildd/klic-3.003-gm1/klic-3.003' > make: *** [build-stamp] Error 2 > ****************************************************************************** > Build finished at 20060805-1116 > FAILED [dpkg-buildpackage died] > ------------------------------------------------------------------------------ -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
signature.asc
Description: Digital signature
