On Sun, Nov 18, 2012 at 02:05:43AM +0100, Jim Meyering wrote:
> Dmitry V. Levin wrote:
> > This gives clients the option to disable stripping of trailing slashes
> > from input path names during fts_open initialization.
> >
> > The recent change v0.0-7611-g3a9002d that made fts_open strip trailing
Dmitry V. Levin wrote:
> This gives clients the option to disable stripping of trailing slashes
> from input path names during fts_open initialization.
>
> The recent change v0.0-7611-g3a9002d that made fts_open strip trailing
> slashes from input path names had a negative impact on findutils that
This gives clients the option to disable stripping of trailing slashes
from input path names during fts_open initialization.
The recent change v0.0-7611-g3a9002d that made fts_open strip trailing
slashes from input path names had a negative impact on findutils that
relies on the old fts_open behav
On Sat, Nov 17, 2012 at 4:07 PM, Paul Eggert wrote:
> I'd try compiling with gcc -Wall. Most likely
> you have a prototype missing. malloc is builtin
> to the compiler but xmalloc is not.
Thank you Paul,
You had exactly correct hunch, my compiler flags did not have proper
include directory def
I'd try compiling with gcc -Wall. Most likely
you have a prototype missing. malloc is builtin
to the compiler but xmalloc is not.
Hello,
While adding a gnulib (git describe v0.0-7694-g0dc4348) to a project I
noticed that one of the commands did not work after malloc() calls
where replaced with xmalloc(). After a bit of debugging I were able to
write a small program which demonstrates what went wrong.
-- snip
#include "confi