Somehow I never got around to reporting this before... Please don't use &> in configure scripts. It breaks horribly with dash as my CONFIG_SHELL, which runs $CC in the background to standard output/error, and creates libctest.log as an empty file. --- sandbox-1.2.18.1/configure.ac +++ sandbox-1.2.18.1/configure.ac @@ -131 +131 @@ -$CC $CFLAGS -Wl,-verbose -o libctest libctest.c &> libctest.log +$CC $CFLAGS -Wl,-verbose -o libctest libctest.c >libctest.log 2>&1
this was fixed in svn a while ago. if you really care about 1.2.18.1, feel free to commit a patch to the package itself.
I don't care about 1.2.18.1 in particular, but it isn't fixed in the alphas either. I'd be happy to modify the sandbox ebuild to fix up the configure script, but it requires a modification to configure.ac, which requires either eautoreconf or direct modification of the generated configure script. I don't know if the former would cause any problems (sandbox being a system package and all, quite possibly installed before autotools are), and while I have no problems with the latter, I know at least one rather vocal dev has strong objections to that... Any insights here?
i was referring to the svn repo, not any particular version in the tree a simple sed on the configure script would fix things up i imagine ... feel free to commit to the tree
Alrighty, done.
looks good, thanks
