From: Jorge Almeida <jalmeida@math.ist.utl.pt>
To: Laurent Bercot <ska-supervision@skarnet.org>
Cc: supervision@list.skarnet.org
Subject: Re: s6-0.17
Date: Thu, 15 Nov 2012 10:09:30 +0000 (WET) [thread overview]
Message-ID: <alpine.DEB.2.00.1211150958270.16312@amber.math.ist.utl.pt> (raw)
In-Reply-To: <20121114223350.GA19045@skarnet.org>
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
next prev parent reply other threads:[~2012-11-15 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 19:01 s6-0.17 Jorge Almeida
2012-11-14 22:33 ` s6-0.17 Laurent Bercot
2012-11-15 10:09 ` Jorge Almeida [this message]
2012-11-15 12:13 ` s6-0.17 Laurent Bercot
2012-11-15 18:42 ` s6-0.17 Jorge Almeida
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1211150958270.16312@amber.math.ist.utl.pt \
--to=jalmeida@math.ist.utl.pt \
--cc=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).