Home > Could Not > Could Not Link Conftestf.o

Could Not Link Conftestf.o

no checking if Solaris -Xa option is needed... no checking whether a location for the HDF5 library was specified... . comment:6 Changed 8 years ago by anonymous Milestone Port Bugs deleted Milestone Port Bugs deleted comment:7 Changed 7 years ago by ryandesign (Ryan Schmidt) Resolution set to fixed Status changed from Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Source

I'm doing this all with Root User enabled. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. no configure: displaying some results checking CPPFLAGS... -DNDEBUG -Df2cFortran checking CC CFLAGS... /usr/bin/gcc-4.0 -O2 -fno-common checking type /usr/bin/gcc-4.0... /usr/bin/gcc-4.0 is /usr/bin/gcc-4.0 checking CXX... /usr/bin/g++-4.0 checking CXXFLAGS... -O2 -fno-common checking type /usr/bin/g++-4.0... ifort checking FFLAGS... -O2 checking type ifort... http://www.unidata.ucar.edu/support/help/MailArchives/netcdf/msg11715.html

yes checking for ifort option to produce PIC... yes checking for an ANSI C-conforming const... but same error. Unfortunately, adding the -Mnomain flag to the Fortran compiler ("pgf90 -Mnomain") actually caused the netcdf-fortran configure script to break: Quote: checking for C-equivalent to Fortran routine "SUB"...

https://gist.github.com/b3acad026e5b659eac00 Member tdsmith commented Sep 29, 2015 I can't reproduce this and we didn't capture the debug log of the failed configure run; can you build with -d and then, when Jared Back to top mkcolgJoined: 30 Jun 2004Posts: 6845Location: The Portland Group Inc. The rest are > > compile flags (assuming you want 64bit, otherwise change x96_64 to i386 and > > -m64 to -m32). > > > > If this works for you, If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.

sub_ checking for Fortran "byte"... yes checking whether fortran type sizes should be checked... You could also add "-g -O2" to > each of those flags as well (e.g. i386-apple-darwin8.11.1 checking for a BSD-compatible install... /usr/bin/install checking whether build environment is sane...

yes checking for dlfcn.h... yes checking whether C API is desired... checking whether extra example tests should be run... Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic

no checking whether to skip C++, F77, or F90 APIs if compiler is broken... Hopefully we can get it going for you too. immediate configure: finding other utilities checking for a BSD-compatible install... /usr/bin/install configure: trying to set fortran flags for this platform configure: trying to set flags for this platform checking if _HPUX_SOURCE yes checking dynamic linker characteristics...

checking if ifort static flag works... http://jessriegel.com/could-not/could-not-be-located-in-the-dynamic-link-library-adobelinguistic-dll.html I've looked through configure -h but can't see anything that relates to this. checking whether new netCDF-4 C++ API is to be built... You can not post a blank message.

Ocean Modeling Discussion Forum Index All times are UTC Powered by phpBB Forum Software © phpBB Group Skip to main content Developer Zone Join today Log in DevelopmentOSAndroid*Chrome*HTML5Windows*Device2-in-1 & Ultrabook™Business ClientEmbedded yes checking whether we are cross compiling... ifort checking whether we are using the GNU Fortran 77 compiler... http://jessriegel.com/could-not/could-not-link-client-dll-function.html no checking if /usr/bin/g++-4.0 supports -c -o file.o...

no checking for ifort... no checking whether examples should be built... Mike Mike Oldest first Newest first Threaded Comments only Change History (7) comment:1 Changed 8 years ago by [email protected]… Description modified (diff) Owner changed from [email protected]… to [email protected]… Port netcdf added

A search on Google returns nothing specific, other than it is related to gfortran under Cygwin, but you already knew that.

United States Copyright © Apple Inc. If you provide the config.log generated by configure, I will take a look and see if anything else pops out. jhcsu commented Oct 3, 2015 I reinstalled gcc using homebrew - same version as I had before (5.2.0), but this time installed from the bottle - and now netcdf builds from All rights reserved.

yes checking for sys/types.h... no checking dynamic linker characteristics... Download in other formats: Comma-delimited Text Tab-delimited Text RSS Feed Open Menu Close Menu Apple Shopping Bag Apple Mac iPad iPhone Watch TV Music Support Search apple.com Shopping Bag : CommunitiesSign http://jessriegel.com/could-not/ldrsetsessionname-could-not-be-located-in-the-dynamic-link.html gawk checking whether make sets $(MAKE)...

configure: error: Could not link conftestf.o and conftest.o I am using ifort 10.1.012 on a Mac with Leopard installed. Thanks in advance. This error doesn't appear to be related specifically to netcdf-fortran; are you able to compile other fortran programs? gfortranchecking FCFLAGS... -g -O2checking type gfortran...

no checking whether FC is set to ''... nmedit checking for -single_module linker flag... BSD nm checking whether ln -s works... ifort is /usr/bin/ifort checking F90...

But once I ditched the -Mnomain flag and set DYLD_LIBRARY_PATH, netcdf-fortran built perfectly. Closing due to lack of response. yes configure: Processing NetCDF-4 options. yes > >> checking for Fortran "integer*2"...

yes checking whether large file (> 2GB) tests should be run... Next by Date: [netCDFJava #SXO-208102]: Reading grib1 files Previous by thread: [netCDF #FVK-122895]: Problem with installing netCDF. yes checking if /usr/bin/g++-4.0 supports -c -o file.o... (cached) yes checking whether the /usr/bin/g++-4.0 linker (/usr/bin/ld) supports shared libraries... ifort checking FFLAGS... -O2 checking type ifort...

Also, please send us a copy of the config.log generated when you ran the netCDF-Fortran configure script, as it contains information that may help us to diagnose the problem you are I did find that if I > removed FFLAGS, then the config failed where it fails for you. > > Cheers! > > Sean > > Sorry, I forgot to send no checking if ifort supports -c -o file.o... strip checking for ranlib...