Bug#672616: FTBFS: Binary files - and ./test/coretest.out differ

[Samuel Thibault]

Package: gforth
Version: 0.7.0+ds1-6
Severity: serious
Justification: FTBFS

Hello,

gforth currently FTBFS in sid:

./engine/gforth-noll --die-on-signal -p ".:/usr/lib/x86_64-linux-gnu/gforth/site-forth:/usr/share/gforth/site-forth:/usr/lib/x86_64-linux-gnu/gforth/0.7.0:/usr/share/gforth/0.7.0:." test/tester.fs test/coretest.fs test/postpone.fs test/dbltest.fs test/string.fs test/float.fs test/deferred.fs test/coreext.fs test/search.fs -e bye 2>&1 | tr -d '\015' | diff -c - ./test/coretest.out
Binary files - and ./test/coretest.out differ

Samuel

-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--
Samuel Thibault <samuel....@fnac.net>
<s> bah, j'aime bien les feux d'artifices, mais j'ai peur de me prendre un boeing sur le coin de la gueule si je vais sur le pont de brooklyn
-+- #ens-mim - 11 septembre forever -+-



--
To UNSUBSCRIBE, email to debian-bugs...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Anton Ertl]

On Tue, May 22, 2012 at 05:23:50PM +0200, gregor herrmann wrote:
> On Sat, 12 May 2012 16:50:18 +0200, Anton Ertl wrote:
> > This may be due to a bug in Gforth uncovered by gcc-4.7. The fix is:
> >
> > http://www.complang.tuwien.ac.at/viewcvs/cgi-bin/viewcvs.cgi/gforth/prim?sortby=date&r2=1.271&r1=1.270
>
> With the patch it fails later; log attached.

Your log shows a much earlier failure (before the engine is even
compiled).

What it shows is that it is actually trying to bootstrap itself, which
needs an installed Gforth; not sure if you have that in the
dependencies (if you don't have that, that may be the cause of the
failure). That's certainly not necessary for the GNU .tar.gz package
we distribute, which contains all the generated files that are
generated in bootstrapping.

> GFORTH="./preforth -p ".:~+:."" ./gfgen

This step requires either an already-installed Gforth or it must be
performed only after the engine is built.

My guess is that the way you patch it makes prim newer than prim.i, so
it wants to build prim.i, and for that step a running Gforth engine is
needed.

The options you have are

1) Require an installed gforth for building gforth.

2) Patch prim.b and engine/prim.i as well, and make sure that prim.b
is not older than prim and engine/prim.i is not older than prim.b.

- anton

[Matthias Klose]

building (the unpatched package) explicitly using gcc-4.6 on amd64, I get the
following build failure. Looks like there is at least something unrelated to
GCC 4.7 (see the second log).

with the suggested patch, I get:

[...]
(cd . && m4 -s -Dcondbranch_opt=0 prim) >prim.b
sleep 1 #should make hpux-workaround unnecessary

GFORTH="./preforth -p ".:~+:."" ./gfgen

make[1]: *** [engine/prim.i] Error 1
make[1]: Leaving directory `/home/packages/tmp/gforth-0.7.0+ds1'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2

so it looks like the patch isn't correctly applied, or some other files need to
be regenerated?

[...]
for i in libffi.fs fflib.fs cstr.fs unix/socket.fs; do ./gforth -e "s\"
`pwd`/lib/gforth/0.7.0/libcc-named/\" libcc-named-dir-v 2! libcc-path clear-path
libcc-named-dir libcc-path also-path :noname 2drop s\"
/usr/lib/x86_64-linux-gnu/gforth/0.7.0/libcc-named/\" ; is replace-rpath" ./$i
-e bye; done
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'

in file included from *OS command line*:-1
libffi.fs:159: libtool compile failed
>>>end-c-library<<<
Backtrace:
$2ADD7A60F988 throw
$2ADD7A64B4D0 c(abort")
$2ADD7A64C0D0 compile-wrapper-function1
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'

in file included from *OS command line*:-1
fflib.fs:136: libtool compile failed
>>>end-c-library<<<
Backtrace:
$2AF9947C7988 throw
$2AF9948034D0 c(abort")
$2AF9948040D0 compile-wrapper-function1
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'

in file included from *OS command line*:-1
cstr.fs:23: libtool compile failed
>>>end-c-library<<<
Backtrace:
$2B6B7E085988 throw
$2B6B7E0C14D0 c(abort")
$2B6B7E0C20D0 compile-wrapper-function1
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'

in file included from *OS command line*:-1
unix/socket.fs:48: libtool compile failed
>>>end-c-library<<<
Backtrace:
$2ACA46213988 throw
$2ACA4624F4D0 c(abort")
$2ACA462500D0 compile-wrapper-function1
make[1]: *** [build-libcc-named] Error 1
make[1]: Leaving directory `/home/packages/tmp/gforth-0.7.0+ds1'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

[Debian Bug Tracking System]

Your message dated Tue, 11 Sep 2012 17:17:54 +0000
with message-id <E1TBU5y-...@franck.debian.org>
and subject line Bug#672616: fixed in gforth 0.7.0+ds1-7
has caused the Debian Bug report #672616,
regarding FTBFS: Binary files - and ./test/coretest.out differ
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 ow...@bugs.debian.org
immediately.)


--
672616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems