I get this kind of odd error when trying to build teTex. Basically
there is stray "1" in the list of objects to link. It works out if I
go to the build directory and manually enter the correct link command.
error message:
Error: Target org.macports.build returned: shell command " cd "/opt/
Ok, I rebuilt now, and still get the same set of errors.
Am 30.12.2007 um 01:58 schrieb Daniel Oberhoff:
Hi,
Ok, yes, I had lots of those darwin_8 thingies. While deinstalling
openssl macports just broke (it seems the whole ports system
depended on openssl) so now I had to shoot it and
02:08, Daniel Oberhoff wrote:
I can't get mozilla-dev built. It gives lots and lots of errors. I
started fixing some, but after an while I kinda though I'd first
ask if anyone has succeeded with it before, so that maybe it's just
a local misconfiguration. Among the things I f
Hi,
I can't get mozilla-dev built. It gives lots and lots of errors. I
started fixing some, but after an while I kinda though I'd first ask
if anyone has succeeded with it before, so that maybe it's just a
local misconfiguration. Among the things I fixed so far are:
1) some of the headers
Hi,
After running into the same problem as before (reversed, this time the
second installation accessed the tcl package of the first) I finally
found the culprit:
On the macports docpage on the web it says to specify the tcl package
installation directory via --with-tcl-package, which I u
I also got it done that way now. Just had to take care to save my
original installations (i.e. move them out of the way and later move
them back). Otherwise the installation starts to do a lot of
linking...whatever. Seems to work :). So now I have one 32 bit tree
and one 64bit. So far ok. J
Hi Dan,
The macoprt.conf files in /opt/local and and /opt/local64 only
reference /opt/local and /opt/local64 respectively, so this seems
correct. Hmm, so how does the port command actually know where it's
tree lives? Is it hardcoded? Or does the installation put a tag
somewhere on the sys
Well, port list lists only those installed by the second installation
(that is /opt/local/port as from the first installation).
Daniel
Am 14.12.2007 um 13:19 schrieb Ryan Schmidt:
On Dec 14, 2007, at 05:57, Daniel Oberhoff wrote:
I just installed a second macport as per instructions to
Well, port list lists only those installed by the second installation
(that is /opt/local/port as from the first installation).
Daniel
Am 14.12.2007 um 13:19 schrieb Ryan Schmidt:
On Dec 14, 2007, at 05:57, Daniel Oberhoff wrote:
I just installed a second macport as per instructions to
Hi,
I just installed a second macport as per instructions to play around
with 64bit builds. But now my first installation seems to use the
database of the second, even though that went into /opt/local64 and
not paths are set there or anything...???
Daniel
Hi,
I just installed a second macport as per instructions to play around
with 64bit builds. But now my first installation seems to use the
database of the second, even though that went into /opt/local64 and
not paths are set there or anything...???
Daniel
On Dec 12, 2007 1:43 PM, Ryan Schmidt <[EMAIL PROTECTED]> wrote:
>
> On Dec 12, 2007, at 06:28, Daniel Oberhoff wrote:
>
> >> > a) I could prevent this (i.e. have it build 32bit as before)
> >> > b) If I could have two completely independent macports repos
>
> > a) I could prevent this (i.e. have it build 32bit as before)
> > b) If I could have two completely independent macports repos on my
> > disk, one built 32bit and one 64bit. This would be ideal since most
> > everyday stuff is 32bit, and only some libs and stuiff are needed
> > for 64. I would
-- Forwarded message --
From: Daniel Oberhoff <[EMAIL PROTECTED]>
Date: Dec 12, 2007 12:29 PM
Subject: Re: plans for 64bit support
To: Weissmann Markus <[EMAIL PROTECTED]>
[...]
>
> we put some research into this during GSOC this year: It's quite hard
&g
Am 11.12.2007 um 09:50 schrieb Ryan Schmidt:
On Dec 11, 2007, at 02:35, Daniel Oberhoff wrote:
Am 10.12.2007 um 01:33 schrieb Ryan Schmidt:
On Dec 9, 2007, at 14:43, Daniel Oberhoff wrote:
Now that Leopard is out and already at 10.5.1 will macports be
supporting 64bit libraries? It&#
, Daniel Oberhoff wrote:
Now that Leopard is out and already at 10.5.1 will macports be
supporting 64bit libraries? It's just I need 64bit in my octave
installation. I pull my octave from octave.org's cvs, but it needs
quite a lot of support libraries. From what I gather it
on Leopard to build fat libraries, i.e. ones that contain 64
and 32 bit code (i think it works using -arch x84_64 -arch i686 as gcc
flags). Or will this be left to the separate ports?
Daniel Oberhoff
___
macports-users mailing list
macp
Am 16.09.2007 um 16:03 schrieb Yves de Champlain:
Le 07-09-15 à 20:06, paul beard a écrit :
On 9/15/07, Daniel Oberhoff <[EMAIL PROTECTED]> wrote:
Hi,
I like using macports to get some stuff with lots of dependencies
installed. I wonder though why it is neccessary for example to
r
;site" folders created etc.. Now wouldn't it be
possible to have proxy packages such as fink has? I.e. python24-
native? It could then be an option. Dunno if macports can handle
options like that, but it woul shure be nice.
Best
19 matches
Mail list logo
