Re: dbus looking for libtool?

ve a more complete build log? I'd like to see what happens at the autoreconf stage. Thanks, Peter -- Peter O'Gorman http://pogma.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: possible libtool 2.2.6 issue

good reason at the time though. :( Peter -- Peter O'Gorman http://pogma.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Why ar doesn't call ranlib on Mac?

Alexy Khrabrov wrote: > Peter -- > > On Wed, Mar 4, 2009 at 10:18 AM, Peter O'Gorman wrote: >> Alexy Khrabrov wrote: >>> In building various Linux things from source on Mac, I've run into the >>> "archive has no table of contents" problem seve

Re: cmake 2.6.2: _FILE_OFFSET_BITS=64/uClibc built w/o large file support

looked around but apparently haven't found the obvious toggle switch. > In file included from /usr/include/elf.h:23, Why do you have /usr/include/elf.h ? Peter -- Peter O'Gorman http://pogma.com ___ macports-users mailing list macports-user

Re: Why ar doesn't call ranlib on Mac?

ble of contents is created. As you can see from the ar sources it calls ranlib -q normally, and ranlib -f if it saw the -s flag. Ranlib -q will "Do nothing if a universal file would be created." whereas ranlib -f will create the fat archive. P

Re: Why ar doesn't call ranlib on Mac?

Joshua Root wrote: > Peter O'Gorman wrote: >> Alexy Khrabrov wrote: >>> In building various Linux things from source on Mac, I've run into the >>> "archive has no table of contents" problem several times. The fix is >>> invariably to go and

Re: Why ar doesn't call ranlib on Mac?

since Mac OS X 10.4 does ranlib the archive. I filed a bug at the time asking for the -S flag to turn off this behavior to speed up creating an archive incrementally. http://www.opensource.apple.com/darwinsource/10.5.6/cctools-667.3/ar/ar.c Peter -- Peter O

Re: error near build_libtool_libs

me, aclocal did not find the libtool-2.x macros in its search path. Please try rebuilding the problematic ports with the libtool port installed. If the build succeeds, then file tickets on those ports for the missing build dependency. Peter -- Peter O'Gorman http://pogma.com ___

Re: Please help.....

Altoine Barker wrote: > What shell are you working in? > > -Altoine > > On Tue, Dec 2, 2008 at 4:06 AM, Christos Vlachos > <[EMAIL PROTECTED] > wrote: > > Dear all, > I would appreciate your help on the following problem. I want to > uninstall MacPorts, sinc

Re: linking to libssl and libcrypt

Shawn Protsman wrote: > Undefined symbols: >"_inflateEnd", referenced from: >_zlib_stateful_free_ex_data in liballkeyrtv.a(c_zlib.o) >_bio_zlib_free in liballkeyrtv.a(c_zlib.o) >"_inflateInit_", referenced from: Need -lz. Peter

Re: gtk1 & X libraries

r add dylib to the list of extensions that configure searches for when looking for X11. If you want a workaround, installing X11 packages from your Leopard install disk, then reinstalling the latest package from xquartz.macosforge.org, should work.

Re: MacPorts that use dscl create group records with password keys -- is this an error?

sword: * PrimaryGroupID: 0 And the group(5) manpage says: The passwd field is an optional encrypted password. This field is rarely used and an asterisk is normally placed in it rather than leaving it blank. Peter -- Peter O'Gorman http://pogma.com ___

Re: trouble building libtool

d ). autoconf should depend on m4, automake depend on autoconf, and libtool, since it is patched, should depend on all of them. Peter -- Peter O'Gorman http://pogma.com ___ macports-users mailing list macports-users@lists.macosforge.org http://l

Re: Why does link pick up wrong library

stall_name, you will, unfortunately, have to rebuild everything that uses freetype. > I don't understand why it refers to 10.16.0, when the build was 2.3.5. The versions of libraries do not need to match the package version. Hope this helps, Peter -- Peter O'Gorman http://pogma

Re: Why does link pick up wrong library

dylib, which > isn't surprising as there is no such file. Check that /opt/local/lib/libfreetype.dylib has the correct install_name: otool -D /opt/local/lib/libfreetype.dylib Peter -- Peter O'Gorman http://pogma.com ___ macports-

Re: GCC questions

rity over > anything else. Is there a way to accomplish the same with include paths? Well, looks like whatever is installed by fink will have priority, then macports, then system etc. You really should not need to worry about setting system include paths, the compiler will have a sane s

Re: ImageMagick checksun error

a2333a213a93cef21f125eeac9682f3136f782f0 rmd160 0d0a058ad079be46c962ddb0f0547c6d9cbe1ac4 It seems likely that upstream replaced the tarball. Peter -- Peter O'Gorman http://pogma.com ___ macports-users mailing list macports-users@lists.macosforge.org

Re: libtool and ImageMagick problems

(#14195). I've also attached the > output Peter O'Gorman requested (and sent it to him off-list also). I > couldn't assign it to you, though. I just committed a patch for this to libtool - and put a workaround in the bug which should work until the imagemagick fo

Re: Is HFS really "scary"?

paul beard wrote: > > [OT] > I use FreeBSD and like it just fine: in fact that's one of the reason I > use [Mac|Darwin]Ports. fink was fine but once it became a leaderless > mob, I left. > [/OT] This kind of crap does not encourage me to help out on this list. Peter

Re: libtool and ImageMagick problems

e builddir): /bin/sh ./libtool --debug --mode=install /usr/bin/install 'utilities/convert' '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_ports_graphics_ImageMagick/work/destroot/opt/local/bin/convert' 2>&1 > log and sending me the (compressed) log file off list, it would be helpful. Thanks, Peter -- Peter O'Gorman http://pogma.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users

Re: gnucash linking wrong libffi.dylib

0.0.0. Does gnucash still have a wrapper script that sets DYLD_LIBRARY_PATH? Peter -- Peter O'Gorman http://pogma.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users

Re: NOT SOLVED: libtool woes

paul beard wrote: > Too hasty, it seems. Apache2 upgraded just fine but libidl is still > balking. I looked back and saw your original post - this is a different error entirely: /bin/sh ./libtool --tag=CC --mode=link /usr/bin/gcc-4.0 -O2 -no-cpp-precomp -version-info 0:0:0 -L/opt/local/lib -

Re: libtool woes

ybe I > would see the problem if I removed the libtool port? >From the looks of things MacPorts at some point changed the default setting for CC? If that is the case, it means that people who had built e.g. apr before it was changed, and then tried to build apache after the change will see this breakage. Peter -- Peter O'Gorman http://pogma.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users

Re: libtool woes

btool? you mean the libtool that the project built > for itself? one is calling /opt/local/bin/glibtool, the other is using apr's libtool (/opt/local/share/apr-1/build/libtool). > >> is being called with a different >> compiler (at least a different compiler name) than it was

Re: libtool woes

an it was built with. In these cases the tag *must* be specified --tag=CC or --tag=CXX etc. as GNU libtool can not guess it. Use the CC tag for C sources and the CXX tag for c++. For automake based projects automake adds the --tag when compiling with gnu libtool, for other projects upstream develop