mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thorsten Glaser <tg@mirbsd.de>
To: linux-kernel@vger.kernel.org
Cc: 648996@bugs.debian.org
Subject: Re: Bug#648996: linux-2.6: FTBFS [m68k] in modpost: "strlen" [iscsi_target_mod.ko] undefined! (and others)
Date: Sun, 1 Jan 2012 23:12:00 +0000 (UTC)	[thread overview]
Message-ID: <Pine.BSM.4.64L.1201012310590.20109@herc.mirbsd.org> (raw)
In-Reply-To: <Pine.BSM.4.64L.1112181929380.856@herc.mirbsd.org>

Dixi quod…

>So, please, compile the Linux kernel with -ffreestanding, too.

Just to keep this bugreport in the loop: that fixes the FTBFS error.
http://lists.debian.org/debian-68k/2012/01/msg00000.html

bye,
//mirabilos
-- 
<dileks> ch: good, you corrected yourself. ppl tend to tweet such news
immediately, sth. like "grml devs seem to be buyable"    <ch> dileks: we
_are_. if you throw enough money in our direction, things will happen
<mika> everyone is buyable, it's just a matter of price   <mrud> and now
comes [mira] and uses this as a signature ;0	   -- they asked for it…

  reply	other threads:[~2012-01-01 23:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111116181424.14920.7730.reportbug@ara5.mirbsd.org>
     [not found] ` <Pine.BSM.4.64L.1111301751500.12725@herc.mirbsd.org>
     [not found]   ` <CAMuHMdW8t8Q7OqxJM602iLG4aSv1KMTY-fhiGS7hyy8xBReh1A@mail.gmail.com>
     [not found]     ` <Pine.BSM.4.64L.1112181741430.856@herc.mirbsd.org>
2011-12-18 19:33       ` Thorsten Glaser
2012-01-01 23:12         ` Thorsten Glaser [this message]
2012-01-01 23:39           ` Jonathan Nieder
2012-01-01 23:45             ` Thorsten Glaser
2012-01-02  0:10               ` Jonathan Nieder
2012-01-02  0:19                 ` Thorsten Glaser

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=Pine.BSM.4.64L.1201012310590.20109@herc.mirbsd.org \
    --to=tg@mirbsd.de \
    --cc=648996@bugs.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®