Dear All,

To build the clamav packages, fink requires gcc46.

The building of gcc46 failed. Below is the error line, with some output
before and after,
to give context to the problem.

> ....
> checking if /sw/src/fink.build/gcc46-4.6.1-1000/darwin_objdir/./gcc/xgcc
> -B/sw/src/fink.build/gcc46-4.6.1-1000/darwin_objdir/./gcc/
> -B/sw/lib/gcc4.6/i386-apple-darwin10.8.0/bin/
> -B/sw/lib/gcc4.6/i386-apple-darwin10.8.0/lib/ -isystem
> /sw/lib/gcc4.6/i386-apple-darwin10.8.0/include -isystem
> /sw/lib/gcc4.6/i386-apple-darwin10.8.0/sys-include  -m64 supports -c -o
> file.o... (cached) yes
> checking whether the
> /sw/src/fink.build/gcc46-4.6.1-1000/darwin_objdir/./gcc/xgcc
> -B/sw/src/fink.build/gcc46-4.6.1-1000/darwin_objdir/./gcc/
> -B/sw/lib/gcc4.6/i386-apple-darwin10.8.0/bin/
> -B/sw/lib/gcc4.6/i386-apple-darwin10.8.0/lib/ -isystem
> /sw/lib/gcc4.6/i386-apple-darwin10.8.0/include -isystem
> /sw/lib/gcc4.6/i386-apple-darwin10.8.0/sys-include  -m64 linker
> (/sw/src/fink.build/gcc46-4.6.1-1000/darwin_objdir/./gcc/collect-ld)
> supports shared libraries... yes
> checking dynamic linker characteristics... darwin10.8.0 dyld
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking sys/mman.h usability... yes
> checking sys/mman.h presence... yes
> checking for sys/mman.h... yes
> checking for mmap... yes
> checking for sys/mman.h... (cached) yes
> checking for mmap... (cached) yes
> checking whether read-only mmap of a plain file works... yes
> checking whether mmap from /dev/zero works... no
> checking for MAP_ANON(YMOUS)... yes
> checking whether mmap with MAP_ANON(YMOUS) works... yes
> checking for ANSI C header files... (cached) yes
> checking for memcpy... yes
> checking for working alloca.h... yes
> checking for alloca... yes
> checking size of double... 8
> checking size of long double... 16
> checking whether byte ordering is bigendian... no
> checking assembler .cfi pseudo-op support... no
> checking whether .eh_frame section should be read-only... no
> checking for __attribute__((visibility("hidden")))... no
> configure: updating cache ./config.cache
> configure: creating ./config.status
> config.status: creating include/Makefile
> config.status: creating include/ffi.h
> config.status: creating Makefile
> config.status: creating testsuite/Makefile
> config.status: creating man/Makefile
> config.status: creating fficonfig.h
> config.status: linking ../../../../gcc-4.6.1/libffi/src/x86/ffitarget.h to
> include/ffitarget.h
> config.status: executing default-1 commands
> Adding multilib support to Makefile in ../../../../gcc-4.6.1/libffi
> with_multisubdir=x86_64
> config.status: executing depfiles commands
> config.status: executing libtool commands
> config.status: executing include commands
> config.status: executing src commands
> config.status: executing depfiles commands
> config.status: executing libtool commands
> config.status: executing include commands
> config.status: executing src commands
> make: *** [all] Error 2
> ### execution of /var/tmp/tmp.1.CDOxNy failed, exit code 2
> Removing runtime build-lock...
> Removing build-lock package...
> /sw/bin/dpkg-lockwait -r fink-buildlock-gcc46-4.6.1-1000
> (Reading database ... 207580 files and directories currently installed.)
> Removing fink-buildlock-gcc46-4.6.1-1000 ...
> Failed: phase compiling: gcc46-4.6.1-1000 failed
>
> Before reporting any errors, please run "fink selfupdate" and try 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 of these mailing lists:
>
>     The Fink Users List <[email protected]>
>     The Fink Beginners List <[email protected]>,
>
> with a carbon copy to the maintainer:
>
>     Jack Howarth <[email protected]>
>
> 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.31.0
> Distribution version: selfupdate-cvs Fri Jul 29 08:13:28 2011, 10.6, i386
> Trees: local/main stable/main stable/crypto unstable/main unstable/crypto
> Xcode Version: 3.2.6-1
>
>
The machine is a 2 GHz Intel Core Duo iMac, running 10.6.8.

Could you please help me?

All the best, and thanks,
Eduardo Pestana
------------------------------------------------------------------------------
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
Fink-users mailing list
[email protected]
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