25 Jun
2018
25 Jun
'18
10:44 p.m.
Hi,
Christophe Lyon wrote,
It was weak in our
uClibc port.
I'm trying to understand it is no longer the case now that I rebased
the patches on top of uClibc-ng: is it a problem with uClib-ng or a
mistake of mine?
Maybe it is another change in your tree?
I checked for ARC and it looks like it isn't weak either.
best regards
Waldemar
What am I missing?
May be it is just not implemented as weak in uClibc-ng/uClibc. Is the ARM
FDPIC port targeting Linuxthreads or NPTL?
All existing FDPIC targets (Blackfin/FR-V) are using Linuxthreads.
We use NTPL:
> UCLIBC_HAS_THREADS_NATIVE=y
Is it a strict requirement for your test code to
overwrite write()?
That's part of a testsuite. I'm trying to understand
where the problem
is, in case it hides a major problem somewhere.
Maybe we could first import your port and test
static and shared
support and then trying to get write and may be other required
functions to be weak.
Sure. I thought it would be better to have a clean patch
series from
the beginning (well at least as clean as possible)
What does musl in this case?
I don't know.
Do you know if write (and friends) is weak on other ports of uClibc-ng?