This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: configure.in - target_libs def. needs a back slash?
- From: Andreas Schwab <schwab at suse dot de>
- To: "Gary Funck" <gary at intrepid dot com>
- Cc: "GCC List" <gcc at gcc dot gnu dot org>
- Date: Fri, 31 May 2002 10:22:08 +0200
- Subject: Re: configure.in - target_libs def. needs a back slash?
- References: <PMEMKNKIFEFGJGBCJFPPIEICCBAA.gary@intrepid.com>
"Gary Funck" <gary@intrepid.com> writes:
|> Hello,
|>
|> In reviewing configure.in I notce the following at around line 72:
|> # these libraries are built for the target environment, and are built after
|> # the host libraries and the host tools (which may be a cross compiler)
|> #
|> target_libs="target-libiberty \
|> target-libgloss \
|> target-newlib \
|> target-librx \
|> ${libstdcxx_version} \
|> target-libf2c \
|> ${libgcj}
|> target-libobjc"
|>
|> There is an entry for $(libgcj) which is not followed by a back slash.
|> Perhaps when target-libobjc was added, the backslash wasn't added to the
|> previous line?
It doesn't matter. All uses of $target_libs are in such a way that the
embedded newline doesn't hurt.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."