From: Arend van Spriel <arend@broadcom.com>
To: Stefan Assmann <sassmann@kpanic.de>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>,
Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: ckmake build issue with undefined symbol mcount
Date: Thu, 10 Apr 2014 13:14:32 +0200 [thread overview]
Message-ID: <53467D18.4000100@broadcom.com> (raw)
In-Reply-To: <534649D8.6040208@kpanic.de>
On 04/10/14 09:35, Stefan Assmann wrote:
> On 08.04.2014 09:39, Stefan Assmann wrote:
>> On 08.04.2014 02:37, Luis R. Rodriguez wrote:
>>> On Mon, Apr 7, 2014 at 6:57 AM, Stefan Assmann<sassmann@kpanic.de> wrote:
>>>> next-20140221
>>>
>>> Did you git reset --hard backports-20140221 ? The respective dated tag
>>> for backports must be used for a specific dated tag for linux-next.
>>> Likewise for the stable releases.
>>>
>>> Luis
>>>
>>
>> My backports tree is at 8e946501aef6e3dd5bac12eb45d24df8248672b0 which
>> should be the same as backports-20140221.
>>
>> Stefan
>>
>
> I tried the same again in a newly installed VM and don't see any issues
> there. Probably an issue with my build env then. Please ignore.
It may related to the used gcc version. I recall a similar issue with
mcount when I had a kernel build with a different gcc than the driver
module.
Regards,
Arend
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe backports" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-04-10 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 13:57 ckmake build issue with undefined symbol mcount Stefan Assmann
2014-04-08 0:37 ` Luis R. Rodriguez
2014-04-08 7:39 ` Stefan Assmann
2014-04-10 7:35 ` Stefan Assmann
2014-04-10 11:14 ` Arend van Spriel [this message]
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=53467D18.4000100@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=mcgrof@do-not-panic.com \
--cc=sassmann@kpanic.de \
/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