[PATCH 1 of 3] configure: check for libstdc++.{so,dylib,a}
Yann E. MORIN
yann.morin.1998@anciens.enib.fr
Mon May 30 16:33:00 GMT 2011
On Monday 30 May 2011 06:59:04 Bryan Hundven wrote:
> configure | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> # HG changeset patch
> # User Bryan Hundven <bryanhundven@gmail.com>
> # Date 1306731488 25200
> # Node ID e48d80f0eb9ea97c2d12f7239a7c54858fb0126a
> # Parent fa3a18f9abcf9dde1535088554778fe4c4e5e831
> configure: check for libstdc++.{so,dylib,a}
> diff -r fa3a18f9abcf -r e48d80f0eb9e configure
> --- a/configure Sun May 29 19:24:41 2011 +0200
> +++ b/configure Sun May 29 21:58:08 2011 -0700
> @@ -429,6 +429,17 @@
> has_or_abort lib="${ncurses_libs}" \
> err="'ncurses' library was not found"
>
> +stdcpp_libs="$( for x in so dylib; do \
> + printf "libstdc++.$x "; \
> + done \
> + )"
> +has_or_abort lib="${stdcpp_libs}" \
> + err="'libstdc++' shared library was not found"
> +
Add the static lib in the check, in case only the static version
is available.
What we really want to know is two-fold:
1) are requirements for PPL available?
2) can we build a statically linked toolchain?
Which trnslates into:
1) is libstdc++ available at all (shared or static)?
2) is static libstdc++ available?
Yes, this could duplicate the test below. We don't care, as most of
the time, the shared library will be present, and thus the two tests
will be different.
> +has_or_warn lib="libstdc++.a" \
> + err="'libstdc++' static library was not found" \
> + kconfig=has_static_libstdcpp
> +
This hunk should go into the patch 2.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list