Re: autogen.sh error on no warnings

Well, in fact, testing for presence of warn in a way I suggested won't
work, so either ||true should be used, or exit 0 at the end

On Fri, Aug 24, 2012 at 6:02 PM, Ruslan Kabatsayev
<b7.10110111@gmail.com> wrote:
> Hi Norbert,
>
> Your fix is not solving all the problem: now autogen fails without
> indication why. See the message:
>
> > If you want to run the smoketest, issue:
> > make check
> >
> > Error running configure at ./autogen.sh line 187.
> This is because you redirect error to /dev/null, but don't prevent cat
> error status. So this is better to be fixed either by first checking
> presence of warn ("[ -e warn ] && cat warn"), or adding "|| true" to
> "cat warn 2>/dev/null"
>
> Regards,
> Ruslan
>
>
> On Fri, Aug 24, 2012 at 5:46 PM, Norbert Thiebaud <nthiebaud@gmail.com> wrote:
> > On Fri, Aug 24, 2012 at 7:34 AM, Ruslan Kabatsayev
> > <b7.10110111@gmail.com> wrote:
> > > Hello,
> > >
> > > When I have no warnings from configure script, I get an error from
> > > "cat warn" line saying "No such file or directory". I guess "cat warn"
> > > should be changed to something like "[ -e warn ] && cat warn", or warn
> > > should be created at the beginning of configure.
> > > CCing Norbert Thiebaud as git-blame says the corresponding line in
> > > configure.in was last added in commit
> > > 65335b13da74f4f350ba52493b0919a62d1a5bca.
> >
> > Thanks for the cc:, fixed.
> >
> > Norbert