Re: [tlug] how to use makedepend?

[Miles Colman <mcolman@example.com>]

Thanks Stephen and Edward.
To clarify, I was just complaining that makedepend didn't assume the
right path to stdarg unless I specified the path in full. Now, I think
that the strange location is due to me installing the gcc 4.3 package.

I wasn't actually compiling an avr toolchain when I was doing the
'hello world' stuff, just making regular binaries from gcc, but I was
trying to build avr binaries when I first saw the warning. I pasted
the wrong message. Sorry.

Anyhow, do the c programmers out there have any alternatives to or
opinions on using splint and/or ctags?
Thanks,
Miles

On Wed, Apr 22, 2009 at 7:39 PM, Stephen J. Turnbull <stephen@example.com> wrote:
> Edward Middleton writes:
>
>  > My point was that Miles hasn't explained in sufficient detail 1. what he
>  > is trying to do 2. what he has done.  I don't know what the standard
>  > practice is on debian based distros but when cross compiling with
>  > openembeeded you don't install the target headers into /usr/include.
>
> Ah, that's true.  So you're saying that the cross compiler is looking
> in a non-standard place for its standard headers, but of course
> vanilla makedepend doesn't know about that.
>
> I wonder if you could get away with building your cross-toolchain
> staticly linked, and then do everything in a chroot jail that looks
> like a native environment for the target platform.
>
> On the other hand, Explicit Is Better Than Implicit.  I would prefer
> the approach presented in the makedepend man page, which is to do all
> the necessary configuration of CFLAGS and LDFLAGS etc in a variable,
> then hand those variables to programs like makedepend and the C
> compiler itself.
>
> --
> To unsubscribe from this mailing list,
> please see the instructions at http://www.tlug.jp/list.html
>
> The TLUG mailing list is hosted by the award-winning Internet provider
> ASAHI Net.
> Visit ASAHI Net's English-language Web page: http://asahi-net.jp/en/
>