Re: cmake upgrade failure/success ?machine-dependant...
It looks like gmake is missing the required libintl. Perhaps try reinstalling gmake? The system gmake usually works fine, but perhaps CMake picked up the MacPorts gmake from your environment instead. Chris -- Sent from my iPod On Nov 18, 2010, at 7:19 AM, Gregory Dodwell gregree...@gmail.com wrote: OSX 10.6.5 upgraded to latest Macports successfully on both machines (iMac 7,1; MacBookPro5,3). Ran sudo port upgrade outdated with no failure on laptop. Same command failed on iMac. (The iMac, being an older, non Pro machine cannot run OSX in 64bit mode, despite similar Core2 Duo processor to laptop.) Here's the terminal output: bash-3.2$ sudo port upgrade outdated --- Computing dependencies for cmake --- Fetching cmake --- Verifying checksum(s) for cmake --- Extracting cmake --- Applying patches to cmake --- Configuring cmake Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details) Log for cmake is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/main.log Error: Unable to upgrade port: 1 To report a bug, see http://guide.macports.org/#project.tickets Please see snippets from the main.log: version:1 :msg:main --- Computing dependencies for cmake:info:main .:debug:main Searching for dependency: libidn :debug:main Found Dependency: receipt exists for libidn :debug:main Searching for dependency: openssl :debug:main Found Dependency: receipt exists for openssl :msg:main :debug:main Executing org.macports.main (cmake) :msg:main --- Fetching cmake :debug:fetch fetch phase started at Thu Nov 18 22:45:29 EST 2010 :debug:fetch Executing org.macports.fetch (cmake) :msg:fetch --- Verifying checksum(s) for cmake :debug:checksum checksum phase started at Thu Nov 18 22:45:29 EST 2010 :debug:checksum Executing org.macports.checksum (cmake) :info:checksum --- Checksumming cmake-2.8.3.tar.gz :debug:checksum Correct (md5) checksum for cmake-2.8.3.tar.gz :debug:checksum Correct (sha1) checksum for cmake-2.8.3.tar.gz :debug:checksum Correct (rmd160) checksum for cmake-2.8.3.tar.gz :msg:checksum --- Extracting cmake :debug:extract extract phase started at Thu Nov 18 22:45:29 EST 2010 :debug:extract Executing org.macports.extract (cmake) :info:extract --- Extracting cmake-2.8.3.tar.gz :debug:extract setting option extract.args to '/opt/local/var/macports/distfiles/cmake/cmake-2.8.3.tar.gz' :debug:extract Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/work/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' MACOSX_DEPLOYMENT_TARGET='10.6' :debug:extract Assembled command: 'cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/work /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/cmake/cmake-2.8.3.tar.gz' | /usr/bin/gnutar --no-same-owner -xf -' :debug:patch patch phase started at Thu Nov 18 22:45:32 EST 2010 :debug:patch Executing org.macports.patch (cmake) :msg:patch --- Applying patches to cmake :info:patch --- Applying /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/cmake/files/patch-CMakeFindFrameworks.cmake.diff :debug:patch Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/work/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' MACOSX_DEPLOYMENT_TARGET='10.6' :debug:patch Assembled command: 'cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/work/cmake-2.8.3 /usr/bin/patch -p0' :info:patch patching file Modules/CMakeFindFrameworks.cmake :debug:patch Executing proc-post-org.macports.patch-patch-0 :msg:patch --- Configuring cmake :debug:patch Using compiler 'Mac OS X gcc 4.2' :debug:configure configure phase started at Thu Nov 18 22:45:32 EST 2010 :debug:configure Executing org.macports.configure (cmake) :debug:configure Environment: CPATH='/opt/local/include' CFLAGS='-O2 -arch x86_64' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-O2 -arch x86_64' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.6' CMAKE_PREFIX_PATH='/opt/local' CXX='/usr/bin/g++-4.2' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/work/.CC_PRINT_OPTIONS' F90FLAGS='-O2 -m64' LDFLAGS='-L/opt/local/lib -arch x86_64' FCFLAGS='-O2 -m64' OBJC='/usr/bin/gcc-4.2' INSTALL='/usr/bin/install -c' CMAKE_INCLUDE_PATH='/opt/local/include/ncurses' CMAKE_LIBRARY_PATH='/opt/local/lib' FFLAGS='-O2 -m64' OBJCFLAGS='-O2 -arch x86_64' CC_PRINT_OPTIONS='YES' CC='/usr/bin/gcc-4.2' :debug:configure Assembled command: 'cd
Re: Solving some Symbol not found problems for libJPEG, libTIFF, libGL, libPng
You could also use DYLD_FALLBACK_LIBRARY_PATH. I had to use that to avoid Apple's libJPEG getting in the way of apps that expected the libjpeg port. See the man page for dlopen() for details. Chris -- Sent from my iPod On Nov 18, 2010, at 2:57 PM, Robert Baruch robert.c.bar...@gmail.com wrote: Hi all, To save some of you some time, if you run something and you get an error like this: dyld: Symbol not found: _gll_noop Referenced from: /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL Expected in: /opt/local/lib/libGL.dylib or this: dyld: Symbol not found: __cg_jpeg_resync_to_restart Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO Expected in: /opt/local/lib/libJPEG.dylib or this: dyld: lazy symbol binding failed: Symbol not found: __cg_TIFFSetErrorHandler Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO Expected in: /opt/local/lib/libTIFF.dylib or this: dyld: Symbol not found: __cg_png_create_info_struct Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO Expected in: /optlocal/lib/libPng.dylib Then congratulations, you've discovered that OSX and MacPorts are incompatible with each other for these libraries! For example, Macport's libjpeg contains the symbol _jpeg_resync_to_restart, but not what Apple is looking for, __cg_jpeg_resync_to_restart. I have seen several solutions, including removing any DYLD_LIBRARY_PATH (which doesn't help when you don't have it set), and removing the offending macports library, which doesn't help when it will just get reinstalled when you try to install a port which has those libraries as a dependency. The solution that worked for me was this (note that if you don't have a particular /opt/local/lib library then you don't need that line) sudo ln -sf /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib /opt/local/lib/libGL.dylib sudo ln -sf /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib /opt/local/lib/libpng.dylib sudo ln -sf /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib /opt/local/lib/libtiff.dylib sudo ln -sf /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib /opt/local/lib/libjpeg.dylib Why does this work? Because for whatever reason, when Apple requests libJPEG.dyld, whatever system searches for it finds /opt/local/lib/libjpeg.dyld because the search is case insensitive. For a Unix operating system. Go figure. The lines above will force any program looking for libjpeg.dyld to be redirected to Apple's libJPEG.dyld. But wait, what if you WANT Macport's libjpeg.dyld? Sorry, not possible unless you statically link your program to libjpeg.a. And since I've never done that before, I can't help you if you want to do that :( --Rob ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: unison 2.32 declared stable
On Oct 16, 2009, at 9:34 AM, Joerg van den Hoff wrote: unison 2.32 has been finally declared stable a few weeks ago. any chance to see this version soon in macports? It looks like it takes some patching to get 2.32 to work properly on Snow Leopard. See http://trac.macports.org/ticket/21862 Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Using macports dylibs without macports
On Sep 28, 2009, at 5:23 PM, Paul Dennis Simonson wrote: All of the *.a files build just fine using MacPorts. I build and link my programs using XCode 3.2, and the build is successful when I build a command line utility and link to the *.a files. However, the program is looking for the *.dylib files when I try to run the program on another computer and of course fails to find them! On Sep 28, 2009, at 1:56 PM, Ryan Schmidt wrote: On Sep 28, 2009, at 12:27, Paul Dennis Simonson wrote: Is there any way to force MacPorts to make a static library that we can link to and distribute easily? It used to do this!!! Ports should install static and dynamic libraries wherever possible. If you find ports that are missing one or the other, please file tickets for those ports. It might also depend on how the linking takes place. When both static and dynamic libraries are available, the linker links with the dynamic libraries by default. I know I've had to provide the full path to the library archive, so you might need to link using /opt/local/lib/ libfreeimage.a instead of -L/opt/local/lib -lfreeimage. Trying to make every port force static libraries might not be feasible, as it would required forcing static linking with all dependencies. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: emacs-app-devel fails to build under Snow Leopard
On Sep 4, 2009, at 4:50 PM, Artemio Gonzalez Lopez wrote: emacs-app-devel does not build under Snow Leopard (yes, I uninstalled first all my ports and rebuilt from scratch with Snow Leopard). More specifically, the error I get is: It looks like there are larger issues trying to build Cocoa emacs on Snow Leopard. I tried a couple small changes, but getting the Cocoa build working on Snow Leopard looks like it's going to take some upstream fixes by someone much more familiar with the code. I'll upstate status to the existing ticket. http://trac.macports.org/attachment/ticket/20244 Thanks, Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: sysadmin: is there a manifesto on environment settings for macports?
On Saturday, April 11, 2009, at 08:17PM, Rainer Müller rai...@macports.org wrote: Darren Weber wrote: I've had some difficulty with the VTK library when I try to get dynamic libraries working under macports. See http://trac.macports.org/ticket/19000 I could use some help with understanding how to get rpath working under macports (if that is THE way to go), given that VTK uses CMAKE settings to configure the RPATH or the INSTALL_RPATH and the settings that I've tried so far get corrupted during the macports build process because it uses a destroot setting. I've thought about a postdestroot hack using 'install_name_tool' but there may be a better way to get it right. I don't know enough details about this RPATH to be of real help here. But if Debian discourages RPATH as you linked in your previous mail and VTK requires that, how did they get it solved? The variables governing RPATH and install names are similar, but install names are much more important on Mac OS X than RPATH settings are on Linux. Without an install name in a shared library, a Mac OS X executable cannot locate the shared library without relying on environment variables. The VTK 4 port sets the INSTALL_RPATH by setting the CMake variable CMAKE_INSTALL_NAME_DIR. I suspect this is the one you're missing. Things might have changed a bit with VTK 5, I did see some posts mentioning a VTK_INSTALL_NAME_DIR. I think that unless one specifies the install name (RPATH), CMake automatically uses the install destination. That is incorrect when using a destroot, and that's why CMake needs the extra variable. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: VTK port naming conventions
On Monday, April 13, 2009, at 04:49PM, Darren Weber dwe...@macports.org wrote: This is a thread to discuss naming conventions for VTK in macports. Macports has the following VTK ports (as of 04/13/2009): VTK @4.4.2 (graphics) 3D visualization toolkit vtk5 @5.2.1 (graphics, devel) 3D visualization toolkit It might be more clear to rename along the lines of: vtk @5.2.1 vtk-devel @5.4 vtk4 @4.4.2 I'm not sure how best we might handle renaming the existing ports to match this scheme, but it would follow the scheme of keeping the port named without a version as the latest, stable release. I also need to fix the case-sensitive handling of the directory versus the port name. Any thoughts? Many of these separate packages in Debian and FreeBSD probably equate to 'variants' in a macport. That's true. MacPorts provides the extra language bindings in variants rather than separate ports, unless the demand hasn't been made to enable a particular binding either by default or as a variant. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Problem installing vtk
On Monday, March 30, 2009, at 06:09AM, bscuser smarras@gmail.com wrote: Hi there, were you able to solve the problem? If so, how did you do it? I am getting the same error on my Mac OS X 10.5 Please run port sync and try to build again. I patched the VTK 4 sources to fix the build error. http://trac.macports.org/ticket/18696 Hope this helps, Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Problem installing vtk
On Mar 20, 2009, at 8:28 AM, David Trem wrote: May somebody help ? I have a problem installing vtk on MacBook OS X 10.5.6, using macports 1.700 (fresh install). See console output below. [...] /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_graphics_vtk/work/VTK/Rendering/ vtkCocoaGLView.h:11: error: using typedef-name 'NSOpenGLPixelFormatAttribute' after 'enum' /System/Library/Frameworks/AppKit.framework/Headers/NSOpenGL.h:90: error: 'NSOpenGLPixelFormatAttribute' has a previous declaration here make[2]: *** [Rendering/CMakeFiles/vtkRendering.dir/ vtkCocoaRenderWindowInteractor.o] Error 1 make[1]: *** [Rendering/CMakeFiles/vtkRendering.dir/all] Error 2 make: *** [all] Error 2 I'll take look ... I think I might have only built the x11 variant. I might have missed another required Leopard fix for the Cocoa windowing. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: install emacs-app failed on Tiger, ppc
On Jan 28, 2009, at 1:56 PM, Ryan Schmidt wrote: On Jan 28, 2009, at 09:33, Joe Davison wrote: I'm running 10.4.11 on a PowerPC G4 (Quicksilver) Today I tried sudo port -v install emacs-app and got a, to me, bizarre failure. I captured both the output from port -v and the config.log. Examining the latter shows that, for some reason when it checked the executable generated by gcc4 it was for intel, not ppc -- possibly an error in flags passed to it? Confirmed on my 10.4 Power Mac. I filed a ticket for you: http://trac.macports.org/ticket/18253 Thanks for noting the bug ... that compile script in the emacs-app port has been carried around for a while. At one point I thought about trying to pull everything out and reconstructing the options on a standard configure line, and then we could more easily control the build options. However, given that emacs-app development has now been folded into the official emacs development, you might want to check the emacs-app- devel port instead. It's a bit more bleeding edge, but it's a lot easier to control settings since it relies on the configuration options rather than a hard-coded script. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Patch of doxygen failed
On Sep 29, 2008, at 8:08 AM, David Evans wrote: --- Applying patches to doxygen --- Applying /opt/local/var/macports/sources/rsync.macports.org/release/ports/ textproc/doxygen/files/patch-qfiledefs_p.h DEBUG: Environment: DEBUG: Assembled command: 'cd /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_textproc_doxygen/work/doxygen-1.5.6 patch -p0' patching file qtools/qfiledefs_p.h Hunk #1 FAILED at 56. 1 out of 1 hunk FAILED -- saving rejects to file qtools/ qfiledefs_p.h.rej I updated the Portfile for 1.5.7, and it works fine on Leopard. Unfortunately I no longer have access to a Tiger system, and it looks like the patch might not be needed anymore. Please report any problems. On a similar note, I finally put together a patch to build the documentation only as a variant. (See https://trac.macports.org/ticket/14421) . This actually makes it much easier to install doxygen, but it conflicts somewhat with the include everything by default approach. What are the thoughts on only bringing in texlive and ghostscript as part of a docs variant? Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Patch of doxygen failed
On Monday, September 29, 2008, at 08:08AM, David Evans [EMAIL PROTECTED] wrote: --- Applying patches to doxygen --- Applying /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/doxygen/files/patch-qfiledefs_p.h DEBUG: Environment: DEBUG: Assembled command: 'cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_doxygen/work/doxygen-1.5.6 patch -p0' patching file qtools/qfiledefs_p.h Hunk #1 FAILED at 56. 1 out of 1 hunk FAILED -- saving rejects to file qtools/qfiledefs_p.h.rej Yup ... I didn't include everything that was needed when I tried to sanitize my portfile to update the port. (I'm also trying to remove the tex dependency to make a lighter-weight install.) I'll get this fixed tonight. Thanks, Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Gnu Emacs.app: Problem with special characters (alt-key)
On Feb 25, 2008, at 4:04 PM, Erik Norgaard wrote: I don't know if this is the right place to direct this problem, but I have built the emacs-app from ports, just updated to the latest version today but problem persists: The best place to investigate this would be either the macosx-emacs mailing list or the Sourceforge project page for Emacs.app. http://email.esm.psu.edu/mailman/listinfo/macosx-emacs http://emacs-app.sourceforge.net/ Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: libsndfile error
On Wednesday, December 05, 2007, at 05:32PM, Chris Share [EMAIL PROTECTED] wrote: So is there a way to install libsndfile? Can I install an earlier version, or can I install it without FLAC? I'll commit the patch posted in #12009 when I'm back at my Mac tonight. Then you'll just need to do a 'port sync' and libsndfile will install without FLAC. If you need it immediately, you could either patch your local copy of the Portfile or turn off FLAC. The new revision won't use the default variant approach, but if you need it installed today, use port install libsndfile -flac. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: libsndfile error
On Dec 5, 2007, at 6:47 AM, Chris Share wrote: I'm trying to install libsndfile however I'm getting the following error: libsndfile does not work with the current version of FLAC http://trac.macosforge.org/projects/macports/ticket/12009 Of course, now I realize I didn't commit the patch to disable flac. libsndfile needs upstream attention to work with the latest FLAC, so for the meantime it seems that libsndfile simply shouldn't support FLAC. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
MacPorts.org trac theme width
Hi, This is minor nit, but that persistent horizontal scroll bar has been nagging me when viewing the MacPorts website. Do the elements of the theme sum to a width greater than 100%? Resizing my Safari window does nothing to alleviate the fact that the web pages remain just a bit width than the browser window. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
teTeX +nox11 fails due to depspec error
Hi, Using MacPorts 1.430 on a MacBook Pro with 10.4.9, I am unable to build the teTeX +nox11 variant: $ sudo port -v fetch +nox11 Error: Error executing nox11: can't set depends_lib: invalid depspec: Error: Status 1 encountered during processing. http://trac.macports.org/projects/macports/ticket/11819 The regular build works fine. Could there be a bug due to the fact that using this variant results in an empty depends_lib? Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Baffled by output from `port dependents'
On Mar 6, 2007, at 10:51 AM, Mark Dickinson wrote: Any clues as to what's going on would be appreciated. I'm wondering on this too. It seems like I'm getting some left-over cruft: $ port dependents expat | grep apr-util apr-util depends on expat apr-util depends on expat apr-util depends on expat apr-util depends on expat apr-util depends on expat apr-util depends on expat apr-util depends on expat $ port installed apr-util The following ports are currently installed: apr-util @1.2.8_1 (active) So where do the other six dependents come from? Do I just have stale entries in my port registry? Is the dependents command repeating on the same entry? Should dependents include the version number? $ find /opt/local/var/db/dports -name apr-util-* /opt/local/var/db/dports/distfiles/apr-util/apr-util-1.2.7.tar.bz2 /opt/local/var/db/dports/distfiles/apr-util/apr-util-1.2.8.tar.bz2 /opt/local/var/db/dports/packages/darwin/powerpc/apr- util-1.2.8_1.powerpc.tgz /opt/local/var/db/dports/software/apr-util/1.2.8_1/opt/local/lib/ pkgconfig/apr-util-1.pc I certainly find the output rather ambiguous. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: libsndfile and FLAC on 10.3
On Jan 17, 2007, at 9:25 AM, [EMAIL PROTECTED] wrote: http://trac.macports.org/projects/macports/ticket/10905 Please clean your build (port clean libsndfile), and then try using port -v configure build build-libsndfile.txt and attach the resulting text file to the ticket. oops, make that: port clean libsndfile port -v build libsndfile build-libsndfile.txt Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shells/fish fails to install due to checksum mismatch.
On Jan 4, 2007, at 6:57 AM, Mike Roberts wrote: also, while trying to determine the md5sum of the package, i discovered that the md5sum command appears to be missing from the corefiles port. info corefiles suggests that it should be present but i cannot find it in /opt/local/bin. The coreutils port adds a g prefix in order to minimize conflicts with built-in Mac OS X tools: $ port provides `which gmd5sum` /opt/local/bin/gmd5sum is provided by: coreutils $ port provides `which gsha1sum` /opt/local/bin/gsha1sum is provided by: coreutils Mac OS X includes its own md5 command: $ which md5 /sbin/md5 Hope this helps, Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Building doxygen +wizard against qt3-mac or qt3
On Nov 3, 2006, at 1:43 PM, Eric Gorr wrote: I attempted to build doxygen +wizard against the the qt3-mac qt3 port, but got the errors below. Anyone know how to get around this problem? I can confirm that error. It looks like an upstream bug with the doxywizard source. Maybe it needs a newer version of Qt? I'll try the doxygen 1.5.1 source to see if that works. http://svn.macosforge.org/projects/macports/ticket/10985 I'll see if I can figure out how to fix the problem, but in the meantime you should be able to build and run the standard command- line version. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Getting graphviz working...?
On Nov 2, 2006, at 8:21 AM, Eric Gorr wrote:
I was hoping someone could help me get things configured properly
for dot on my Mac running 10.4.8.
I am using dot 2.8
I'm getting the same error, but most of my dot files specify a
specific font. The default Times-Roman font is probably the wrong
choice. This might be an upstream issue that we can resolve my
specifying a different default font in the config file.
http://www.graphviz.org/bugs/b588.html
https://mailman.research.att.com/pipermail/graphviz-devel/
2006/000157.html
This seems to work:
digraph test123 {
node [fontname = Times];
a - b - c;
}
Strangely, Helvetica doesn't work.
http://www.graphviz.org/bugs/b891.html
Chris
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
