[ADMB Users] gcc 4.xx 64-bit and source code

JohnS sibert at hawaii.edu
Tue Dec 9 13:34:28 PST 2008


Opening the source code is an important part of the ADMB Project plan.
It is currently a bit difficult to compile for all platforms as Evan
requests. We are working to solve these problems and to address a few
other problems in the source code. We plan to fully open the source
code in the second half of 2009. Meanwhile please be patient; this is
a relatively new project.

Thanks for your interest.
John

On Dec 9, 9:39 am, "John Ancheta" <jnanch... at gmail.com> wrote:
> Hi,
>
> Thanks for confirming, we haven't been able to get around to gcc-4.3 yet,
> but it is in the tasks list
>
> http://code.google.com/p/admb-project/issues/list
>
> johnoel
>
> On Tue, Dec 9, 2008 at 9:12 AM, Ian Taylor <Ian.Tay... at noaa.gov> wrote:
> >  Evan,
> > I just downloaded and installed the 64 bit linux admb ("Linux 64-bit for
> > gcc-3.4.6<http://admb-project.googlecode.com/files/admb-9.0.65-linux64-gcc3.4.6...>")
> > on a computer which professes to be using gcc 4.3.2. It compiled and ran
> > just fine. I've pasted the results of $gcc -v below:
> > -Ian
>
> > ###
>
> > ian at ian-laptop:~/admb$ gcc -v
> > Using built-in specs.
> > Target: x86_64-linux-gnu
> > Configured with: ../src/configure -v --with-pkgversion='Ubuntu
> > 4.3.2-1ubuntu11' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
> > --with-system-zlib --libexecdir=/usr/lib --without-included-gettext
> > --enable-threads=posix --enable-nls
> > --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
> > --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr
> > --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
> > --target=x86_64-linux-gnu
> > Thread model: posix
> > gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11)
>
> > ###
>
> > developers-boun... at admb-project.org wrote:
>
> > ------------------------------
>
> >   Subject:
> > problems with Linux version...  From:
> > Evan Cooch <evan.co... at cornell.edu> <evan.co... at cornell.edu>  Date:
> > Tue, 09 Dec 2008 10:43:46 -0500  To:
> > develop... at admb-project.org    To:
> > develop... at admb-project.org
> > Greetings -
>
> > Trying to install ADMB on a multi-Opteron box, that is binary compatible
> > for both 32- and 64-bit apps. Has gcc 4.1.2 installed. Since it doesn't look
> > as though there is a gcc 4.xx version for 64-bits (why?), I downloaded the
> > archive for the 32-bit version. Followed the directions for install, cd'd to
> > ADMB_HOME, ran make, and got a whole slew of errors, starting with
>
> > In file included from
> > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/backward/strstream:51,
>
> >                 from //home/egc/Desktop/admb/include/fvar.hpp:446,
> >                 from ham4.cpp:1:
> > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/backward/backward_warning.h:32:2:
> > warning: #warning This file includes at least one deprecated or antiquated
> > header. Please consider using one of the 32 headers found in section
> > 17.4.1.2 of the C++ standard. Examples include substituting the <X> header
> > for the <X.h> header for C++ includes, or <iostream> instead of the
> > deprecated header <iostream.h>. To disable this warning use
> > -Wno-deprecated....
>
> > and culminating with:
>
> > /usr/bin/ld: cannot find -ldf1b2stub
> > collect2: ld returned 1 exit status
> > /bin/sh: ./ham4: No such file or directory
> > make: *** [ham4] Error 127
>
> > My guess is that that when ADMB tries to compile using gcc, it isn't smart'
> > enough to tell gcc to compile for 32-bits (the default on this machine is to
> > compile for 64 unless you throw the -m32 flag at it during compilation).
> > Moreover, 32-bit and 64-bit libs are generally both installed on 64-bit
> > machines, and ADMB would need to know where to find what it needs.
>
> > Suggestions?  Since ADMB is now being given away freely, why not consider
> > making the source available, and letting users do a config/make/make install
> > sequence? Would make your lives simpler than trying to make binaries which
> > are unlikely to run on all permutations of Linux.
>
> > ------------------------------
>
> > _______________________________________________
> > Users mailing listUs... at admb-project.orghttp://lists.admb-project.org/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Us... at admb-project.orghttp://lists.admb-project.org/mailman/listinfo/users



More information about the Users mailing list