Re: recommended dependencies?
On 13 Feb 2007, at 01:04, Ryan Schmidt wrote:
On Feb 12, 2007, at 11:12, Mike Roberts wrote:
Then, I would say that you should have either an +rtf variant, or a
+no_rtf variant, but never both. (What would it do if you did not
specify any variant?)
specifying both would have to be disallowed.
my proposal is that the lack of a variant would be an indication that
the user has no preference and a port-specific default can be used.
Ok. Consider a port that has a variant +with_rtf and, by your
request, also +without_rtf. The user specifies neither of these
variants. You say the default should be one or the other. Let's say
that the default is to include RTF support. So the +with_rtf
variant would do nothing different? Would contain no code at all?
Doesn't that seem weird?
Here is a quick example of how a port may work:
configure.args --enable-foo --prefix=${prefix} # --prefix in here
only for the example
variant no_foo {
configure.args-delete --enable-foo
configure.args-append --disable-foo # this line is often missing
}
And how I would like to see the above port written:
configure.args --prefix=${prefix}
default-variants +enable_foo
variant enable_foo conflicts disable_foo {
configure.args-append --enable-foo
}
variant disable_foo conflicts enable_foo {
configure.args-append --disable-foo
}
The second version of the same file does the same thing, but I find
that it is easier to work with. Note also that if the line that is
commented this line is often missing is missing, then the port may
install in a non-deterministic way, installing with foo enabled
because the package's configure script auto-selects that.
I have never used the variants.conf file so I have no comment on
that
feature. Well, maybe I do: the comment would be that variants vary
from port to port, so I can't see any usefulness in a global way to
specify variants that should be used for all ports.
Many ports (particularly for web applications) require that a
database be installed. Given that MacPorts supports at least 7
different relational databases, standard variant names are useful to
ensure that the database that I want to use for some particular port
is used instead of the database that the port developer thought was
best (again, a number of open-source web applications can run on
mysql3/4/5 or postgresql7/8.0/8.1/8.2 or sqlite or ... If I want 1
database server running then I need to be able to say: use mysql4 for
all these applications...)
global variants such as darwin_8 exist and seem to be useful. their
usefulness diminishes beyond those few pre-defined names but i don't
believe this has to be the case.
However, variants like darwin_8 and macosx are auto-selected by the
MacPorts infrastructure without the need to specify them in the
variants.conf file.
You say it doesn't have to be the case that only these few variants
be useful globally. To you have a specific example of another kind
of variant that would be useful globally? I believe I saw that
gentoo has this concept too, and I wasn't sure how it was useful
there either.
Variants that are set to ensure that other ports are aware that
certain capabilities exist on the system and should be taken
advantage of would be useful, such as +with_gnome if GNOME is
installed or +with_kde if KDE is installed or
+with_postgresqlversion if postgresql version version is
installed would all be useful default variants.
Randall Wood
[EMAIL PROTECTED]
The rules are simple: The ball is round. The game lasts 90 minutes.
All the
rest is just philosophy.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gcc 3.3 fails to build: cannot exec `cc1'
On Thu, Feb 15, 2007 at 12:03:10AM +0100, Elias Pipping wrote: $gcc-3.3 -o test1 test.c $ $./test1 Hello world works just fine for me. Presumably you're running on a PPC Mac? -- Mike ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Digging myself a gnucash hole after upgrading other ports
I had to uninstall and clean both goffice and gnucash, then reinstall both. Vince McGarry On Feb 14, 2007, at 11:41 PM, Kurt L wrote: Correction: my upgrade command was % sudo port -f -n upgrade gnucash Kurt Better is the natural enemy of good enough On Wed, 14 Feb 2007 21:27:00 -0800, 'Kurt L' ([EMAIL PROTECTED]) said: Hello, I had a more-or-less working copy of gnucash 2.0.4, and then decided to upgrade a fairly substantial list of outdated ports. Port chugged along for a couple of hours, and eventually all of the outdated ports were upgraded. However, when I tried running gnucash again afterwards I got this kind of error message in the xterm window: Computer$ gnucash dyld: Library not loaded: /opt/local/lib/libgoffice-1.2.dylib Referenced from: /opt/local/bin/gnucash-bin Reason: image not found Trace/BPT trap Computer$ I reasoned that gnucash had been built with a dependency on an outdated library, so thought that perhaps forcing gnucash to build as though it were an upgrade would get it to notice the current libraries and eliminate this problem... so I entered % sudo port -f -n gnucash Well, the upgrade failed spectacularly, with a lengthy list of modules. I think that this is the nub of it here: Error: Target com.apple.build returned: shell command cd /opt/local/var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate _dports_gnome_gnucash/work/gnucash-2.0.4 make all returned error 2 This was followed by some pretty indecipherable module linking lists, etc. Any ideas on where to proceed from here? It feels like I'm just digging a hole deeper and deeper... should I try an uninstall gnucash, and then install gnucash? Suggestions welcome. Kurt L. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Digging myself a gnucash hole after upgrading other ports
Can you show us the indecipherable output? Maybe one of us can decipher it. Thank you for your willingness to help. Here it is: $ sudo port -f -n upgrade gnucash Password: --- Fetching gnucash --- Verifying checksum(s) for gnucash --- Extracting gnucash --- Configuring gnucash --- Building gnucash with target all Error: Target com.apple.build returned: shell command cd /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_gnome_gnucash/work/gnucash-2.0.4 make all returned error 2 Command output: /bin/sh ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../.. -I../../../.. -I../../../.. -I../../../../lib/libgsf-1.12.3 -I../../../../lib/goffice-0.0.4 -I../../../../lib/goffice-0.0.4 -DXTHREADS -DORBIT2=1 -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/opt/local/include/libxml2 -I/opt/local/include/pango-1.0 -I/opt/local/include/freetype2 -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/libpng12 -I/usr/X11R6/include -I/opt/local/include/libglade-2.0 -I/opt/local/include/libgnomeprint-2.2 -I/opt/local/include/libart-2.0 -I/opt/local/include/gconf/2 -I/opt/local/include/orbit-2.0 -I/opt/local/include/libgnomeui-2.0 -I/opt/local/include/libgnome-2.0 -I/opt/local/include/libgnomecanvas-2.0 -I/opt/local/include/libbonoboui-2.0 -I/opt/local/include/gnome-vfs-2.0 -I/opt/local/lib/gnome-vfs-2.0/include -I/opt/local/include/gnome-keyring-1 -I/opt/local/include/libbonobo-2.0 -I/opt/local/include/bonobo-activation-2.0 -I/opt/local/include/libgsf-1 -I/opt/local/include/gnome-vfs-module-2.0 -L/opt/local/lib -I/opt/local/include -L/opt/local/lib -I/opt/local/include -g -pg -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2 -c -o xl-surface.lo xl-surface.c gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../.. -I../../../.. -I../../../.. -I../../../../lib/libgsf-1.12.3 -I../../../../lib/goffice-0.0.4 -I../../../../lib/goffice-0.0.4 -DXTHREADS -DORBIT2=1 -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/opt/local/include/libxml2 -I/opt/local/include/pango-1.0 -I/opt/local/include/freetype2 -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/libpng12 -I/usr/X11R6/include -I/opt/local/include/libglade-2.0 -I/opt/local/include/libgnomeprint-2.2 -I/opt/local/include/libart-2.0 -I/opt/local/include/gconf/2 -I/opt/local/include/orbit-2.0 -I/opt/local/include/libgnomeui-2.0 -I/opt/local/include/libgnome-2.0 -I/opt/local/include/libgnomecanvas-2.0 -I/opt/local/include/libbonoboui-2.0 -I/opt/local/include/gnome-vfs-2.0 -I/opt/local/lib/gnome-vfs-2.0/include -I/opt/local/include/gnome-keyring-1 -I/opt/local/include/libbonobo-2.0 -I/opt/local/include/bonobo-activation-2.0 -I/opt/local/include/libgsf-1 -I/opt/local/include/gnome-vfs-module-2.0 -L/opt/local/lib -I/opt/local/include -L/opt/local/lib -I/opt/local/include -g -pg -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2 -c xl-surface.c -fno-common -DPIC -o .libs/xl-surface.o /bin/sh ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../.. -I../../../.. -I../../../.. -I../../../../lib/libgsf-1.12.3 -I../../../../lib/goffice-0.0.4 -I../../../../lib/goffice-0.0.4 -DXTHREADS -DORBIT2=1 -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/opt/local/include/libxml2 -I/opt/local/include/pango-1.0 -I/opt/local/include/freetype2 -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/libpng12 -I/usr/X11R6/include -I/opt/local/include/libglade-2.0 -I/opt/local/include/libgnomeprint-2.2 -I/opt/local/include/libart-2.0 -I/opt/local/include/gconf/2 -I/opt/local/include/orbit-2.0 -I/opt/local/include/libgnomeui-2.0 -I/opt/local/include/libgnome-2.0 -I/opt/local/include/libgnomecanvas-2.0 -I/opt/local/include/libbonoboui-2.0 -I/opt/local/include/gnome-vfs-2.0 -I/opt/local/lib/gnome-vfs-2.0/include -I/opt/local/include/gnome-keyring-1 -I/opt/local/include/libbonobo-2.0 -I/opt/local/include/bonobo-activation-2.0 -I/opt/local/include/libgsf-1 -I/opt/local/include/gnome-vfs-module-2.0 -L/opt/local/lib -I/opt/local/include -L/opt/local/lib -I/opt/local/include -g -pg -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2 -c -o gog-contour-prefs.lo gog-contour-prefs.c gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../.. -I../../../.. -I../../../.. -I../../../../lib/libgsf-1.12.3
Cyrus Imap Cyrus SASL
Hello everyone! Of the small list of ports I maintain, I consider the Cyrus imap mail server related ones to be the most important (cyrus-imapd cyrus-sasl2). However, I currently don't have the time nor appropriate hardware to dedicate to full maintainership of such a complex port (I'm mostly referring to cyrus-imapd here), which is why I added openmaintainer as one of the caretakers. Instead of letting it die a slow and abandoned death, I would like to ask publicly for help in bringing it up to date. I would like to encourage anyone caring about cyrus and savvy enough on the subject to step up and write a patch against the existing Portfile, taking care of as many aspects of its build installation process as possible: first and foremost, building on Intel hardware; version upgrade, of course; variants; startup item re-factoring if needed; system user creation (needs adapting to Tiger, I believe); others... (the post-destroot stage I originally wrote is rather complex, so I'd recommend going over it before venturing to tackle cyrus-imapd's installation). As the final note in the very Portfile says: Port is itself bare bones, suport for many other things could be added (maybe as variants), so suggest away!. So if you're feeling adventurous enough to enhance the port even further, please by all means by my guest! Anyone volunteering please take a look at http://trac.macports.org/projects/macports/ticket/7863 and post your proposed patches against the Portfile as attachments to that ticket (better than sending them to me personally, I might loose track of them). I haven't found any other valid open tickets for cyrus-imapd so I'd like to concentrate all discussion there. I'll review them ASAP and will commit the most complete integral one after discussion consensus with participating parties is reached. All this commentary also applies to cyrus-sasl2, of course, but that should be a much simpler port. Please concentrate all discussion for that port on ticket http://trac.macports.org/projects/macports/ticket/11386 Thanks in advance for your time and help! Much regards, -jmpp PS: If you, reader, are one of those who has already sent me patches and/or suggestions for cyrus-imapd, please excuse me for not having acted on them in due time, I've been most busy on one hand and haven't used cyrus in a while. May I ask you to please step up again and submit your work to the referenced tickets? Thanks! ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: openmotif installation error
On Feb 15, 2007, at 07:47, Georg Otto wrote: I have a problem intsalling openmotif. It gives me the following error: [snip] In file included from /usr/X11R6/include/X11/Xft/Xft.h:35, from TextIn.c:91: /opt/local/include/freetype2/freetype/freetype.h:20:2: #error `ft2build.h' hasn 't been included yet! /opt/local/include/freetype2/freetype/freetype.h:21:2: #error Please always use macros to include FreeType header files. /opt/local/include/freetype2/freetype/freetype.h:22:2: #error Example: /opt/local/include/freetype2/freetype/freetype.h:23:2: #error #include ft2bu ild.h /opt/local/include/freetype2/freetype/freetype.h:24:2: #error #include FT_FRE ETYPE_H make[3]: *** [TextIn.lo] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Yes, this problem has been reported before: http://www.opendarwin.org/pipermail/darwinports/2006-March/032836.html The bug was reported against openmotif 2.3.0 beta 1, and closed without any action being taken because openmotif 2.3.0 beta 2 became available: http://trac.macosforge.org/projects/macports/ticket/7764 It was reported again in another bug which may include a fix and is still open: http://trac.macosforge.org/projects/macports/ticket/8975 The openmotif port has no maintainer, which is probably why this hasn't been fixed yet. Please try the solution in ticket 8975 and see if it works for you. If so, I can commit the fix to the port. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
hang at gnupg configuration
Hello to all. I have the latest version of MacPorts (base version 1.320) and am running 10.4.8 on an iMac G5. I am trying to install duplicity using MacPorts and have run into a problem with the installation of gnupg (which duplicity requires). Namely, it hangs during configuration. In the Activity Monitor, I can see that tar is using about half the CPU. This looks very similar to bug #10227 http://trac.macosforge.org/projects/macports/ticket/10227, but the gnupg portfile I have seems to have been updated as suggested there, and I am at a loss. Like [EMAIL PROTECTED] from that thread, I have found that manually executing cd and configure works. However, despite my having done so, when the gnupg configuration is concluded and I reattempt to install duplicity, I get the same hang-up as before, at Configuring gnupg. I've googled, and searched through the archives for this list through September, but found nothing. Can anyone help? Phil ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: openmotif installation error
Hi I just commited a patch. Tell me if it works yves Le 07-02-15 à 08:47, Georg Otto a écrit : Hi, I have a problem intsalling openmotif. It gives me the following error: ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Digging myself a gnucash hole after upgrading other ports - resolved
Thanks for the tip, Vince. I did this and now it is working again. I guess what I learned from this is that if one has a problem with top-level port A not loading dependent port B, clean and uninstall both ports, and then re-install both ports. Kurt L. On Thu, 15 Feb 2007 07:35:50 -0600, McGarry Vince ([EMAIL PROTECTED]) said: I had to uninstall and clean both goffice and gnucash, then reinstall both. Vince McGarry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
qt3-mac 3.3.7 build failed (while making libqtwidgets.dylib)
Hi, When trying to build qt3-mac 3.3.7 on MacBook with Xcode 2.4.1, I got the following error: --- Error: Target com.apple.build returned: shell command cd /opt/local/var/db/dports/build/_opt_local_var_db_dports_ sources_rsync.rsync.darwinports.org_dpupdate_dports_aqua_qt3-mac/work/qt-mac-free-3.3.7 QMAKESPEC='' QTDIR='' D YLD_LIBRARY_PATH=/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupd ate_dports_aqua_qt3-mac/work/qt-mac-free-3.3.7/lib make symlinks src-qmake src-moc sub-src sub-tools returned err or 2 Command output: ../../../../include/qaccessible.h:232: warning: 'struct QAccessibleInterface' has virtual functions but non-virtual destructor ../../../../include/qaccessible.h:266: warning: 'struct QAccessibleFactoryInterface' has virtual functions but non- virtual destructor main.cpp:9: warning: 'class AccessibleFactory' has virtual functions but non-virtual destructor c++ -c -pipe -I/opt/local/include -Wall -W -Os -fPIC -DQT_ACCESSIBILITY_SUPPORT -DQT_TABLET_SUPPORT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_PLUGIN -DQT_SHARED -I/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync .rsync.darwinports.org_dpupdate_dports_aqua_qt3-mac/work/qt-mac-free-3.3.7/mkspecs/macx-g++ -I. -I../../../../inclu de -I/System/Library/Frameworks/OpenGL.framework/Versions/A/Headers -I/System/Library/Frameworks/AGL.framework/Vers ions/A/Headers -I.moc/release-shared-mt/ -o .obj/release-shared-mt/qaccessiblewidget.o qaccessiblewidget.cpp ../../../../include/qaccessible.h:232: warning: 'struct QAccessibleInterface' has virtual functions but non-virtual destructor ../../../../include/qaccessible.h:266: warning: 'struct QAccessibleFactoryInterface' has virtual functions but non- virtual destructor c++ -c -pipe -I/opt/local/include -Wall -W -Os -fPIC -DQT_ACCESSIBILITY_SUPPORT -DQT_TABLET_SUPPORT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_PLUGIN -DQT_SHARED -I/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync .rsync.darwinports.org_dpupdate_dports_aqua_qt3-mac/work/qt-mac-free-3.3.7/mkspecs/macx-g++ -I. -I../../../../inclu de -I/System/Library/Frameworks/OpenGL.framework/Versions/A/Headers -I/System/Library/Frameworks/AGL.framework/Vers ions/A/Headers -I.moc/release-shared-mt/ -o .obj/release-shared-mt/qaccessiblemenu.o qaccessiblemenu.cpp ../../../../include/qaccessible.h:232: warning: 'struct QAccessibleInterface' has virtual functions but non-virtual destructor ../../../../include/qaccessible.h:266: warning: 'struct QAccessibleFactoryInterface' has virtual functions but non- virtual destructor qaccessiblemenu.cpp: In member function 'virtual QString QAccessiblePopup::text(QAccessible::Text, int) const': qaccessiblemenu.cpp:80: warning: 'id' may be used uninitialized in this function test -d ../../../accessible/ || mkdir -p ../../../accessible/ rm -f libqtwidgets.dylib c++ -headerpad_max_install_names -bundle -o libqtwidgets.dylib .obj/release-shared-mt/main.o .obj/release-shared-mt /qaccessiblewidget.o .obj/release-shared-mt/qaccessiblemenu.o -L/opt/local/lib -L/opt/local/var/db/dports/build/_ opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_aqua_qt3-mac/work/qt-mac-free-3.3.7/lib -lqt-mt -lz -framework OpenGL -framework AGL /usr/bin/ld: warning -prebind has no effect with -bundle /usr/bin/ld: Undefined symbols: QAccessible::queryAccessibleInterface(QObject*, QAccessibleInterface**) QAccessibleObject::queryInterface(QUuid const, QUnknownInterface**) QAccessibleObject::QAccessibleObject(QObject*) QAccessibleObject::~QAccessibleObject() QAccessibleObject::object() const QAccessibleObject::isValid() const typeinfo for QAccessibleObject non-virtual thunk to QAccessibleObject::queryInterface(QUuid const, QUnknownInterface**) non-virtual thunk to QAccessibleObject::isValid() const collect2: ld returned 1 exit status make[3]: *** [../../../accessible/libqtwidgets.dylib] Error 1 make[2]: *** [sub-widgets] Error 2 make[1]: *** [sub-accessible] Error 2 make: *** [sub-plugins] Error 2 Warning: the following items did not execute (for qt3-mac): com.apple.activate com.apple.build com.apple.destroot c om.apple.archive com.apple.install Error: Status 1 encountered during processing. --- How do I fix this problem? Thank you, Takashi Nishigaya ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
