[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#744574: marked as done (gcc-4.6: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4)



Your message dated Sun, 13 Apr 2014 19:45:53 +0200
with message-id <534ACD51.2080202@debian.org>
and subject line Re: Bug#744574: gcc-4.6: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4
has caused the Debian Bug report #744574,
regarding gcc-4.6: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
744574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744574
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-4.6
Version: 4.6.4-6
User: debian-devel@lists.debian.org
Usertags: autoreconf

The package fails to build on ppc64el (powerpc64le-linux-gnu), because
the config.{guess,sub} files are out of date, and are not updated during
the build.  If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.

  - For dh, call dh --with autoreconf.

  - For cdbs based build systems, include
    /usr/share/cdbs/1/rules/autoreconf.mk

  - For other rules files, call dh_autoreconf before calling
    configure (in the build or configure target), and call
    dh_autoreconf_clean before dh_clean in the clean target.

For combining autoreconf and autotools_dev, see bug #698765.

After the build on any architecture, and before a clean, a grep for
powerpc64le in the configure, aclocal.m4 and/or libtool.m4 file(s)
should print some lines. It is not enough to just update the
config.guess and config.sub files.

The full build log can be found at:
http://people.debian.org/~doko/logs/ppc64el-20140414/buildlog_ubuntu-trusty-ppc64el.gcc-4.6_4.6.4-6ubuntu1_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.

Please note that these builds were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.

See https://wiki.debian.org/qa.debian.org/FTBFS for a guide how to
address these.

[...]
checking whether errno is declared... yes
checking whether snprintf is declared... yes
checking whether vsnprintf is declared... yes
checking whether vasprintf is declared... yes
checking whether malloc is declared... yes
checking whether realloc is declared... yes
checking whether calloc is declared... yes
checking whether free is declared... yes
checking whether basename is declared... yes
checking whether getopt is declared... no
checking whether clock is declared... yes
checking whether getpagesize is declared... yes
checking whether clearerr_unlocked is declared... yes
checking whether feof_unlocked is declared... yes
checking whether ferror_unlocked is declared... yes
checking whether fflush_unlocked is declared... yes
checking whether fgetc_unlocked is declared... yes
checking whether fgets_unlocked is declared... yes
checking whether fileno_unlocked is declared... yes
checking whether fprintf_unlocked is declared... no
checking whether fputc_unlocked is declared... yes
checking whether fputs_unlocked is declared... yes
checking whether fread_unlocked is declared... yes
checking whether fwrite_unlocked is declared... yes
checking whether getchar_unlocked is declared... yes
checking whether getc_unlocked is declared... yes
checking whether putchar_unlocked is declared... yes
checking whether putc_unlocked is declared... yes
checking whether getrlimit is declared... yes
checking whether setrlimit is declared... yes
checking whether getrusage is declared... yes
checking whether ldgetname is declared... no
checking whether times is declared... yes
checking whether sigaltstack is declared... yes
checking for struct tms... yes
checking for clock_t... yes
checking for .preinit_array/.init_array/.fini_array support... yes
checking if mkdir takes one argument... no
*** Configuration powerpc64le-unknown-linux-gnu not supported
make[4]: *** [configure-stage1-gcc] Error 1
make[4]: Leaving directory `/build/buildd/gcc-4.6-4.6.4/build'
make[3]: *** [stage1-bubble] Error 2
make[3]: Leaving directory `/build/buildd/gcc-4.6-4.6.4/build'
make[2]: *** [bootstrap-lean] Error 2
make[2]: Leaving directory `/build/buildd/gcc-4.6-4.6.4/build'
s=`cat status`; rm -f status; test $s -eq 0
make[1]: *** [stamps/05-build-stamp] Error 1
make[1]: Leaving directory `/build/buildd/gcc-4.6-4.6.4'
make: *** [stamps/05-build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

--- End Message ---
--- Begin Message ---
invalid, GCC 4.6 doesn't build on this architecture

--- End Message ---

Reply to: