Re: make check when cross compiling

[John Darrington]

In principle, sack *could* run on either side.  But we have arranged for it to
be built on the host side, so when building for windows, it'll have to be run
under wine.

I suppose we could change the build setup so that it builds with CC_FOR_BUILD 
but
then everything upon which it depends would have to be rebuilt too.

My opinion is that it is probably better to leave it host side.  

I expect there will also need to be certain other measures necessary to let the 
testsuite run properly under wine ...

J'

On Wed, Mar 09, 2016 at 10:34:26PM +0100, Harry Thijssen wrote:
     Hi
     
     Bash can't run the generated sack.exe even when I rename it to sack. But
     wine knows how to handel sack.exe, even if I rename it to sack. So I guess
     sack.exe is indeed a MSWindows exe file. If I understand Ben will this
     shouldn't be the case?
     
     Have fun
     
     2016-03-09 18:28 GMT+01:00 John Darrington <address@hidden>:
     
     > In general I think you are right.  If we append $(EXEEXE) onto the names
     > of many
     > of the binaries in the .at files, it will fix some, but not all of the
     > problems
     > relating to running the tests in wine.
     >
     > J'
     >
     > On Wed, Mar 09, 2016 at 06:25:10PM +0100, Harry Thijssen wrote:
     >      Ok
     >
     >      Then the problem might be that the file in tests/data is sack.exe 
and
     > not
     >      sack.  Also I have seen errors for pspp which I guess should be
     > pspp.exe.
     >
     >      Might there be a problem?
     >
     >      Have fun
     >
     >
     >
     >
     >
     >      2016-03-09 18:11 GMT+01:00 Ben Pfaff <address@hidden>:
     >
     >      > On Wed, Mar 09, 2016 at 01:57:49PM +0100, Harry Thijssen wrote:
     >      > > Hi
     >      > >
     >      > > I had a look to find out why all tests fail when cross 
compiling.
     >      > >
     >      > > If I look at atconfig.in I see:
     >      > >
     >      > > # -*- shell-script -*-
     >      > >
     >      > > # Variables used internally by the testsuite.
     >      > > EXEEXT='.exe'
     >      > > GNM_READ_SUPPORT='yes'
     >      > > ODF_READ_SUPPORT='yes'
     >      > > .....
     >      > >
     >      > >
     >      > > if I look in the logfiles from the tests I see:
     >      > >
     >      > > #                             -*- compilation -*-
     >      > > 93. sys-file-reader.at:1908: testing missing string continuation
     > record
     >      > ...
     >      > > ./sys-file-reader.at:1926: sack --$variant sys-file.sack >
     > sys-file.sav
     >      > > --- /dev/null    2016-03-08 20:27:55.663840673 +0100
     >      > > +++
     >      > >
     >      >
     > 
/home/harry/pspp-master-20160308/pspp-0.9.0-gc50266/tests/testsuite.dir/at-groups/93/stderr
     >      > > 2016-03-08 22:01:34.369722134 +0100
     >      > > @@ -0,0 +1 @@
     >      > >
     >      >
     > 
+/home/harry/pspp-master-20160308/pspp-0.9.0-gc50266/tests/testsuite.dir/at-groups/93/test-source:
     >      > > line 25: sack: command not found
     >      > > ./sys-file-reader.at:1926: exit code was 127, expected 0
     >      > > 93. sys-file-reader.at:1908: 93. missing string continuation
     > record (
     >      > > sys-file-reader.at:1908): FAILED (sys-file-reader.at:1926)
     >      > >
     >      > > Shouldn't it be sack.exe instead of sack?
     >      >
     >      > No, sack runs on the machine where the build occurs, not on the
     > machine
     >      > that the build targets.  In other words, sack is a build tool.
     >      >
     >
     >      _______________________________________________
     >      pspp-dev mailing list
     >      address@hidden
     >      https://lists.gnu.org/mailman/listinfo/pspp-dev
     >
     >
     > --
     > Avoid eavesdropping.  Send strong encryted email.
     > PGP Public key ID: 1024D/2DE827B3
     > fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
     > See http://sks-keyservers.net or any PGP keyserver for public key.
     >
     >

-- 
Avoid eavesdropping.  Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.

signature.asc
Description: Digital signature