On Saturday, 28 April 2012 at 09:48, Daniel Macks wrote: > On Fri, 27 Apr 2012 21:31:44 -0700, Brendan Cully > > wrote: > On 2012-04-19 3:06 PM, Alexander Hansen wrote: > > > On 4/19/12 11:15 AM, Cameron Christensen wrote: > > >> > > >> I'm using OSX Lion, latest updates of OS and fink: > > >> > > >> configure.in:77: warning: macro `AM_ICONV' not found in library > > >> configure.in:77: error: possibly undefined macro: AM_ICONV > > >> If this token and others are legitimate, please use > > m4_pattern_allow. > > >> See the Autoconf documentation. > > >> autoreconf: /usr/bin/autoconf failed with exit status: 1 > > >> ### execution of /tmp/fink.YITxS failed, exit code 1 > > >> Removing runtime build-lock... > > >> Removing build-lock package... > > >> /sw/bin/dpkg-lockwait -r fink-buildlock-fuse4x-dev-0.8.13-2 > > >> (Reading database ... 23550 files and directories currently installed.) > > >> Removing fink-buildlock-fuse4x-dev-0.8.13-2 ... > > >> Failed: phase compiling: fuse4x-dev-0.8.13-2 failed > > >> > > >> > > > The package has some missing build dependencies, which we should fix. > > > > > > Use "fink install automake1.11 autoconf2.6 libtool2" and then try your > > > build again. > > > > I've added builddepends for gettext-tools, automake1.11 and libtool2. > > Luckily, autoconf* is a Depends of automake--for now--but for > safety/sanity/transparancy you might want to specify it as a > BuildDepends here (since you are invoking it directly, not just > "automake is using it"). Also, the message indicates that an iconv
alright, done. > macro is being used, so you likely need libiconv-dev as a > BuildDepends done. > as well (no idea if/how that lib itself is actually used, so no idea > if it also leads to a Depends). Building on my machine, I see: I'm not sure either. It doesn't show up in otool -L /sw/lib/libfuse4x.dylib though. > checking for iconv... no, consider installing GNU libiconv > > so it definitely wants iconv and no idea why it's failing to find it (but > that might lead to different users getting different build results). Moving > further, the final validation check fails: I had to explicitly add -I%p/include -L%p/lib to CFLAGS at configure time to fix this. > Error: The -framework flag may get munged by libtool. See the gcc manpage for > information about passing multi-word options to flags for specific compiler > passes. > > Offending file: /sw/lib/libfuse4x.la > > Offending line: inherited_linker_flags=' -framework CoreFoundation' This one I don't know offhand how to fix, and I don't really have time at the moment to pore through gcc and libtool trying to figure out the right fix. Suggestions welcome. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ 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
