Problems installing Oregano.

[mike clemow]

Okay, I finally got Oregano to build on my machine...  it was not
trivial.  There are some issues with Python versions, etc. which might
require some changes to the SConstruct build file, and/or actually
changing the version of Python that Scons uses by default when
installed via port.  It needs to use the version of Python that
installs as it's dependency and not the one that comes with Mac OS X.
Perhaps the Darwin people don't have this problem?

I'm going to have to join the Oregano-dev list and talk to those guys too.

A little bit further...
Mike

On 10/3/07, mike clemow <gelfmuse at gmail.com> wrote:
> The differences between gmtl portfile and the oregano portfile seem
> pretty straight forward.  I'm going to read more about this in the
> documentation, but it seems like an easy change.  How do I get the
> latest source in the repos?  Does it have to be uploaded there in
> order to test it or can I do that from my local box?
>
> mike
>
>
> On 10/2/07, Ryan Schmidt <ryandesign at macports.org> wrote:
> >
> > On Oct 2, 2007, at 07:21, mike clemow wrote:
> >
> > >> The current oregano port looks relatively straightforward so
> > >> hopefully the software will not have become more difficult to build
> > >> since 0.3.2. You will want to change the depends_lib items from
> > >> lib:X:X form to port:X form (lib:X:X form is deprecated in most
> > >> cases). You may need to add new dependencies if the software has
> > >> grown any new dependencies since 0.3.2. otool -L on the installed
> > >> products can tell you. You should also check whether the cflags and
> > >> cppflags are still necessary; try without them. You should look
> > >> through oregano's ./configure --help to see if any new configure
> > >> arguments should be used.
> > >
> > > Okay, this is all in the portfile, I assume?
> >
> > Right. Type "port edit oregano" or "port cat oregano" to see it.
> >
> > > Out of curiosity, why TCL?
> >
> > Dunno.
> >
> > > I know that there is at least one new dependency.  The problem I'm
> > > having at the moment is that the new package uses scons to build and I
> > > can't get it to run.  I installed the new dependency with port and
> > > also scons, but when I go to run scons in the src directory, it
> > > doesn't run.  Upon investigation I found that scons is trying to run
> > > with /opt/local/bin/python and it's not there because the install was
> > > differentiated from the default Mac OS X installation of python.  The
> > > port version is /opt/ocal/bin/python2.4.  I'm sure scons has some kind
> > > of config file somewhere, but I'll have to dig for it.
> > >
> > > There will be a sconsscript rather than a configure file, but the idea
> > > is the same.  Is there anything special I have to do with the portfile
> > > to build the package with scons, or is that basically the same deal
> > > too?
> >
> > Hmm. I have no information on scons. MacPorts assumes software uses ./
> > configure && make && make install; deviation from that, for example
> > using scons, requires some legwork.
> >
> > Using
> >
> > grep scons */*/Portfile
> >
> > in the dports directory I found that the nsis and gmtl ports are the
> > only ones that appear to use scons at this time. You may want to look
> > to those for examples. gmtl looks to be doing it the more sane way.
> > nsis's method seems more weird.
> >
> >
>
>
> --
> http://shadowofaculture.blogspot.com
>


-- 
http://shadowofaculture.blogspot.com