s6-0.17

s6-0.17

[Jorge Almeida]

Trying to compile against dietlibc:

Making subsystem pipe-tools...
make[1]: Entering directory `/package/admin/s6-0.17/compile/pipe-tools'
exec ./gen-EXPORT > EXPORT-
./gen-Makefile > Makefile.real && make -f Makefile.real && : > .done
make[2]: Entering directory `/package/admin/s6-0.17/compile/pipe-tools'
exec ./compile s6-cleanfifodir.c
exec ./load s6-cleanfifodir -lftrigw -lstddjb
exec ./compile s6-ftrig-listen.c
s6-ftrig-listen.c:15:22: fatal error: execline.h: No such file or directory
compilation terminated.
make[2]: *** [s6-ftrig-listen.o] Error 1
make[2]: Leaving directory `/package/admin/s6-0.17/compile/pipe-tools'
make[1]: *** [.done] Error 2
make[1]: Leaving directory `/package/admin/s6-0.17/compile/pipe-tools'
make: *** [.done] Error 2


s6-0.16 compiles without problems, same computer, same conf-compile
contents, same skalibs (1.2.8), and same execline (1.1.6).

TIA
-- 
Jorge Almeida

Re: s6-0.17

[Laurent Bercot]

> exec ./compile s6-ftrig-listen.c
> s6-ftrig-listen.c:15:22: fatal error: execline.h: No such file or directory
> compilation terminated.

 This is very strange. The differences between s6-0.16 and s6-0.17
absolutely do not touch this, you are the only one to report such a
problem, and I can't reproduce it.
 Can you triple-check your conf-compile subdirectory ?
 Can you triple-check the entire compilation log, especially
package/prepare, where the symlink to execline.h should be made ?

 Thank you,

-- 
 Laurent

Re: s6-0.17

[Jorge Almeida]

On Wed, 14 Nov 2012, Laurent Bercot wrote:

> > exec ./compile s6-ftrig-listen.c
> > s6-ftrig-listen.c:15:22: fatal error: execline.h: No such file or directory
> > compilation terminated.
> 
>  This is very strange. The differences between s6-0.16 and s6-0.17
> absolutely do not touch this, you are the only one to report such a
> problem, and I can't reproduce it.
>  Can you triple-check your conf-compile subdirectory ?
>  Can you triple-check the entire compilation log, especially
> package/prepare, where the symlink to execline.h should be made ?
> 


 package/prepare is identical in both cases (same md5sum, checked also
 with vimdiff). Contents of conf-compile follow. But where is the
 complete log?
 Note that I have conf-home set to the empty string (yes, I really need
 this!)

 Thanks

 Jorge


#  head -n 1 s6-0.16/conf-compile/*
==> s6-0.16/conf-compile/conf-cc <==
/opt/bin/diet gcc -O3 -march=native -W -Wall -Wextra -fomit-frame-pointer -pipe

==> s6-0.16/conf-compile/conf-dynld <==
gcc

==> s6-0.16/conf-compile/conf-home <==


==> s6-0.16/conf-compile/conf-ld <==
/opt/bin/diet gcc -s

==> s6-0.16/conf-compile/conf-stripbins <==
/command/superstrip1

==> s6-0.16/conf-compile/conf-striplibs <==
strip -x -R .note -R .comment -R .note.GNU-stack

==> s6-0.16/conf-compile/flag-allstatic <==

==> s6-0.16/conf-compile/import <==
$SP_ROOT/package/prog/skalibs/sysdeps

==> s6-0.16/conf-compile/path-include <==
$SP_ROOT/package/prog/skalibs/include

==> s6-0.16/conf-compile/path-library <==
$SP_ROOT/package/prog/skalibs/library

==> s6-0.16/conf-compile/path-library.so <==
$SP_ROOT/package/prog/skalibs/library.so


#  head -n 1 s6-0.17/conf-compile/*
==> s6-0.17/conf-compile/conf-cc <==
/opt/bin/diet gcc -O3 -march=native  -W -Wall -Wextra -fomit-frame-pointer -pipe

==> s6-0.17/conf-compile/conf-dynld <==
gcc

==> s6-0.17/conf-compile/conf-home <==


==> s6-0.17/conf-compile/conf-ld <==
/opt/bin/diet gcc -s

==> s6-0.17/conf-compile/conf-stripbins <==
/command/superstrip1

==> s6-0.17/conf-compile/conf-striplibs <==
strip -x -R .note -R .comment -R .note.GNU-stack

==> s6-0.17/conf-compile/flag-allstatic <==

==> s6-0.17/conf-compile/import <==
$SP_ROOT/package/prog/skalibs/sysdeps

==> s6-0.17/conf-compile/path-include <==
$SP_ROOT/package/prog/skalibs/include

==> s6-0.17/conf-compile/path-library <==
$SP_ROOT/package/prog/skalibs/library

==> s6-0.17/conf-compile/path-library.so <==
$SP_ROOT/package/prog/skalibs/library.so

Re: s6-0.17

[Laurent Bercot]

> ==> s6-0.17/conf-compile/import <==
> $SP_ROOT/package/prog/skalibs/sysdeps
> 
> ==> s6-0.17/conf-compile/path-include <==
> $SP_ROOT/package/prog/skalibs/include
> 
> ==> s6-0.17/conf-compile/path-library <==
> $SP_ROOT/package/prog/skalibs/library
> 
> ==> s6-0.17/conf-compile/path-library.so <==
> $SP_ROOT/package/prog/skalibs/library.so

 For some reason, your conf-compile/path-* files are lacking the paths
to the execline headers and libraries. I have no idea how your compilation
process manages to work with s6-0.16, but anyway, unless you modified those
conf-compile/ files yourself, something is wrong with your tarball.
 Grab a pristine tarball of s6-0.17 and try again.

-- 
 Laurent

Re: s6-0.17

[Jorge Almeida]

On Thu, 15 Nov 2012, Laurent Bercot wrote:

> 
>  For some reason, your conf-compile/path-* files are lacking the paths
> to the execline headers and libraries. I have no idea how your compilation
> process manages to work with s6-0.16, but anyway, unless you modified those
> conf-compile/ files yourself, something is wrong with your tarball.
>  Grab a pristine tarball of s6-0.17 and try again.
> 
Indeed, this was the problem. I can't imagine what happened. In a
related note, would you consider putting the md5sum (or whatever digest) of
the tarballs in the corresponding pages? It might be safer (although I
don't think this was the case).
Thanks, and sorry for the noise.
-- 
Jorge