On domingo, 5 de fevereiro de 2017 12:53:38 PST Cristian Ionescu-Idbohrn
wrote:
> + _ldconfig=$(PATH=/usr/local/sbin:/usr/sbin:/sbin:$PATH command -v
> ldconfig) || { + echo "can't find ldconfig" >&2
> + exit 1
> + }
> + LIBGIT=$($_ldconfig -p | grep l
On Sun, 5 Feb 2017, Robert Helling wrote:
> > On 05 Feb 2017, at 15:21, Cristian Ionescu-Idbohrn
> > wrote:
> >
> > I have an idea ;)
> >
> > Why not error handle those the code that produces those "warnings" (as
> > you call them) on that particular architecture, instead of
> > ignoring/hiding
Hi,
> On 05 Feb 2017, at 15:21, Cristian Ionescu-Idbohrn
> wrote:
>
> I have an idea ;)
>
> Why not error handle those the code that produces those "warnings" (as
> you call them) on that particular architecture, instead of
> ignoring/hiding the errors (exit status failure) for everyone? That
On Sun, 5 Feb 2017, Robert C. Helling wrote:
> > Am 05.02.2017 um 12:53 schrieb Cristian Ionescu-Idbohrn
> > :
> >
> > That's the reason shell option '-e' (errexit) was introduced.
>
> That option had been introduced before and then later been removed
> again. The build on mac throws warnings a
Hi,
> Am 05.02.2017 um 12:53 schrieb Cristian Ionescu-Idbohrn
> :
>
> That's the reason shell option
> '-e' (errexit) was introduced.
That option had been introduced before and then later been removed again. The
build on mac throws warnings about certain Qt things that one should do (but
whic
The unhandled error was:
./subsurface/scripts/build.sh: line 84: ldconfig: command not found
On my box, the path is /sbin/ldconfig, and /sbin is not in common users'
PATH.
The script just continued to execute after that error, which can result
in other odd bugs showing up later. That's