Hi all,
In using ftw/nftw, I've discovered a bug when using FTW_CHDIR and FTW_DEPTH.
After changing the working directory to a subdirectory, nftw would process the
contents fine. However, it would then try and process the directory itself
while still in that directory and then switch back to
On 10/17/2016 14:54, Waldemar Brodkorb wrote:
> Hi Joshua,
[snip]
>
> You don't like cross-compiling, right?
> uClibc-ng seems not only be interesting for embedded devices, but
> also for classic old unix hardware :)
>
Oh, I cross-compile all the time. All of my SGI kernels are built with
cr
Hi Ignacy,
Ignacy Gawędzki wrote,
> On Sun, Oct 16, 2016 at 10:01:30PM +0200, thus spake Waldemar Brodkorb:
> > > As I said, I used d4d4f37 and not strictly origin/master. But I
> > > otherwise used the command line you gave me, including --libc-source.
> >
> > But 17ad14e5780533db90171e16b95dbe
Hi Joshua,
Joshua Kinard wrote,
> On 10/16/2016 17:45, Waldemar Brodkorb wrote:
> [snip]
>
> >
> > I have 2xO2 and 2xIndy.
> >
> > The modern O2:
> >> hinv
> >System: IP32
> > Processor: 300 Mhz R5000, with FPU
> > Primary I-cache size: 32 Kbytes
> >
Hi Hackers,
I had a nice talk about uClibc-ng with Alexey on ELCE2016.
One of the points where the separation of the test suite included in
uClibc-ng source tree.
Recently Max and I discovered a problem regarding
libgcc/pthread_cancel, because the code was _not_ compiled with
the normal full shar
On Mon, Oct 17, 2016 at 03:40:04PM +0200, thus spake Ignacy Gawedzki:
> On Sun, Oct 16, 2016 at 10:01:30PM +0200, thus spake Waldemar Brodkorb:
> > > As I said, I used d4d4f37 and not strictly origin/master. But I
> > > otherwise used the command line you gave me, including --libc-source.
> >
> >
On Sun, Oct 16, 2016 at 10:01:30PM +0200, thus spake Waldemar Brodkorb:
> > As I said, I used d4d4f37 and not strictly origin/master. But I
> > otherwise used the command line you gave me, including --libc-source.
>
> But 17ad14e5780533db90171e16b95dbeda4e81ffb0 contains a workaround
> for exactl