public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Andre Naujoks <nautsch2@googlemail.com>
To: dedekind1@gmail.com
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Matthieu CASTET <matthieu.castet@parrot.com>
Subject: Re: gcc 4.5 and copy_flag in libubigen.c
Date: Tue, 15 Mar 2011 10:21:18 +0100	[thread overview]
Message-ID: <4D7F2F8E.10608@googlemail.com> (raw)
In-Reply-To: <1300176400.2740.2.camel@localhost>

Am 15.03.2011 09:06, schrieb Artem Bityutskiy:
> On Tue, 2011-03-15 at 08:55 +0100, Andre Naujoks wrote:
>> Am 14.03.2011 18:53, schrieb Matthieu CASTET:
>>> Andre Naujoks a écrit :
>>>> Hi all.
>>>>
>>>> I am compiling a board support package with mtd-utils-1.3.1.
>>>>
>>> Why don't you update your mtd-utils version ?
>>
>> Because it would be more of a hassle and a risk to do that. There are
>> patches applied that were build from the suppliers of the BSP, which I
>> would have to possibly reproduce for a newer version. As far as I can
>> see, they are all patches to the build system, but nevertheless.
> 
> Well, you can use 1.3.1, but do not use old UBI utils, use the new ones,
> i.e., use ubi-utils/src/libubigen.c, not
> ubi-utils/old-utils/src/libubigen.c
> 

Thank You. That helped a lot. I just removed SUBDIRS from the Makefile
in ubi-utils. It seems as if those were not used at all from the beginning.

Sorry for the noise for something that old I did not even use :-)

Thanks for the help
  Andre

  reply	other threads:[~2011-03-15  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 16:37 gcc 4.5 and copy_flag in libubigen.c Andre Naujoks
2011-03-14 17:53 ` Matthieu CASTET
2011-03-15  7:55   ` Andre Naujoks
2011-03-15  8:06     ` Artem Bityutskiy
2011-03-15  9:21       ` Andre Naujoks [this message]
2011-03-15  8:04 ` Artem Bityutskiy
2011-03-15  8:45 ` Ricard Wanderlof
2011-03-15  9:29   ` Andre Naujoks

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=4D7F2F8E.10608@googlemail.com \
    --to=nautsch2@googlemail.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matthieu.castet@parrot.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