From: Mike Frysinger <vapier@gentoo.org>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 2/3] Make system enhancements, Draft 1
Date: Wed, 8 Jul 2009 20:41:31 -0400 [thread overview]
Message-ID: <200907082041.32384.vapier@gentoo.org> (raw)
In-Reply-To: <364299f40907081726l2a78728dx957f06cb3c46a986@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1438 bytes --]
On Wednesday 08 July 2009 20:26:37 Garrett Cooper wrote:
> On Wed, Jul 8, 2009 at 4:24 PM, Mike Frysinger<vapier@gentoo.org> wrote:
> > for the toolchain, do you purposefully only document CC and CFLAGS ?
>
> Where did I do that?
README.mk-devel
> > i'm not familiar with this "MAKEOPTS=';'" thing you refer to. what's
> > that all about ?
>
> -r, --no-builtin-rules
> Eliminate use of the built-in implicit rules. Also clear
> out the default list of suffixes for suffix rules.
>
> There isn't a way to disable -r in make-3.81 except by removing it
> from MAKEOPTS (that's how it was enabled in our make system at Cisco
> in my group). `MAKEOPTS=;' is the quick way out. Nasty PITA...
doesnt that clobber -j and -l and similar ?
rather than help the user, spank them for it. in the .mk, you can add a
findstring on the MAKEOPTS for "r" and $(error) out if found.
> > master_rules.mk shouldnt be a '-include' ... we want an error if that
> > doesnt exist
>
> I only did that to ensure that this commit could go in, irrespective
> of PATCH 3/4, but I agree, it should be enabled once both changes are
> committed.
dont worry about it ... assume they're going in as a set
> > your %.a rule is missing a call to ranlib on the archive
>
> Ok. How do I do that call exactly?
>
> ar [blah]
> ranlib [blah]
>
> maybe?
ranlib only needs one argument -- the archive
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 389 bytes --]
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2009-07-09 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 23:02 [LTP] [PATCH 2/3] Make system enhancements, Draft 1 Garrett Cooper
2009-07-08 23:24 ` Mike Frysinger
2009-07-09 0:26 ` Garrett Cooper
2009-07-09 0:41 ` Mike Frysinger [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=200907082041.32384.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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