From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Fixing linux-pam build failures
Date: Sat, 08 Sep 2012 17:40:35 +0300 [thread overview]
Message-ID: <504B58E3.3070901@petroprogram.com> (raw)
In-Reply-To: <CADiAo4KAOhh3DDxn+kPGoqrOOZx4iw9s2A6mdft2619ofhZHtw@mail.gmail.com>
Hi Dmitry
8.9.2012 15:54, Dmitry Golubovsky kirjoitti:
>
>> Your work for v86d ( http://patchwork.ozlabs.org/patch/157286/ )
>> is working wonderfully in my distro !
> Thanks for testing. The patchwork entry you mentioned also captures
> the discussion we had regarding non-standard use of C flags: the way
> Makefile is written in v86d does not capture them from the build
> environment, and they have to be pushed harder down via redefinition
> of $(CC) rather than via an environment variable.
>
> I thnk eventually I'll try to reintroduce the v86d patch: may I take
> your e-mail as a supporting vote? ;)
>
> Thanks.
>
Of course.
I will be glad to :)
Stefan
prev parent reply other threads:[~2012-09-08 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 4:32 [Buildroot] Fixing linux-pam build failures Dmitry Golubovsky
2012-09-08 11:28 ` Stefan Fröberg
2012-09-08 12:54 ` Dmitry Golubovsky
2012-09-08 14:40 ` Stefan Fröberg [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=504B58E3.3070901@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/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