This is the mail archive of the
mailing list for the GCC project.
Re: plugin includes for MELT
- From: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- To: Basile STARYNKEVITCH <basile at starynkevitch dot net>
- Cc: 'GCC Mailing List' <gcc at gcc dot gnu dot org>
- Date: Tue, 4 Mar 2008 21:47:06 +0100
- Subject: Re: plugin includes for MELT
- References: <47C55E11.firstname.lastname@example.org> <003201c87969$bc06fa40$2e08a8c0@CAM.ARTIMI.COM> <47C5AB49.email@example.com> <004601c87974$408c6890$2e08a8c0@CAM.ARTIMI.COM> <47C5C181.firstname.lastname@example.org> <47C5C427.email@example.com> <47C6E3D3.firstname.lastname@example.org> <20080228171355.GB13837@ins.uni-bonn.de> <47C6F5D3.email@example.com>
* Basile STARYNKEVITCH wrote on Thu, Feb 28, 2008 at 06:56:35PM CET:
> Ralf Wildenhues wrote:
>> * Basile STARYNKEVITCH wrote on Thu, Feb 28, 2008 at 05:39:47PM CET:
>>>> run-basilys.d: run-basilys.h \
>>>> $(CONFIG_H) $(SYSTEM_H) $(TIMEVAR_H) $(TM_H) $(TREE_H) $(GGC_H) \
>>>> tree-pass.h basilys.h gt-basilys.h
>>>> $(CC) -MT run-basilys-deps -MMD $(ALL_CFLAGS) $(ALL_CPPFLAGS) $<
>> The build compiler may not be gcc and may not understand -MT and -MMD.
> Yes, I know. But how can I avoid that?
Use depcomp. Rather than explaining how to do that, it's easier if you
wait until Tom puts the depcomp support code in the tree, then use it
the same way the other stuff will.
>> Wasn't there a proposal to use depcomp in gcc a while ago?
> What is depcomp exactly?
A compiler wrapper that helps to do dependency computation as a
side-effect of compilation. IIRC it first appeared in Automake
(though its authors are also GCC developers, I'm not sure who
>>>> mkdir -p $(melt_build_include_dir); \
>> mkdir -p is not portable, use $(mkinstalldirs).
> Is $(mkinstalldirs) usable for non-installed directories?
> (in other words, it does not do any chown or chmod?