I did cc the maintainer the first time but they reported that 10.9 was not
available to them.

/bin/sh ../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.
-I../.. -I../../include/  -I/sw/include  -g -O2 -c -o iso9660.lo iso9660.cpp
/bin/sh ../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.
-I../.. -I../../include/  -I/sw/include  -g -O2 -c -o cdio.lo cdio.cpp
/bin/sh ../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.
-I../.. -I../../include/  -I/sw/include  -g -O2 -c -o devices.lo devices.cpp
mkdir .libs
mkdir .libs
mkdir .libs
mkdir: .libs: File exists
mkdir: .libs: File exists
 g++ -DHAVE_CONFIG_H -I. -I../.. -I../../include/ -I/sw/include -g -O2 -c
cdio.cpp  -fno-common -DPIC -o .libs/cdio.o
 g++ -DHAVE_CONFIG_H -I. -I../.. -I../../include/ -I/sw/include -g -O2 -c
iso9660.cpp  -fno-common -DPIC -o .libs/iso9660.o
 g++ -DHAVE_CONFIG_H -I. -I../.. -I../../include/ -I/sw/include -g -O2 -c
devices.cpp  -fno-common -DPIC -o .libs/devices.o
In file included from iso9660.cpp:25:
In file included from ../../include/cdio++/iso9660.hpp:30:
../../include/cdio/iso9660.h:303:20: warning: field 'root_directory_record'
with variable sized type 'iso9660_dir_t' (aka 'iso9660_dir_s') not at the
end of a struct or class is a GNU extension [-Wgnu]
  iso9660_dir_t    root_directory_record;        /**< See 8.4.18 and
                   ^
../../include/cdio/iso9660.h:418:20: warning: field 'root_directory_record'
with variable sized type 'iso9660_dir_t' (aka 'iso9660_dir_s') not at the
end of a struct or class is a GNU extension [-Wgnu]
  iso9660_dir_t    root_directory_record;        /**< See section 8.5.12 and
                   ^
 g++ -DHAVE_CONFIG_H -I. -I../.. -I../../include/ -I/sw/include -g -O2 -c
cdio.cpp  -fno-common -DPIC -o cdio.o >/dev/null 2>&1
 g++ -DHAVE_CONFIG_H -I. -I../.. -I../../include/ -I/sw/include -g -O2 -c
devices.cpp  -fno-common -DPIC -o devices.o >/dev/null 2>&1
/bin/sh ../../libtool --tag=CXX   --mode=link g++  -g -O2   -o libcdio++.la
-rpath /sw/lib cdio.lo devices.lo  -L/sw/lib -lm
In file included from iso9660.cpp:25:
../../include/cdio++/iso9660.hpp:129:7: error: use of undeclared identifier
'free'
      free(p_stat);
      ^
../../include/cdio++/iso9660.hpp:131:2: error: use of undeclared identifier
'calloc'
        calloc( 1, sizeof(iso9660_stat_t)
        ^
../../include/cdio++/iso9660.hpp:138:7: error: use of undeclared identifier
'free'
      free(p_stat);
      ^
../../include/cdio++/iso9660.hpp:144:7: error: use of undeclared identifier
'free'
      free(p_stat);
      ^
2 warnings and 4 errors generated.
make[3]: *** [iso9660.lo] Error 1
make[3]: *** Waiting for unfinished jobs....
g++ -r -keep_private_externs -nostdlib -o
.libs/libcdio++.0.0.0.dylib-master.o  .libs/cdio.o .libs/devices.o
g++ -dynamiclib ${wl}-undefined ${wl}dynamic_lookup -o
.libs/libcdio++.0.0.0.dylib .libs/libcdio++.0.0.0.dylib-master.o  -L/sw/lib
-lm  -install_name  /sw/lib/libcdio++.0.dylib -compatibility_version 1
-current_version 1.0
(cd .libs && rm -f libcdio++.0.dylib && ln -s libcdio++.0.0.0.dylib
libcdio++.0.dylib)
(cd .libs && rm -f libcdio++.dylib && ln -s libcdio++.0.0.0.dylib
libcdio++.dylib)
ar cru .libs/libcdio++.a  cdio.o devices.o
ranlib .libs/libcdio++.a
creating libcdio++.la
(cd .libs && rm -f libcdio++.la && ln -s ../libcdio++.la libcdio++.la)
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
### execution of make failed, exit code 2
### execution of /tmp/fink.CXhdW failed, exit code 2
Removing runtime build-lock...
Removing build-lock package...
/sw/bin/dpkg-lockwait -r fink-buildlock-libcdio7-shlibs-0.79-3
(Reading database ... 129068 files and directories currently installed.)
Removing fink-buildlock-libcdio7-shlibs-0.79-3 ...
Failed: phase compiling: libcdio7-shlibs-0.79-3 failed
>
Before reporting any errors, please run "fink selfupdate" and try again.
Also try using "fink configure" to set your maximum build jobs to 1 and
attempt to build the package again.
If you continue to have issues, please check to see if the FAQ on Fink's
website solves the problem.  If not, ask on one (not both, please) of
these mailing lists:
>
      The Fink Users List <fink-users@lists.sourceforge.net>
      The Fink Beginners List <fink-beginn...@lists.sourceforge.net>,
>
with a carbon copy to the maintainer:
>
      Justin F. Hallett <the...@users.sourceforge.net>
>
Note that this is preferable to emailing just the maintainer directly,
since most fink package maintainers do not have access to all possible
hardware and software configurations.
>
Please try to include the complete error message in your report.  This
generally consists of a compiler line starting with e.g. "gcc" or "g++"
followed by the actual error output from the compiler.
>
Also include the following system information:
Package manager version: 0.35.99.git
Distribution version: selfupdate-rsync Tue Oct 29 15:33:05 2013, 10.9,
x86_64
Trees: local/main stable/main
Xcode.app: 5.0.1
Xcode command-line tools: 5.0.1.0.1.1382131676
Max. Fink build jobs:  8
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to