From: Andre Naujoks <nautsch2@googlemail.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: gcc 4.5 and copy_flag in libubigen.c
Date: Tue, 15 Mar 2011 08:55:56 +0100 [thread overview]
Message-ID: <4D7F1B8C.2080303@googlemail.com> (raw)
In-Reply-To: <4D7E5601.6090905@parrot.com>
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.
The current version is the version I would stick to just because it
takes the maintenance of the package of of me. I would rather add a
little patch myself instead of handling the whole package.
I additionally have no idea about the implications an update of this
particular package would have. It just broke, because the gcc people
decided a new warning was a good idea.
Andre
>
>
> Matthieu
next prev parent reply other threads:[~2011-03-15 7:56 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 [this message]
2011-03-15 8:06 ` Artem Bityutskiy
2011-03-15 9:21 ` Andre Naujoks
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=4D7F1B8C.2080303@googlemail.com \
--to=nautsch2@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.