This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/21232] miss posix_fadvise64 on MIPS64 when static linking
- From: "ma.jiang at zte dot com.cn" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 14 Mar 2017 21:22:37 +0000
- Subject: [Bug libc/21232] miss posix_fadvise64 on MIPS64 when static linking
- Auto-submitted: auto-generated
- References: <bug-21232-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21232
--- Comment #5 from ma.jiang at zte dot com.cn ---
(In reply to Adhemerval Zanella from comment #4)
> The strong alias adds linkspace issues showed by conform testcases (since
> posix_fadvise64 is a glibc name convention). My understanding is it correct
> approach is to use a weak_alias instead (as previous implementation). I
> will prepare and send a patch.
Hi,
Thanks for your reply. I agree with your suggestion. And , your message
remind me to rethink about these weak_lias things carefully. I have rechecked
some functions similar to posix_fadvise64. Unfortunately, I still can not find
a very clear rule for there things. In my opinion, all open functional
interfaces in libc.a should be weak. Of course,this is not true for current
glibc. In fact, some functions in posix-standard are still strong symbols(for
example, fstatat). So, What is the right rule?
--
You are receiving this mail because:
You are on the CC list for the bug.