public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Richard Weinberger <richard@nod.at>, Guan Xuetao <gxt@mprc.pku.edu.cn>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] unicore32: Fix build error
Date: Sun, 10 Aug 2014 09:30:14 -0700	[thread overview]
Message-ID: <53E79E16.7040603@roeck-us.net> (raw)
In-Reply-To: <53E7923F.5000008@nod.at>

On 08/10/2014 08:39 AM, Richard Weinberger wrote:
> Guenther,
>
> Am 10.08.2014 17:29, schrieb Guenter Roeck:
>> unicore32 builds fail with
>>
>> arch/unicore32/kernel/signal.c: In function ‘setup_frame’:
>> arch/unicore32/kernel/signal.c:257: error:
>> 			‘usig’ undeclared (first use in this function)
>> arch/unicore32/kernel/signal.c:279: error:
>> 			‘usig’ undeclared (first use in this function)
>> arch/unicore32/kernel/signal.c: In function ‘handle_signal’:
>> arch/unicore32/kernel/signal.c:306: warning: unused variable ‘tsk’
>> arch/unicore32/kernel/signal.c: In function ‘do_signal’:
>> arch/unicore32/kernel/signal.c:376: error:
>> 			implicit declaration of function ‘get_signsl’
>> make[1]: *** [arch/unicore32/kernel/signal.o] Error 1
>> make: *** [arch/unicore32/kernel/signal.o] Error 2
>>
>> Bisect points to commit 649671c90eaf ("unicore32: Use get_signal()
>> signal_setup_done()").
>>
>> This code never even compiled. Reverting the patch does not work,
>> since previously used functions no longer exist, so try to fix it up.
>> Compile tested only.
>
> Where did you get the unicore32 cross compiler from?
>
mprc.pku.edu.cn/~guanxuetao/linux/uc4-1.0.5-hard.tgz

Guenter


  reply	other threads:[~2014-08-10 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 15:29 [PATCH] unicore32: Fix build error Guenter Roeck
2014-08-10 15:39 ` Richard Weinberger
2014-08-10 16:30   ` Guenter Roeck [this message]
2014-08-11  5:04     ` 回复: " Xuetao Guan 
2014-08-15 19:38 ` Guenter Roeck
2014-08-16  0:45   ` 回复: " Xuetao Guan 
2014-08-16  2:21     ` Guenter Roeck
2014-08-18  0:26       ` 回复: " Xuetao Guan 

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=53E79E16.7040603@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    /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