From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2012.11.0 released
Date: Tue, 27 Nov 2012 13:44:14 +0100 [thread overview]
Message-ID: <82aead2c9b94d51fbde156e74831b5e1@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20121127122445.GC10460@pengutronix.de>
Hei hei,
Am 2012-11-27 13:24, schrieb Michael Olbrich:
> What we changed was the handling of additional compiler and linker flags.
> In the past we've tried to pass these flags through the build-systems of
> the individual packages. This was always a lot of work and wasn't very
> reliable. Now the compiler and linker a wrapper scripts that insert the
> necessary flags before calling the real tool.
> This should make writing rules much easier, especially for packages with
> hand-written Makefiles.
Is it necessary to change any existing rules?
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-11-27 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 12:24 Michael Olbrich
2012-11-27 12:44 ` Alexander Dahl [this message]
2012-11-27 14:18 ` Michael Olbrich
2012-11-30 14:27 ` [ptxdist] md5sum and ptxdist-2012.11.0 Robert Bouwens
2012-11-30 14:31 ` Marc Kleine-Budde
2012-11-30 15:08 ` Robert Schwebel
2012-11-30 15:42 ` [ptxdist] Antwort: " Robert Bouwens
2012-11-30 19:07 ` Robert Schwebel
2012-12-06 12:39 ` [ptxdist] [ANNOUNCE] PTXdist 2012.11.0 released - problems Tim Sander
2012-12-06 14:36 ` Michael Olbrich
2012-12-07 8:09 ` Tim Sander
2012-12-07 11:02 ` Michael Olbrich
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=82aead2c9b94d51fbde156e74831b5e1@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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