[BuildTools] COIN/OR on a 64-bit machine

[Cumhur A Gelogul]

I am sorry, I thought I was at the right mailing list.
I will create a ticket for the problem. I appreciated your help.

Thanks

Cumhur




On 8/28/07, Andreas Waechter <andreasw at watson.ibm.com> wrote:
>
> Hi Cumhur,
>
> The BuildTools mailing list is not meant for bug reports, it is meant for
> the developers of the COIN BuildTools to communicate.
>
> To handle your problem, please submit a ticket at the BuildTools trac
> page (https://projects.coin-or.org/BuildTools).  This also allows you to
> attach large files if necessary.  To submit a ticket you first need to
> register and log in (see http://www.coin-or.org/usingTrac.html)
>
> As for your particular problem, from the make output it seems to me that
> you are working on a SUN?  I have no experience working with GNU compilers
> on a SUN (wny not using the native sun compilers?).  You might try to
> compile static libraries instead of shared libraries (by specifying
> --disable-shared), since the error message appears during the linkage of
> the shared library, and you observed the warning message regarding shared
> libraries in your configure output.
>
> When you submit a ticket, make sure you include information about your
> operating system, the compiler (incl. version) you are using, which
> version of the COIN code you are trying to compile etc.
>
> Regards,
>
> Andreas
>
> On Tue, 28 Aug 2007, Cumhur A Gelogul wrote:
>
> > Hi Ted and Andreas,
> >
> > Thanks for your reply to my previous email. I specified the g++ compiler
> and
> > removed other flags. It completes succesfully -though with some warning
> > messages which are as follows:
> >
> >> ./configure CC=/usr/sfw/bin/gcc CXX=/usr/sfw/bin/g++ > myconfigure.log
> > configure: WARNING: Could not automatically determine how to tell the
> linker
> > about automatic inclusion of the path for shared libraries.  The test
> > examples might not work if you link against shared objects.  You will
> need
> > to set the LD_LIBRARY_PATH, DYLP_LIBRARY_PATH, or LIBDIR variable
> manually.
> >
> > Then I ran the make command, and got the following error messages. Could
> you
> > tell what I am missing now? I have attached myconfigure.log to this
> email as
> > well.
> >
> > Thank you very much.
> > Cumhur
> >
> > OUTPUT OF MAKE:
> > Making all in CoinUtils
> > Making all in src
> > /bin/bash ../libtool --tag=CXX --mode=link /usr/sfw/bin/g++   -O3
> > -fomit-frame-pointer -pipe -DNDEBUG -pedantic-errors -Wimplicit
> > -Wparentheses -Wreturn-type -Wcast-qual -Wall -Wpointer-arith
> > -Wwrite-strings -Wconversion   -o libCoinUtils.la -rpath
> > /home/uxtapa1/a557563/COIN/FlopC++-1.0.1/lib  CoinBuild.lo
> > CoinDenseVector.lo  CoinError.lo CoinFactorization1.lo
> CoinFactorization2.lo
> > CoinFactorization3.lo CoinFactorization4.lo CoinFileIO.lo
> > CoinIndexedVector.lo CoinLpIO.lo CoinMessage.lo  CoinMessageHandler.lo
> > CoinModel.lo CoinModelUseful.lo  CoinModelUseful2.lo CoinMpsIO.lo
> > CoinPackedMatrix.lo  CoinPackedVector.lo CoinPackedVectorBase.lo
> > CoinPostsolveMatrix.lo CoinPrePostsolveMatrix.lo
> CoinPresolveDoubleton.lo
> > CoinPresolveDual.lo  CoinPresolveDupcol.lo CoinPresolveEmpty.lo
> > CoinPresolveFixed.lo CoinPresolveForcing.lo
> CoinPresolveHelperFunctions.lo
> > CoinPresolveImpliedFree.lo  CoinPresolveIsolated.lo
> CoinPresolveMatrix.lo
> > CoinPresolvePsdebug.lo CoinPresolveSingleton.lo  CoinPresolveSubst.lo
> > CoinPresolveTighten.lo  CoinPresolveTripleton.lo CoinPresolveUseless.lo
> > CoinPresolveZeros.lo CoinShallowPackedVector.lo  CoinWarmStartBasis.lo
> > CoinWarmStartDual.lo
> > *** Error code 1
> > *** Error code 1
> > The following command caused the error:
> > failcom='exit 1'; \
> > for f in x $MAKEFLAGS; do \
> >  case $f in \
> >    *=* | --[!k]*);; \
> >    *k*) failcom='fail=yes';; \
> >  esac; \
> > done; \
> > dot_seen=no; \
> > target=`echo all-recursive | sed s/-recursive//`; \
> > list='src '; for subdir in $list; do \
> >  echo "Making $target in $subdir"; \
> >  if test "$subdir" = "."; then \
> >    dot_seen=yes; \
> >    local_target="$target-am"; \
> >  else \
> >    local_target="$target"; \
> >  fi; \
> >  (cd $subdir && make  $local_target) \
> >  || eval $failcom; \
> > done; \
> > if test "$dot_seen" = "no"; then \
> >  make  "$target-am" || exit 1; \
> > fi; test -z "$fail"
> > *** Error code 1
> > The following command caused the error:
> > failcom='exit 1'; \
> > for f in x $MAKEFLAGS; do \
> >  case $f in \
> >    *=* | --[!k]*);; \
> >    *k*) failcom='fail=yes';; \
> >  esac; \
> > done; \
> > dot_seen=no; \
> > target=`echo all-recursive | sed s/-recursive//`; \
> > list='CoinUtils Clp Osi Cgl Cbc FlopCpp'; for subdir in $list; do \
> >  echo "Making $target in $subdir"; \
> >  if test "$subdir" = "."; then \
> >    dot_seen=yes; \
> >    local_target="$target-am"; \
> >  else \
> >    local_target="$target"; \
> >  fi; \
> >  (cd $subdir && make  $local_target) \
> >  || eval $failcom; \
> > done; \
> > if test "$dot_seen" = "no"; then \
> >  make  "$target-am" || exit 1; \
> > fi; test -z "$fail"
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On 8/27/07, Andreas Waechter <andreasw at watson.ibm.com> wrote:
> >>
> >> Hi Cumhur,
> >>
> >> Please look at the config.log file in the subdirectory corresponding
> the
> >> the configure script that is run to produce that output.  See
> >>
> >>
> >>
> https://projects.coin-or.org/BuildTools/wiki/user-troubleshooting#ProblemsDuringConfiguration
> >>
> >> It seems to me that the C++ compiler that the configure scripts find
> >> doesn't work.  I note that you only specify the C compiler, but not the
> >> C++ compiler in the command line.
> >>
> >> The config.log file will show you the specific compiler command it is
> >> trying to run, and the test program it is trying to compile.  This
> should
> >> help you to find out what is wrong with your system.
> >>
> >> If you are building on a 64bit machine, you usually don't need to
> specify
> >> anything special, if you compile compiles in 64bit more by default
> (that
> >> is the case on my system).  Otherwise, for the GNU compilers, you need
> to
> >> specify the -m64 flag, e.g. using the ADD_CXXFLAGS, ADD_CFLAGS, etc
> >> configure variables arguments.  Please read the documentation for those
> >> options.
> >>
> >> I hope this helps,
> >>
> >> Andreas
> >>
> >>
> >> On Mon, 27 Aug 2007, Cumhur A Gelogul wrote:
> >>
> >>> Hi all,
> >>> I am trying to build COIN/OR libs on a 64-bit machine. I use the
> >> following
> >>> configure command:
> >>>
> >>>>  ./configure CC=/usr/sfw/bin/gcc CFLAG="-pto -PIC -DIL_STD
> >> -xarch=amd64" >
> >>> myconfigure.log
> >>>
> >>> I am getting an error message as follows:
> >>>>  configure: WARNING: The flags CXXFLAGS="  -DNDEBUG   " do not
> work.  I
> >>> will now just try '-O', but you might want to set CXXFLAGS manually.
> >>>>  configure: WARNING: This value for CXXFLAGS does not work.  I will
> >>> continue with empty CXXFLAGS, but you might want to set CXXFLAGS
> >> manually.
> >>>>  configure: WARNING: Could not automatically determine how to tell
> the
> >>> linker about automatic inclusion of the path for shared
> libraries.  The
> >> test
> >>> examples >  might not work if you link against shared objects.  You
> will
> >>> need to set the LD_LIBRARY_PATH, DYLP_LIBRARY_PATH, or LIBDIR variable
> >>> manually.
> >>>>  configure: WARNING: Cannot find C-function for checking Inf. Check
> >> will
> >>> test whether the value is different from DBL_MAX
> >>>>  configure: WARNING: Cannot find C-function for checking NaN. Check
> >> will
> >>> return false
> >>>>  configure: error: Cannot find integer type with 64 bits
> >>>>  configure: error: /bin/bash './configure' failed for CoinUtils
> >>> Can you help make sense why I am getting this error?
> >>> Should I pay special attention to some settings because this is a
> 64-bit
> >>> machine?
> >>>
> >>> Thanks in advance.
> >>>
> >>>
> >>> Cumhur
> >>>
> >>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.coin-or.org/pipermail/buildtools/attachments/20070828/50ded7b4/attachment-0001.html