Closed ocefpaf closed 8 years ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
OS X is not happy. Not sure that is going on as libgfortran.3.dylib
does exist in the libgcc
package. @jakirkham any ideas?
gcc -DHAVE_CONFIG_H -I. -I../src -I../src -pedantic -Wall -arch x86_64 -fPIC -I/Users/travis/miniconda3/envs/_build_placehold_placehold_placehold_placehold_pla/include -I/Users/travis/miniconda3/envs/_build_placehold_placehold_placehold_placehold_pla/include -I/Users/travis/miniconda3/envs/_build_placehold_placehold_placehold_placehold_pla/include -MT grib_fortran_kinds.o -MD -MP -MF .deps/grib_fortran_kinds.Tpo -c -o grib_fortran_kinds.o grib_fortran_kinds.c
mv -f .deps/grib_fortran_kinds.Tpo .deps/grib_fortran_kinds.Po
gfortran -g -O2 -o same_int_long same_int_long.o grib_fortran_kinds.o
gfortran -g -O2 -c -o same_int_size_t.o same_int_size_t.f90
gfortran -g -O2 -o same_int_size_t same_int_size_t.o grib_fortran_kinds.o
gfortran -g -O2 -c -o grib_types.o grib_types.f90
gfortran -g -O2 -o grib_types grib_types.o grib_fortran_kinds.o
./grib_types > grib_kinds.h
dyld: Library not loaded: @rpath/./libgfortran.3.dylib
Referenced from: /Users/travis/miniconda3/conda-bld/work/grib_api-1.14.7-Source/fortran/./grib_types
Reason: image not found
/bin/sh: line 1: 29839 Trace/BPT trap: 5 ./grib_types > grib_kinds.h
make[1]: *** [grib_kinds.h] Error 133
make: *** [all-recursive] Error 1
Command failed: /bin/bash -x -e /Users/travis/build/conda-forge/ecmwf_grib-feedstock/recipe/build.sh
The command "conda build ./recipe" exited with 1.
Done. Your build exited with 1.
Thanks to cmake
we have a successful build using de default channel gcc
. @kmuehlbauer, @pelson, and @ajdawson if you have some time can you take a look at this?
Note that we are building only the shared libraries for now. Also, we have an extra dependency on libgcc
because of Fortran
.
@ocefpaf Nothing obvious. LGTM.
Thanks for the review @kmuehlbauer!
We are stuck with the
default
channelgcc
for Fortran modules, not sure if there is a better approach in sight.Closes #8