This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Question on Makefile.in's program_transform_cross_name
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Kelley Cook <kelleycook at wideopenwest dot com>
- Cc: Nathanael Nerode <neroden at twcny dot rr dot com>, gcc at gcc dot gnu dot org
- Date: Fri, 5 Dec 2003 12:02:37 -0500
- Subject: Re: Question on Makefile.in's program_transform_cross_name
- References: <3FD0B60B.6060803@ford.com>
On Fri, Dec 05, 2003 at 11:44:59AM -0500, Kelley Cook wrote:
> Now looking look at the definitions of GCC_INSTALL_NAME and
> GCC_CROSS_NAME we get:
>
> GCC_INSTALL_NAME = `echo gcc|sed '$(program_transform_name)'`
> GCC_CROSS_NAME = `echo gcc|sed '$(program_transform_cross_name)'`
>
> Continuing to check the definitions of those two $(program...)
> definitions, I see
>
> program_transform_name = @program_transform_name@
> program_transform_cross_name = @program_transform_name@
>
> So those are always the same, which consequently means GCC_INSTALL_NAME
> and GCC_CROSS_NAME are always the same which means I could just delete
> the *_CROSS_NAME lines as well as the numerous spots in the makefile
> which differentiate on them.
>
> Is my analysis of the current situation correct and more importantly if
> so should GCC_INSTALL_NAME always be the same as GCC_CROSS_NAME? I
> think that the answer is yes since configure.in seems to take care of
> adjusting the sed script to prefix the target name.
Once upon a time, these were different. It was confusing, and people
didn't really like it, so now they're the same. I suspect you could
remove GCC_CROSS_NAME at this point.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer