On Tuesday, June 19, 2012 11:16:07 PM UTC+8, Jeroen Demeyer wrote:
>
> On 2012-06-19 15:48, Gonzalo Tornaria wrote:
> > The two issues are related with using "time" with a pipeline, assuming
> > it is the builtin time, but in fact is not (I've no idea why).
>
> This seems to be a known Mandriv
On 2012-06-19 15:48, Gonzalo Tornaria wrote:
> The two issues are related with using "time" with a pipeline, assuming
> it is the builtin time, but in fact is not (I've no idea why).
This seems to be a known Mandriva bug:
https://qa.mandriva.com/show_bug.cgi?id=20894
--
To post to this group, s
What does
$ bash -c 'type time'
say?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sag
On 2012-06-19 15:48, Gonzalo Tornaria wrote:
> I want to report two issues in the bash scripts (sage 5.0.1) which
> break the build of sage under certain situations. This actually
> happens in the computers at ICTP.
>
> The two issues are related with using "time" with a pipeline, assuming
> it is
I want to report two issues in the bash scripts (sage 5.0.1) which
break the build of sage under certain situations. This actually
happens in the computers at ICTP.
The two issues are related with using "time" with a pipeline, assuming
it is the builtin time, but in fact is not (I've no idea why).
