All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] reintroduce BUILD_LDFLAGS for the cross-compile case
Date: Sat, 18 Jan 2014 16:24:17 +0100	[thread overview]
Message-ID: <52DA9CA1.9010509@gmail.com> (raw)
In-Reply-To: <20140112161121.4d2d4b2b@opensuse.site>

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

Go ahead.
On 12.01.2014 13:11, Andrey Borzenkov wrote:
> This allows providing separate LDFLAGS for build and host environment, which
> are not necessary the same for cross-compile case. In particular, it allows
> building host programs statically to not depend on presence of libraries at
> run-time (e.g. MinGW environment on Windows) while continue to use default
> build time dynamic linking.
> 
> Also fix obsolete comments in confgure.ac - we do use different environment
> for build and host now.
> 
> In principle, it would be enough to just reset LDFLAGS before
> performing build time tests, but I think this functionality is useful
> by itself (e.g. to be able to link with libraries in non-standard
> location). And patch itself it trivial enough.
> 
> Attached because git won't send mail with so long lines.
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 274 bytes --]

      reply	other threads:[~2014-01-18 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 12:11 [PATCH] reintroduce BUILD_LDFLAGS for the cross-compile case Andrey Borzenkov
2014-01-18 15:24 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=52DA9CA1.9010509@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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 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.