On Sat, Jun 30, 2012 at 10:12:36AM +0100, Mikolaj Kucharski wrote:
> Hi,
>
> Ports build by `dpb -a' fails at lang/gcc/4.6 with below:
>
> # zgrep execinfo gcc-4.6.3p3.log.gz
> checking execinfo.h usability... yes
> checking execinfo.h presence... yes
> checking for execinfo.h... yes
> checking execinfo.h usability... yes
> checking execinfo.h presence... yes
> checking for execinfo.h... yes
> checking execinfo.h usability... yes
> checking execinfo.h presence... yes
> checking for execinfo.h... yes
> /home/users/build/obj/gcc-4.6.3/gcc-4.6.3/libgfortran/runtime/backtrace.c:42:22:
> fatal error: execinfo.h: No such file or directory
>
> # ls -1 /var/db/pkg/ | grep execinfo
> libexecinfo-0.2p0v0
>
> Full log available at:
>
> http://www.kucharski.name/pub/ports/
>
I got another failure from libjava about magic.h, unfortunately VM
crashed and I don't have the log.
I downloaded lang/gcc/4.6 packages from nearest mirror:
# cd /usr/ports/lang/gcc/4.6 && make show=PKGNAMES
gcc-4.6.3p3 g95-4.6.3p3 gobjc-4.6.3p3 gcj-4.6.3p4 g++-4.6.3p5 libstdc++-4.6.3p3
gnat-4.6.3p3 gccgo-4.6.3p3
extracted all above packages and ran objdump -p on all the files from
the packages:
# grep -w NEEDED lang-gcc-46.objdump | sort | uniq
NEEDED libc.so.65.0
NEEDED libgcj-tools.so.1.0
NEEDED libgcj.so.1.0
NEEDED libgij.so.1.0
NEEDED libgmp.so.9.0
NEEDED libm.so.7.0
NEEDED libmpc.so.0.1
NEEDED libmpfr.so.1.1
NEEDED libpthread.so.16.0
NEEDED libz.so.4.1
I don't see libmagic and libexecinfo there, so does following change
make sense?
Index: Makefile
===================================================================
RCS file: /cvs/ports/lang/gcc/4.6/Makefile,v
retrieving revision 1.27
diff -u -r1.27 Makefile
--- Makefile 21 Jun 2012 13:56:57 -0000 1.27
+++ Makefile 30 Jun 2012 17:57:44 -0000
@@ -107,6 +107,8 @@
EXTRA_ENV += am_cv_func_iconv=no JAR=no
EXTRA_ENV += ac_cv_prog_M4=/usr/bin/m4
+EXTRA_ENV += ac_cv_header_execinfo_h=no
+EXTRA_ENV += ac_cv_header_magic_h=no
MAKE_FLAGS += ac_cv_path_mkdir=/bin/mkdir
CONFIGURE_ENV += ${EXTRA_ENV}
I just started the build with above patch, but I'm not sure is this the
way to go. Any comments?
--
best regards
q#
