On Mon, Nov 05, 2012 at 08:10:21AM -0600, Ryan Schmidt wrote:
>
> > :info:build filter_yadif.c:380: error: ‘asm’ operand has impossible
> > constraints
> > :info:build filter_yadif.c:380: error: ‘asm’ operand has impossible
> > constraints
> > :info:build make[2]: *** [filter_yadif.o] Error 1
>
On Sun, Oct 24, 2010 at 02:33:53PM +0200, Marko Käning wrote:
> Yep, I see. The situation is the same everywhere when it comes to uninstalls.
> ;)
>
> Windows, Linux, MacOSX, ...
huh - uninstall works fine for both rpm (as mentioned previously on this list)
and deb (ubuntu) - dpkg remove/purge -
On Thu, Jun 10, 2010 at 10:59:46AM -0400, Daniel J. Luke wrote:
>
> (doing an upgrade gives the same error after generating the new version's
> archive).
>
> Looks like portuninstall.tcl (line 149) just needs to check for image vs
> direct and do uninstall vs deactivate.
>
unfortunately I don
On Tue, May 18, 2010 at 07:51:16AM -0500, Ryan Schmidt wrote:
>
> On May 18, 2010, at 07:04, Bradley Giesbrecht wrote:
>
> > Maybe local repos is something that should be promoted and made more
> > prominent on the homepage and in the guide?
>
> Personally I've never used a local port repositor
On Mon, Jan 25, 2010 at 04:47:28PM -0700, Ryan Schmidt wrote:
>
> Right, this line is the problem. For correct functionality, it should list
> the full path to the library, i.e.
>
> /opt/local/lib/libiguanaIR.dylib (compatibility version 1.0.0, current
> version 1.0.0)
>
> I don't know h
>
> Comment:
>
> I'd rather make these into real targets than replicate all this
> infrastructure. Also, it might be better to wait until after the images-
> and-archives branch is merged.
>
I dont think this is possible - what would deactivate/uninstall depend on?
they cannot depend on inst
On Thu, May 21, 2009 at 03:43:19AM -0600, Emmanuel Hainry wrote:
>
>
> You should also drop bugfixing for anything not macosx (linux, bsd,
> puredarwin). Jordan's plan would mean you can remove a lot of code from
> base: why are there different gcc default, different x11prefix? Why
> should you c
Hi,
OK - so here is the real deal for solving what extra modules to install with
the base python
port
_ssl.so most definitely should be installed
why??
because in the particular case of _ssl.so there is no "failed to import"
message - as that
is protected in socket.py by try/except - the ob
On Tue, May 05, 2009 at 08:55:46AM -0600, Joshua Root wrote:
> David Osguthorpe wrote:
> > Hi,
> >
> > I know the macports developers dont like using Apple supplied stuff
> > but here is an inverse case - where the system supplied python works
> > but macport
On Tue, May 05, 2009 at 08:55:46AM -0600, Joshua Root wrote:
> >>result = func(*args)
> >> File
> >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/urllib2.py",
> >> line 1140, in unknown_open
> >>raise URLError('unknown url type: %s' % type)
> >> urllib2.URLE
Hi,
I know the macports developers dont like using Apple supplied stuff
but here is an inverse case - where the system supplied python works
but macports python doesnt.
running macports python with a python script that has worked for a year or so
(from Panther to Leopard) gives the following err
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>
> Would you still care to send a patch? :-)
>
patch sent as ticket 19176
note I kept as close as possible to the existing code and its variable names
David
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org
On Thu, Apr 02, 2009 at 09:55:22AM -0600, Rainer Müller wrote:
> >
> > with this I have had pkg_uninstall working for a few years - unfortunately
> > the name change
> > from darwinports to macports made life difficult for me (running on Panther
> > at the time
> > and only recently upgrading to
On Thu, Apr 02, 2009 at 04:11:14AM -0600, Ryan Schmidt wrote:
> On Apr 2, 2009, at 04:51, Anand Buddhdev wrote:
>
> Oh yes, understood. But sorry, no, there is no post-uninstall hook.
> There are several ports where this would be useful, but nobody has
> written it yet.
>
what about the pkg_
On Wed, Mar 28, 2007 at 04:09:29PM -0700, Jordan K. Hubbard wrote:
>
>Sure, it could probably be worked around by having some set of binary
>tcl distributions to start from, but since Tcl is well-supported by
>the system, why go to all the extra trouble?
there is also the file ${prefi
16 matches
Mail list logo
