• Bug#251989: FTBFS i386: configure script to old and --host missing for

    From Goswin von Brederlow@1:229/2 to All on Mon Aug 16 13:00:19 2004
    From: [email protected]

    dpkg-buildpackage: source package is libsigc++-2.0
    dpkg-buildpackage: source version is 2.0.3-1
    dpkg-buildpackage: source maintainer is Daniel Burrows <[email protected]> dpkg-buildpackage: host architecture is i386
    fakeroot debian/rules clean
    dh_testdir
    dh_testroot
    if [ -f debian/soname-specific-files ]; then rm -f `cat debian/soname-specific-files`; rm debian/soname-specific-files; fi
    dh_testdir
    dh_testroot
    if [ -d builddir ]; then rm -rf builddir; fi
    #-for x in debian/*.patch; do patch --dry-run -fRp1 < $x > /dev/null&&\
    patch -fRp1 < $x ; done
    dh_clean build-stamp config-stamp install-stamp debian/shlibs.local
    debian/rules build
    dh_testdir
    #for x in debian/*.patch; do patch --dry-run -fp1 < $x > /dev/null && \
    patch -fp1 < $x; done
    test -d builddir || mkdir builddir
    cd builddir && ../configure --prefix=/usr
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking for gm4... no
    checking for m4... m4
    checking for perl... /usr/bin/perl
    checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc
    checking for C compiler default output... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ANSI C... none needed
    checking for style of include used by make... GNU
    checking dependency style of gcc... gcc3
    checking how to run the C preprocessor... gcc -E
    checking for some Win32 platform... no
    checking for a sed that does not truncate output... /bin/sed
    checking for egrep... grep -E
    checking for ld used by gcc... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking for /usr/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking whether ln -s works... yes
    checking how to recognise dependent libraries... file_magic ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib )
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for g++... g++
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking dependency style of g++... gcc3
    checking how to run the C++ preprocessor... g++ -E
    checking for g77... no
    checking for f77... no
    checking for xlf... no
    checking for frt... no
    checking for pgf77... no
    checking for fl32... no
    checking for af77... no
    checking for fort77... no
    checking for f90... no
    checking for xlf90... no
    checking for pgf90... no
    checking for epcf90... no
    checking for f95... no
    checking for fort... no
    checking for xlf95... no
    checking for lf95... no
    checking for g95... no
    checking whether we are using the GNU Fortran 77 compiler... no
    checking whether accepts -g... no
    checking the maximum length of command line arguments... 32768
    checking command to parse /usr/bin/nm -B output from gcc object... ok
    checking for objdir... .libs
    checking for ar... ar
    checking for ranlib... ranlib
    checking for strip... strip
    checking for file... /usr/bin/file
    checking if gcc static flag works... yes
    checking if gcc supports -fno-rtti -fno-exceptions... no
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc supports -c -o file.o... yes
    checking whether the gcc linker (/usr/bin/ld -m elf_i386) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... no
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    configure: creating libtool
    appending configuration tag "CXX" to libtool
    checking for ld used by g++... /usr/bin/ld -m elf_i386
    checking if the linker (/usr/bin/ld -m elf_i386) is GNU ld... no
    checking whether the g++ linker (/usr/bin/ld -m elf_i386) supports shared libraries... yes
    checking for g++ option to produce PIC... -fPIC
    checking if g++ PIC flag -fPIC works... yes
    checking if g++ supports -c -o file.o... yes
    checking whether the g++ linker (/usr/bin/ld -m elf_i386) supports shared libraries... yes
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking dynamic linker characteristics... GNU/Linux ld.so
    appending configuration tag "F77" to libtool
    checking whether we are using the GNU C++ compiler... (cached) yes
    checking whether g++ accepts -g... (cached) yes
    checking dependency style of g++... (cached) gcc3
    checking if C++ compiler supports the use of a particular specialization when calling operator() template methods.... yes
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating sigc++-2.0.pc
    config.status: creating sigc++/Makefile
    config.status: creating scripts/Makefile
    config.status: creating tests/Makefile
    config.status: creating examples/Makefile
    config.status: creating MSVC_Net2003/Makefile
    config.status: creating docs/Makefile
    config.status: creating docs/images/Makefile
    config.status: creating docs/reference/Makefile
    config.status: creating docs/reference/Doxyfile
    config.status: creating sigc++config.h
    config.status: executing depfiles commands
    touch config-stamp
    dh_testdir -a
    #cd builddir && perl -i -pe 's/^(hardcode_libdir_flag_spec\s*=\s*).+$/$1" -D__LIBTOOL_IS_A_FOOL__ "/' libtool
    cd builddir && /usr/bin/make
    make[1]: Entering directory `/tmp/foo/libsigc++-2.0-2.0.3/builddir' /usr/bin/make all-recursive

    [continued in next message]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Daniel Burrows@1:229/2 to All on Mon Aug 16 18:00:15 2004
    From: [email protected]

    libsigc++2.0 builds just fine on i386, both sid and sarge. (yes, I
    just tested it on my own system and pbuilder) Maybe something is wrong
    with your build environment.

    Daniel

    --
    /-------------------- Daniel Burrows <[email protected]> -------------------\ | Almost Winter, Winter, Still Winter, and Construction. | \---- Be like the kid in the movie! Play chess! -- http://www.uschess.org ---/


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

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Goswin von Brederlow@1:229/2 to Daniel Burrows on Mon Aug 16 20:00:16 2004
    From: [email protected]

    Daniel Burrows <[email protected]> writes:

    libsigc++2.0 builds just fine on i386, both sid and sarge. (yes, I
    just tested it on my own system and pbuilder) Maybe something is wrong
    with your build environment.

    Daniel

    Do you have an amd64 (x86_64) cpu running a 64bit kernel?

    MfG
    Goswin


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

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Daniel Burrows@1:229/2 to All on Mon Aug 16 20:30:13 2004
    From: [email protected]

    On Mon, Aug 16, 2004 at 07:35:01PM +0200, Goswin von Brederlow <[email protected]> was heard to say:
    Daniel Burrows <[email protected]> writes:

    libsigc++2.0 builds just fine on i386, both sid and sarge. (yes, I
    just tested it on my own system and pbuilder) Maybe something is wrong with your build environment.

    Daniel

    Do you have an amd64 (x86_64) cpu running a 64bit kernel?

    No, nor does Debian.

    Daniel

    --
    /-------------------- Daniel Burrows <[email protected]> -------------------\ | "A game which, from the viewpoint of the other players (ie, everyone) might | | be compared to playing poker with blank cards, for infinite stakes, with a | | Dealer who won't tell you the rules and who /smiles all the time/." | | -- Terry Pratchett, _Good Omens_ | \------------- Got APT? -- Debian GNU/Linux http://www.debian.org ------------/


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

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Daniel Burrows@1:229/2 to All on Mon Aug 16 20:40:12 2004
    From: [email protected]

    I just remembered that sig *1.2* is frozen for sarge, not 2.0, so
    there isn't a problem with uploading a new version. However, I'd rather
    not stress the autobuilders unnecessarily. I think that upstream is
    slowly working towards another release, and I was planning to just roll
    this into that release; does that work for you? (note that 2.0.4 might
    not make sarge in that case, depending on how long they take)

    Daniel

    --
    /-------------------- Daniel Burrows <[email protected]> -------------------\ | Human beings were created by water to transport it uphill. | \-Evil Overlord, Inc: planning your future today. http://www.eviloverlord.com-/


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

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Goswin von Brederlow@1:229/2 to Daniel Burrows on Tue Aug 17 06:40:07 2004
    From: [email protected]

    Daniel Burrows <[email protected]> writes:

    I just remembered that sig *1.2* is frozen for sarge, not 2.0, so
    there isn't a problem with uploading a new version. However, I'd rather
    not stress the autobuilders unnecessarily. I think that upstream is
    slowly working towards another release, and I was planning to just roll
    this into that release; does that work for you? (note that 2.0.4 might
    not make sarge in that case, depending on how long they take)

    Daniel

    Not realy.

    The amd64 and intel em64t cpus will be very common in the near future
    and if all goes well sarge will have a 64bit kernel image for
    them (so people don't have to compile their own).

    The package has a FTBFS bug on those cpus because you fail to pass
    "--host" and the configure script is too old to work without.
    libsig2.0 needs to be fixed for sarge or removed. Since you just need
    to update the generated files and add a "--host=..." in rules to be
    policy compliant I don't see a reason to make an exception.

    MfG
    Goswin


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

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Daniel Burrows@1:229/2 to All on Tue Aug 17 17:00:11 2004
    From: [email protected]

    severity 251989 serious
    severity 254174 serious
    merge 251989 254174
    thanks

    If that's the case, this should be "serious".

    Off to load up the autobuilders with a change that's pointless for
    99.99% of the user base,
    Daniel

    --
    /-------------------- Daniel Burrows <[email protected]> -------------------\ | He had a terrible memory. He remembered everything. | \------- (if (not (understand-this)) (go-to http://www.schemers.org)) --------/


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

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)