Flavio Cruz, on Sun 03 Jan 2016 01:35:55 +0100, wrote:
> On Sun, Jan 03, 2016 at 01:27:17AM +0100, Samuel Thibault wrote:
> > So you are making libc keep any heading slash, just dropping
> > double-heading-slash, right?
>
> Yes.
I'm wondering why keeping this heading slash, it seems unnecessary,
On Sun, Jan 03, 2016 at 01:27:17AM +0100, Samuel Thibault wrote:
> Hello,
>
> So you are making libc keep any heading slash, just dropping
> double-heading-slash, right?
Yes.
> Does that work with current translators?
It appears to work fine so far, but it might require more stress testing
to b
Hello,
So you are making libc keep any heading slash, just dropping
double-heading-slash, right? Does that work with current translators?
Otherwise the principle looks fine to me.
Samuel
Hello
I've played around with the code in order to fix the trailing slash
issue. When we do a file name lookup with a trailing '/' and the final
component is a translator, the '/' is not sent to the translator since
glibc strips the '/' before calling dir_lookup on the translator. This
patches fi
Applied, thanks!
This fixes a long list of undefined references when compiling with -O0
by using static instead of extern in header files.
---
diff --git a/pfinet/glue-include/linux/kernel.h
b/pfinet/glue-include/linux/kernel.h
index a0e101b..de5852f 100644
--- a/pfinet/glue-include/linux/kernel.h
+++ b/pfinet/