bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

EXTRA_LDFLAGS


From: Albert Chin-A-Young
Subject: EXTRA_LDFLAGS
Date: Fri, 29 Sep 2000 00:55:37 -0500
User-agent: Mutt/1.1.12i

Two issues:
  1. The patch below fixes a problem in configure.in whereby
     `$GXX --version` is being called when $GXX != "g++". Also,
     I redid the test -n "$GCC" with test "$GCC" = yes because
     configure has tests of the latter case at the beginning
     (and because it seems more correct).

  2. The value of EXTRA_LDFLAGS if --enable-rpath is given for Solaris is:
     EXTRA_LDFLAGS="-R ../lib:\$(libdir) $EXTRA_LDFLAGS"

     Is this really a wise thing? I might need some correcting on this but
     I interpret this to mean that if ncurses is compiled as a shared
     library and one of the programs in progs/ is compiled, the runtime
     library search path for libncurses.so will be "../lib:$(libdir)". So,
     if my cwd is /tmp/foo, will the search path be
       /tmp/lib
       $(libdir)

     Actually, just tried this by copying libncurses.so.5 to /tmp/lib with
     my cwd set to /tmp/foo and ldd on the tic binary has:
        libncurses.so.5 =>       ../lib/libncurses.so.5
        libc.so.1 =>     /usr/lib/libc.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1

     I know why ../lib is chosen but I dislike it.

-- 
albert chin (address@hidden)

-- snip snip
--- configure.in.orig   Fri Sep 29 00:30:02 2000
+++ configure.in        Fri Sep 29 00:39:48 2000
@@ -79,9 +79,9 @@
 
 ###    Checks for programs.
 AC_PROG_CC
-if test -n "$GCC" ; then
-AC_MSG_CHECKING(version of gcc)
-eval "$CC --version"
+if test "$GCC" = yes ; then
+       AC_MSG_CHECKING(version of gcc)
+       eval "$CC --version"
 fi
 if test "$host" != $build; then
        AC_CHECK_PROGS(BUILD_CC, $CC gcc cc)
@@ -124,8 +124,16 @@
        AC_PROG_CXX
        popdef([AC_MSG_ERROR])dnl
 fi
+
 changequote(,)dnl
-if test -n "$GXX" ; then case "`${CXX-g++} --version`" in 1*|2.[0-6]*) GXX=""; 
CXX=""; ac_cv_prog_gxx=no; cf_cxx_library=no ; echo No: templates do not work;; 
esac; fi
+if test "$GXX" = yes; then
+       case "`${CXX-g++} --version`" in
+       1*|2.[0-6]*)
+               GXX=""; CXX=""; ac_cv_prog_gxx=no
+               cf_cxx_library=no
+               echo No: templates do not work ;;
+       esac
+fi
 changequote([,])dnl
 
 AC_MSG_CHECKING(if you want to build C++ binding and demo)
@@ -846,17 +854,18 @@
 if test -n "$CXX" ; then
        AC_LANG_CPLUSPLUS
        CF_STDCPP_LIBRARY
-       case "`${CXX-g++} --version`" in
-       1*|2.[0-6]*)
-           cf_cxx_library=yes
-           ;;
-       2.7*)
-           CF_GPP_LIBRARY
-           ;;
-       *)
-           cf_cxx_library=no
-           ;;
-       esac
+       if test "$GXX" = yes; then
+               case "`${CXX-g++} --version`" in
+               1*|2.[0-6]*)
+                       cf_cxx_library=yes ;;
+               2.7*)
+                       CF_GPP_LIBRARY ;;
+               *)
+                       cf_cxx_library=no ;;
+               esac
+       else
+               cf_cxx_library=no
+       fi
        AC_CHECK_HEADERS(typeinfo)
        CF_BOOL_DECL
        CF_BOOL_SIZE
@@ -958,7 +967,7 @@
 ### using a 'char' for bools.  gcc 2.7.0's conversion-warnings are broken too
 ### badly to consider using for development purposes, but 2.5.8 is okay.
 if test -n "$with_warnings"; then
-       if test -n "$GCC"; then
+       if test "$GCC" = yes; then
                case "`$CC --version`" in
                2.6.3)
                        if test "$cf_cv_type_of_bool" != "char"; then



reply via email to

[Prev in Thread] Current Thread [Next in Thread]