William,
On 29 Jun 2013, at 01:55, William Kyngesburye wrote:
> I was going to try it myself (haven't installed Qt5 yet, no need), but for
> some dumb reason, Qt5 switched to a custom Qt-made installer for their
> binaries. I don't trust them to not do something weird.
>
> Since the only thing
I was going to try it myself (haven't installed Qt5 yet, no need), but for some
dumb reason, Qt5 switched to a custom Qt-made installer for their binaries. I
don't trust them to not do something weird.
Since the only thing I compile doesn't support Qt5 yet (and may not for a long
while), I rea
On Fri, 28 Jun 2013 18:42:39 +0100, Anzir Boodoo
wrote:
> Phil,
> On 28 Jun 2013, at 17:39, Phil Thompson wrote:
>
>> On Fri, 28 Jun 2013 10:20:24 -0500, William Kyngesburye
>> wrote:
>>> Though I see now what you mean by those lines in configure.py -
whatever
>>> you give for --spec will be ove
Phil,
On 28 Jun 2013, at 17:39, Phil Thompson wrote:
> On Fri, 28 Jun 2013 10:20:24 -0500, William Kyngesburye
> wrote:
>> Though I see now what you mean by those lines in configure.py - whatever
>> you give for --spec will be overridden by that 'darwin' if block. And
> if
>> it isn't macx-xcode
On Fri, 28 Jun 2013 10:20:24 -0500, William Kyngesburye
wrote:
> Though I see now what you mean by those lines in configure.py - whatever
> you give for --spec will be overridden by that 'darwin' if block. And
if
> it isn't macx-xcode it defaults to whatever Qt5 was compiled with,
probably
> clan
On Fri, 28 Jun 2013 17:16:27 +0100, Phil Thompson
wrote:
> On Fri, 28 Jun 2013 10:20:24 -0500, William Kyngesburye
> wrote:
>> Though I see now what you mean by those lines in configure.py -
whatever
>> you give for --spec will be overridden by that 'darwin' if block. And
> if
>> it isn't macx-x
On Fri, 28 Jun 2013 10:20:24 -0500, William Kyngesburye
wrote:
> Though I see now what you mean by those lines in configure.py - whatever
> you give for --spec will be overridden by that 'darwin' if block. And
if
> it isn't macx-xcode it defaults to whatever Qt5 was compiled with,
probably
> clan
William,
On 28 Jun 2013, at 16:20, William Kyngesburye wrote:
> Though I see now what you mean by those lines in configure.py - whatever you
> give for --spec will be overridden by that 'darwin' if block. And if it
> isn't macx-xcode it defaults to whatever Qt5 was compiled with, probably
> cl
William,
On 28 Jun 2013, at 16:10, William Kyngesburye wrote:
> It should be:
>
> --spec=macx-llvm
>
> Do you get the same error?
Yes... it's still trying to get at clang++
It looks like qmake is trying to get at clang++ - the day was going to come
when me still being on Snow Leopard started
Though I see now what you mean by those lines in configure.py - whatever you
give for --spec will be overridden by that 'darwin' if block. And if it isn't
macx-xcode it defaults to whatever Qt5 was compiled with, probably clang++.
On Jun 28, 2013, at 10:10 AM, William Kyngesburye wrote:
> It s
It should be:
--spec=macx-llvm
Do you get the same error?
On Jun 28, 2013, at 9:38 AM, Anzir Boodoo wrote:
> Phil,
> On 28 Jun 2013, at 09:53, Phil Thompson wrote:
>
>> On Thu, 27 Jun 2013 18:59:26 -0500, William Kyngesburye
>> wrote:
>>> PyQt should be picking the spec from SIP (unless PyQt
Phil,
On 28 Jun 2013, at 09:53, Phil Thompson wrote:
> On Thu, 27 Jun 2013 18:59:26 -0500, William Kyngesburye
> wrote:
>> PyQt should be picking the spec from SIP (unless PyQt 5 changed that).
>> You can specify the spec when compiling SIP with the option:
>>
>> -p macx-g++
>>
>> if that does
On Thu, 27 Jun 2013 18:59:26 -0500, William Kyngesburye
wrote:
> PyQt should be picking the spec from SIP (unless PyQt 5 changed that).
> You can specify the spec when compiling SIP with the option:
>
> -p macx-g++
>
> if that doesn't work when compiling PyQt, try:
>
> -p macx-llvm
>
> It's o
PyQt should be picking the spec from SIP (unless PyQt 5 changed that). You can
specify the spec when compiling SIP with the option:
-p macx-g++
if that doesn't work when compiling PyQt, try:
-p macx-llvm
It's odd though, even on OS X 10.7, I get macx-g++ as the default for SIP.
If PyQt 5 ign
William,
On 27 Jun 2013, at 15:40, William Kyngesburye wrote:
> Xcode on OSX 10.6 doesn't have clang++, all c++ is handled directly in
> "clang", though I think the early versions of clang here don't fully support
> c++. You're better off with llvm-g++. Xcode added clang++ in later versions
>
Xcode on OSX 10.6 doesn't have clang++, all c++ is handled directly in "clang",
though I think the early versions of clang here don't fully support c++.
You're better off with llvm-g++. Xcode added clang++ in later versions
starting with Lion.
You should try to use a different qmake spec, ei
Phil,
On 25 Jun 2013, at 15:42, Phil Thompson wrote:
> On Tue, 25 Jun 2013 15:36:59 +0100, Anzir Boodoo
> wrote:
>> Hello,
>>
>> I've been trying to install PyQt 5 on Mac OS X 10.6.8...
Phil suggested:
> Use the --qmake flag to point to Qt5's qmake. You are probably defaulting
> to Qt4's.
It
On Tue, 25 Jun 2013 15:36:59 +0100, Anzir Boodoo
wrote:
> Hello,
>
> I've been trying to install PyQt 5 on Mac OS X 10.6.8, and got the
> following output (the first line being the Terminal command):
>
>> Anzir-Boodoos-MacBook-Pro-2:PyQt-gpl-5.0 pbadmin$ python configure.py
>> --verbose
>> Query
Hello,
I've been trying to install PyQt 5 on Mac OS X 10.6.8, and got the following
output (the first line being the Terminal command):
> Anzir-Boodoos-MacBook-Pro-2:PyQt-gpl-5.0 pbadmin$ python configure.py
> --verbose
> Querying qmake about your Qt installation...
> An internal error occured.
19 matches
Mail list logo
