Sorry for that... Gmail must have added it for some reason. From my side, I
cannot see it.
On 22 October 2015 at 23:01, Daniel Gimpelevich <
dan...@gimpelevich.san-francisco.ca.us> wrote:
> On Thu, 2015-10-22 at 22:50 +0100, Carlos Ferreira wrote:
> > Yes :S Sorry!
> > Btw, Caps lock day? Did my
On Thu, 2015-10-22 at 22:50 +0100, Carlos Ferreira wrote:
> Yes :S Sorry!
> Btw, Caps lock day? Did my Gmail applied some weird format again ? :S
HTML.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailm
Yes :S Sorry!
Btw, Caps lock day? Did my Gmail applied some weird format again ? :S
On 22 October 2015 at 22:46, Daniel Gimpelevich <
dan...@gimpelevich.san-francisco.ca.us> wrote:
> On Thu, 2015-10-22 at 22:30 +0100, Carlos Ferreira wrote:
> > Daniel
> > Your patch did not work without some sim
On Thu, 2015-10-22 at 22:30 +0100, Carlos Ferreira wrote:
> Daniel
> Your patch did not work without some simple modifications.
>
This puzzled me until I realized you meant the other Daniel.
PS: HAPPY INTERNATIONAL CAPS LOCK DAY!
___
openwrt-devel maili
Ok... this is going to be impossible. The problem is not only in procd but
in other system programs.
For example, rpcd is showing the same problems. See bellow.
PS: I added Jo-Philipp to CC
make[1]: Entering directory '/home/ArkHDD/OpenWRT/15.05'
make[2]: Entering directory
'/home/ArkHDD/OpenWRT/1
Daniel
Your patch did not work without some simple modifications.
Instead of having
*inline __attribute__((always_inline)) int ignore(int x) {return x;}*
at procd.h, I had to add a
*static inline __attribute__((always_inline)) int ignore(int x) {return x;}*
at the begining of both coldplug.c and
On Thu, 2015-10-22 at 17:54 +0200, Felix Fietkau wrote:
> On 2015-10-21 01:34, Daniel Golle wrote:
> > Hi!
> >
> > This has been an argument going on between the gcc and the glibc people
> > for about 10 years now.
> > See
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25509
> >
> > It seems li
On 2015-10-21 01:34, Daniel Golle wrote:
> Hi!
>
> This has been an argument going on between the gcc and the glibc people
> for about 10 years now.
> See
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25509
>
> It seems like commit b6618ffa which added the symlinks silently broke
> things when b
Hi!
This has been an argument going on between the gcc and the glibc people
for about 10 years now.
See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25509
It seems like commit b6618ffa which added the symlinks silently broke
things when building with glibc.
Don't ask me why glibc enabled warn_unu