configure/make/install options for compiling applications from source into /opt/local?
Hello, as the Gnumeric package in the Macports repository does apparently not include the Python plugin (as well as a lot of others), I would like to compile Gnumeric from source myself. Such that it is linked against the libraries already in the /opt/local tree and that it is also installed there, of course. What options must I pass to configure, make and install to achieve this? Such as e.g. --prefix=/opt/local or whatnot? TIA, Sincerely, Wolfgang Keller -- My email-address is correct. Do NOT remove ".nospam" to reply.
Wolfgang, I usually take a slightly different approach to solving problems like this, which is to ask, 'how different is the version I want from the one that's already available from macports?' I approach it that way because, most of the time, someone has already figured out what options need to be passed to configure to be built using macports dependencies and to install to the macports location. In your case, I would remove any existing gnumeric port you have, by doing: 'sudo port clean --all gnumeric'. Then I would modify the existing portfile to add the option you want: 'sudo port edit gnumeric'. Change configure.args to remove the '-- without-python' tag. Build and install your slightly modified gnumeric port via 'sudo port install gnumeric'. If you get this working you could consider submitting any changes you needed to make to the gnumeric Portfile to get it working with python and the other plugins you want as a patch in trac. This method has the advantage of being installable and uninstallable via the 'port' command. Good luck, Frank McPherson On Sep 20, 2006, at 23:29, Wolfgang Keller wrote:
Hello,
as the Gnumeric package in the Macports repository does apparently not include the Python plugin (as well as a lot of others), I would like to compile Gnumeric from source myself. Such that it is linked against the libraries already in the /opt/local tree and that it is also installed there, of course.
What options must I pass to configure, make and install to achieve this?
Such as e.g. --prefix=/opt/local or whatnot?
TIA,
Sincerely,
Wolfgang Keller
-- My email-address is correct. Do NOT remove ".nospam" to reply.
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
as the Gnumeric package in the Macports repository does apparently not include the Python plugin (as well as a lot of others), I would like to compile Gnumeric from source myself. Such that it is linked against the libraries already in the /opt/local tree and that it is also installed there,
of course.
What options must I pass to configure, make and install to achieve this?
Such as e.g. --prefix=/opt/local or whatnot?
--prefix=/opt/local isnt enough: extracted from the output of ./configure --prefix=/opt/local: *snip* checking for GTK... yes checking for GNOME... checking for GNUMERIC... configure: error: Package requirements ( glib-2.0 >= 2.6.0 gobject-2.0 >= 2.6.0 gmodule-2.0 >= 2.6.0 libgsf-1 >= 1.13.2 libgoffice-1 >= 0.2.1 libgoffice-1 < 0.3.0 libxml-2.0 >= 2.4.12 pango >= 1.8.1 pangoft2 >= 1.8.1 gtk+-2.0 >= 2.6.0 libglade-2.0 >= 2.3.6 libgnomeprint-2.2 >= 2.8.2 libgnomeprintui-2.2 >= 2.8.2 libart-2.0 >= 2.3.11 ) were not met: Requested 'libgsf-1 >= 1.13.2' but version of libgsf-1 is 1.10.1 No package 'libgoffice-1' found No package 'libgoffice-1' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GNUMERIC_CFLAGS and GNUMERIC_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. It _does_ find GTK, but _not_ the rest, although all dependencies _are_ installed. All in the same tree. :-( And the error message about libgsf is _wrong_, libgsf in Macports is version 1.14.0. A package named "libgoffice" doesn't exist. A package named goffice with version 0.2.1 does exist and it _is_ installed. Sincerely, Wolfgang Keller -- My email-address is correct. Do NOT remove ".nospam" to reply.
Hello, thanks for your reply.
Then I would modify the existing portfile to add the option you want: 'sudo port edit gnumeric'.
$ sudo port edit gnumeric Error: No EDITOR is specified in your environment That's the kind of things that are not really Mac-like in Macports. Lots of things are "broken by default", there are no manuals how to fix things. Sincerely, Wolfgang Keller -- My email-address is correct. Do NOT remove ".nospam" to reply.
On Sep 21, 2006, at 12:17 PM, Wolfgang Keller wrote:
Then I would modify the existing portfile to add the option you want: 'sudo port edit gnumeric'.
$ sudo port edit gnumeric Error: No EDITOR is specified in your environment
That's the kind of things that are not really Mac-like in Macports.
Well, Macports gives you access to a bunch of non Mac-like software ;-)
Lots of things are "broken by default", there are no manuals how to fix things.
EDITOR is an environment variable that port uses to decide which text editor to invoke when you type 'port edit foo' With bash, you'd want to do something like 'export EDITOR=nano' (or vi or emacs or whatever) We could probably have it default to nano if no editor is specified, though. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
"Daniel J. Luke" <dluke@geeklair.net> writes:
EDITOR is an environment variable that port uses to decide which text editor to invoke when you type 'port edit foo'
With bash, you'd want to do something like 'export EDITOR=nano' (or vi or emacs or whatever)
We could probably have it default to nano if no editor is specified, though.
Oooh. That would be nice for people who are new to Unix, and also for us who assist them. Could that be put on the TODO list, wherever it is? Mark
On Thu, 21 Sep 2006 17:40:45 +0200, Frank McPherson wrote (in message <96800123-C71D-4C2B-A64E-6B9332AB2F96@janusresearch.com>):
Then I would modify the existing portfile to add the option you want: 'sudo port edit gnumeric'. Change configure.args to remove the '-- without-python' tag. Build and install your slightly modified gnumeric port via 'sudo port install gnumeric'.
If you get this working
Doesn't work. Doesn't throw any errors, but doesn't install Python either. No python-loader directory in /opt/local/lib/gnumeric/1.6.3/plugins, no Python console in the Tools menu, and trying a py_<whatever> function in a sheet raises an error. It does seem to install some other plugins however, which weren't installed with the "standard" portfile. Strange. Although the only option I removed was the Python support option. This is apparently just utterly broken. Like _lots_ of ports I've tried, unfortunately. Sincerely, Wolfgang Keller -- My email-address is correct. Do NOT remove ".nospam" to reply.
On Sep 21, 2006, at 10:48, Mark Duling wrote:
"Daniel J. Luke" <dluke@geeklair.net> writes:
EDITOR is an environment variable that port uses to decide which text editor to invoke when you type 'port edit foo'
With bash, you'd want to do something like 'export EDITOR=nano' (or vi or emacs or whatever)
We could probably have it default to nano if no editor is specified, though.
Oooh. That would be nice for people who are new to Unix, and also for us who assist them. Could that be put on the TODO list, wherever it is?
Seeing as Wolfgang Keller was whining about not being Mac-like, why not go all the way? TextMate and BBEdit have command line tools ('mate' and 'bbedit') that launch the GUI editor. Only half jokingly, -landonf
On Sep 21, 2006, at 2:41 PM, Landon Fuller wrote:
On Sep 21, 2006, at 10:48, Mark Duling wrote:
"Daniel J. Luke" <dluke@geeklair.net> writes:
EDITOR is an environment variable that port uses to decide which text editor to invoke when you type 'port edit foo'
With bash, you'd want to do something like 'export EDITOR=nano' (or vi or emacs or whatever)
We could probably have it default to nano if no editor is specified, though.
Oooh. That would be nice for people who are new to Unix, and also for us who assist them. Could that be put on the TODO list, wherever it is?
Seeing as Wolfgang Keller was whining about not being Mac-like, why not go all the way? TextMate and BBEdit have command line tools ('mate' and 'bbedit') that launch the GUI editor.
TextMate and BBEdit don't come with the OS install, though. I suppose we could use TextEdit, though (open -e), or the default text editor (open -t) ... (mostly jokingly) -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On Sep 21, 2006, at 1:53 PM, Wolfgang Keller wrote:
This is apparently just utterly broken.
Well, it just means that the simple modifications that were suggested as a possible fix for you are insufficient for what you want it to do. You can either: 1. Learn how to add the functionality you want to the port (and hopefully contribute it back) or 2. File a bug requesting the additional functionality you want (and when the volunteer who maintains the port gets some time, he/she might add it for you).
Like _lots_ of ports I've tried, unfortunately.
If something is broken, please file a bug report (and assign it to the port's maintainer). No one is getting paid to make this stuff work for you (we're all volunteers), and we haven't gotten an automated build system set up (yet) to help us catch more errors - so there are bound to be a few ports that have problems now and then. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On Sep 21, 2006, at 1:48 PM, Mark Duling wrote:
"Daniel J. Luke" <dluke@geeklair.net> writes:
EDITOR is an environment variable that port uses to decide which text editor to invoke when you type 'port edit foo'
With bash, you'd want to do something like 'export EDITOR=nano' (or vi or emacs or whatever)
We could probably have it default to nano if no editor is specified, though.
Oooh. That would be nice for people who are new to Unix, and also for us who assist them. Could that be put on the TODO list, wherever it is?
Or it could be filed as an enhancement bug :) -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On Sep 21, 2006, at 20:41, Landon Fuller wrote:
On Sep 21, 2006, at 10:48, Mark Duling wrote:
"Daniel J. Luke" <dluke@geeklair.net> writes:
EDITOR is an environment variable that port uses to decide which text editor to invoke when you type 'port edit foo'
With bash, you'd want to do something like 'export EDITOR=nano' (or vi or emacs or whatever)
We could probably have it default to nano if no editor is specified, though.
Oooh. That would be nice for people who are new to Unix, and also for us who assist them. Could that be put on the TODO list, wherever it is?
Seeing as Wolfgang Keller was whining about not being Mac-like, why not go all the way? TextMate and BBEdit have command line tools ('mate' and 'bbedit') that launch the GUI editor.
Absolutely. Here's how I do just that: http://svn.haxx.se/users/archive-2006-07/0848.shtml (That was in response to a question on the Subversion mailing list but it applies just as well to MacPorts or any other Unix command- line utility that uses the EDITOR environment variable.)
"Daniel J. Luke" <dluke@geeklair.net> writes:
Or it could be filed as an enhancement bug :)
Yeah, but let's be honest and just admit that even "we" often ignore the bug tracking system much of the time. There are probably RFE's out there either entirely impractical or undesirable, but still they sit there actually thinking anyone cares that they exist. If there isn't some way for an RFE to graduate from Trac ticket purgatory to "like to get done if possible in the next 2 or 3 releases" status maybe it isn't worth the effort of making a ticket to begin with. Mark
On Sep 21, 2006, at 3:56 PM, Mark Duling wrote:
"Daniel J. Luke" <dluke@geeklair.net> writes:
Or it could be filed as an enhancement bug :)
Yeah, but let's be honest and just admit that even "we" often ignore the bug tracking system much of the time. There are probably RFE's out there either entirely impractical or undesirable, but still they sit there actually thinking anyone cares that they exist. If there isn't some way for an RFE to graduate from Trac ticket purgatory to "like to get done if possible in the next 2 or 3 releases" status maybe it isn't worth the effort of making a ticket to begin with.
Well, with trac, we can assign tickets to milestones (and then watch the graphs fill up as we close bugs for each milestone) ... but I get your point. The best way to make sure a change makes it into a release is to code it up and submit the patch (and even then, the submitter probably has to bug people to review and commit it). -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
participants (6)
-
Daniel J. Luke
-
Frank McPherson
-
Landon Fuller
-
Mark Duling
-
Ryan Schmidt
-
Wolfgang Keller