I know where you're coming from on doing selfupdate :)
Somehow your MacPorts install has an incorrect 'base' file. Maybe I
need to bump the revision in case there are others out there with your
issue?
% sudo port -f uninstall qt4_select
% sudo port install qt4_select
% sudo qt4_select none
% sud
> The "base" file is not the correct size; it should be 3356 bytes. That'll
> make a difference! Maybe your ports tree is out of date? "port installed
> qt4_select" should return "qt4_select @0.3_1 (active)".
I'm a bit religious on the selfupdate :-)
I do have qt4_select @0.3_1 (active).
The "base" file is not the correct size; it should be 3356 bytes.
That'll make a difference! Maybe your ports tree is out of date? "port
installed qt4_select" should return "qt4_select @0.3_1 (active)".
On Thu, 01 Jul 2010 18:37 -0400, "Jeremy Lavergne"
wrote:
> > $ ls -l /opt/local/etc/select
> $ ls -l /opt/local/bin/qmake
lrwxr-xr-x 1 root admin 36 Jul 1 15:34 /opt/local/bin/qmake ->
/opt/local/libexec/qt4-mac/bin/qmake
> $ ls -ld /opt/local/etc/select/qt4*
drwxr-xr-x 7 root admin 238 Jul 1 15:33 /opt/local/etc/select/qt4
> $ ls -l /opt/local/etc/select/qt4
-rw-r--r-- 2
Is there a way -inside a portfile- to determine the header or library
search path for another port (e.g., as provided by "pkg-config
--cflags-only-I dbus-1")? For example, use 'pkg-config' to return
information & save that into a variable locally for manipulation? Right
now I'm hard-coding headin
Hi Jeremy - Thanks for those outputs; they're interesting. So what do
$ ls -l /opt/local/bin/qmake
$ ls -ld /opt/local/etc/select/qt4*
$ ls -l /opt/local/etc/select/qt4
return? You might want to try:
$ sudo qt4_select none
$ sudp qt4_select qt4-mac
and then see if the symlinks aren't correct.
Erm, perhaps I misread the debug output. Will have a look tomorrow.
R
- Original Message -
From: MacPorts
To: Russell Jones; macports-tick...@lists.macosforge.org
Sent: Thu Jul 01 19:46:39 2010
Subject: Re: [MacPorts] #25485: Xaw3d doesn't build +universal or 64-bit on
10.6.4
#25485:
> Can you do:
>
> $ ls -d /opt/local/libexec/qt*
>
> and if 'qt4-mac' is listed, then what do the following commands return:
>
> $ ls /opt/local/libexec/qt4-mac
> $ port installed qt4-mac
bin
include
lib
mkspecs
phrasebooks
plugins
q3porting.xml
share
translations
qt4-mac @4.6.3_1+no_debug+no
Hi Jeremy - That's strange; on my install of 'qt4-mac' all of the
symlinks go to somewhere. Can you do:
$ ls -d /opt/local/libexec/qt*
and if 'qt4-mac' is listed, then what do the following commands return:
$ ls /opt/local/libexec/qt4-mac
$ port installed qt4-mac
Likewise, if the command:
$ w
On Thu, 01 Jul 2010 12:34 +0200, "Rainer Müller"
wrote:
> Instead of making these default variants, rename them to +demo,
> +examples etc. That would make more sense.
Yes, I had had that thought too -- switching the polarity of the
variants' purposes.
My bigger question is: Does this change make
After running `qt4_select qt4-mac` I get this symlink to nowhere:
/opt/local/share/qt4 -> /opt/local/libexec/qt4-mac/share/qt4-mac
Is it simply missing the creation of a directory or is there another symlink
for that destination that's missing as well?
smime.p7s
Description: S/MIME cryptograph
On 06/30/2010 07:09 PM, Michael Dickens wrote:
> I think my changes to the qt4-* series are almost stabilized; one reason
> there have been so many issues is because Qt is so large in size and
> takes so long to compile (~2 hours on my 2.6 GHz MacBook Pro) -- & hence
> some changes were done by "wi
12 matches
Mail list logo
