From: "Brian Jackson" <iggy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Common make.conf screwups?
Date: Fri, 19 Nov 2004 14:42:37 +0000 [thread overview]
Message-ID: <124236248c71da7a909c4de7f14b2ea0@testdomain.com> (raw)
In-Reply-To: <20041118194529.3ff36a8a@snowdrop.home>
On 7:45:29 pm 11/18/04 Ciaran McCreesh <ciaranm@gentoo.org> wrote:
> I've got some better vim syntax highlighting rules for make.conf lined
> up to go into the next app-vim/gentoo-syntax. One of the things that
> this lets me do is highlighting of (some kinds of) mistakes. What're
> the most common screwups that people see? My current list is:
I don't know if you can detect it, but basing a var on another unset var,
i.e.
#PORTDIR=/usr/portage
then later in make.conf:
PKGDIR=${PORTDIR}/packages
or something similar
--Iggy
>
> * CFLAGS: -0[123s] instead of -O[123s], -ffast-math globally
>
> * USE: +foo flags
>
> * ACCEPT_KEYWORDS: random duff entries (syntax is easy enough for me
> to validate the whole thing)
>
> * CHOST: there're certain settings that will cause glibc to fall over
> and die that people who are used to debian/sparc will sometimes use
>
> * MAKEOPTS: I'm kinda tempted to highlight "-j N" (where n is integer)
>
> --
> Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, Sparc, Mips)
> Mail : ciaranm at gentoo.org
> Web : http://dev.gentoo.org/~ciaranm
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-11-19 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 19:45 [gentoo-dev] Common make.conf screwups? Ciaran McCreesh
2004-11-18 20:34 ` Robert Moss
2004-11-18 20:40 ` Ciaran McCreesh
2004-11-18 21:58 ` Robert Moss
2004-11-19 14:50 ` Ned Ludd
2004-11-20 8:17 ` [gentoo-dev] " Duncan
2004-11-21 21:10 ` Robert Moss
2004-11-22 9:54 ` [gentoo-dev] " Duncan
2004-11-22 4:22 ` [gentoo-dev] " Luke-Jr
2004-11-19 14:42 ` Brian Jackson [this message]
2004-11-19 22:00 ` [gentoo-dev] " Drake Wyrm
2004-11-19 23:31 ` Jason Stubbs
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=124236248c71da7a909c4de7f14b2ea0@testdomain.com \
--to=iggy@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox