From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Vinson Lee <vlee@twitter.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] ltp_signal.h: Remove inline keyword from handler_h.
Date: Tue, 07 Aug 2012 09:09:09 +0800 [thread overview]
Message-ID: <50206AB5.7040701@cn.fujitsu.com> (raw)
In-Reply-To: <CAKixpbjzpzLBLuUL3rf=9ujuPC7s89DmBLehfEmHoEk4iAjjsA@mail.gmail.com>
On 08/07/2012 12:55 AM, Vinson Lee wrote:
> On Sun, Aug 5, 2012 at 6:42 PM, Wanlong Gao <gaowanlong@cn.fujitsu.com> wrote:
>> On 08/04/2012 06:29 AM, Vinson Lee wrote:
>>> This patch fixes this build error with clang.
>>>
>>> testcases/kernel/syscalls/rt_sigaction/../../../../include/ltp_signal.h:85: undefined reference to `handler_h'
>>
>> If you wanna build LTP with LLVM, why not make out "a path for LLVM building" and send
>> out it. I think this one line change can't do everything for LLVM building, although
>> untested. right?
>>
>> Thanks,
>> Wanlong Gao
>>
>
> This was the only build error with I saw with clang. This one change
> fixes the build with clang.
>
> It's a C99 error which would probably occur with gcc -std=c99 as well.
> http://clang.llvm.org/compatibility.html#inline
I saw that "Change add to a static inline function.
This is usually the right solution if only one translation
unit needs to use the function. static inline functions are
always resolved within the translation unit, so you won't have
to add a non-inline definition of the function elsewhere in your program."
So, why not just change it to "static inline" to resolve this?
Thanks,
Wanlong Gao
>
>
>>>
>>> Signed-off-by: Vinson Lee <vlee@twitter.com>
>>> ---
>>> include/ltp_signal.h | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/include/ltp_signal.h b/include/ltp_signal.h
>>> index 1ac6f70..093059f 100644
>>> --- a/include/ltp_signal.h
>>> +++ b/include/ltp_signal.h
>>> @@ -69,7 +69,7 @@ struct kernel_sigaction {
>>>
>>> void (*restore_rt) (void);
>>>
>>> -inline void
>>> +void
>>> handler_h (int signal)
>>> {
>>> return;
>>>
>>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-08-07 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 22:29 [LTP] [PATCH] ltp_signal.h: Remove inline keyword from handler_h Vinson Lee
2012-08-06 1:42 ` Wanlong Gao
2012-08-06 16:55 ` Vinson Lee
2012-08-07 1:09 ` Wanlong Gao [this message]
2012-10-04 13:00 ` chrubis
2012-10-04 13:02 ` chrubis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50206AB5.7040701@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vlee@twitter.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox