* Simon Ruderich <si...@ruderich.org> [130815 00:20]:
> On Mon, Jul 01, 2013 at 02:39:58PM +0200, Matthias Klose wrote:
> > Please check for redundant search paths for -I and -L flags, which are
> > already
> > included in the search paths of the compiler.
> >
> > That is, things like
> >
> > /usr/{include,lib}
> > /usr/local/{include,lib}
> > /usr/{include,lib}/<multiarch>
> > /usr/local/{include,lib}/<multiarch>
> > [...]
> [...]
> Implementing this should be straight-forward, but I'm not sure if
> blhc is the best place to add this.
>
> Bernhard, what do you think? Should this get implemented in blhc
> or in your general buildd log scanner?
I'm also undecided which is the best place. As blhc already looks at
similar flags it might be easy to add there, but then it is quite a
different check compared to those blhc has.
> If you think blhc is the right place, what buildd-mode messages (e.g.
> I-foo, W-foo) should I use?
If you consider it something blhc should do, I'd suggest something like
W-dangerous-search-path. Otherwise I'll add a new rule to my log
scanner.
> (btw. are the sources of the buildd log scanner available)
The scanner itself is available at git://anonscm.debian.org/qa/bls.git,
the rules are embedded in their descriptions at
http://anonscm.debian.org/viewvc/qa/trunk/data/bls/descriptions/
Bernhard R. Link
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
