Dear Folk,
This time it died not at the configure but at the build. I gave up and am now
doing an install of qt4-mac.
Ryan Schmidt wrote:
As I said earlier in the thread, qt4-x11 is ancient and needs to be updated. I
wouldn't expend any effort trying to get version 4.4.3 to build; I'd try t
Dear Folk,
Thank you for the lead. The addresses in that patch are way out of alignment.
However, I saw what was needed, search the header for the lines of test and
approval, and did a manual patch. Presently the configure is doing it's thing.
At least it has not died at the start.
Michael
As I said earlier in the thread, qt4-x11 is ancient and needs to be updated. I
wouldn't expend any effort trying to get version 4.4.3 to build; I'd try to
update the port to 4.7.4, by packporting changesets from the qt4-mac port.
___
macports-users mai
Hi John - I don't know if this will help, but you need to patch
the file "src/corelib/global/qglobal.h"; see also, for an
example, the current qt4-mac patch for this file:
< https://trac.macports.org/browser/trunk/dports/aqua/qt4-mac/fil
es/patch-src-corelib-global-qglobal.h.diff >. Good luck! - M
> #error "This version of Mac OS X is unsupported"
Check out the qt4-mac portfile for where it makes patches to allow a version of
OS X to build.
smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lis
Dear Folk,
My attempt has died with the following tail of the main.log. Is there a piece
missing I must get first? Needless to say, the mail.log file is monstrous.
Getting postgresql was an exercise in decompressing and compressing; the bz2
file would not even start to download. I got the gz f
On Dec 4, 2011, at 03:44, Frédéric Dubois wrote:
> ok ... and it works, I mean patch ok + py-xlib now works without modifying
> DISPLAY.
Thanks for testing. I updated the port in r87757.
___
macports-users mailing list
macports-users@lists.macosforg
ok ... and it works, I mean patch ok + py-xlib now works without
modifying DISPLAY.
thanks.
Le 04/12/11 10:32, Ryan Schmidt a écrit :
On Dec 4, 2011, at 03:32, Frédéric Dubois wrote:
vpn2:py-xlib dubois$ sudo patch Portfile< ~/Desktop/py-xlib-0.15rc1.diff
Password:
patching file Portfile
Hu
vpn2:py-xlib dubois$ sudo port install py27-xlib
---> Computing dependencies for py27-xlib
---> Fetching archive for py27-xlib
---> Attempting to fetch py27-xlib-0.15rc1_0.darwin_10.x86_64.tbz2 from
http://packages.macports.org/py27-xlib
---> Fetching py27-xlib
---> Attempting to fetch pyth
On Dec 4, 2011, at 03:32, Frédéric Dubois wrote:
> vpn2:py-xlib dubois$ sudo patch Portfile < ~/Desktop/py-xlib-0.15rc1.diff
> Password:
> patching file Portfile
> Hunk #2 FAILED at 22.
> 1 out of 2 hunks FAILED -- saving rejects to file Portfile.rej
>
> oups ?
sudo port selfupdate
Then try th
vpn2:py-xlib dubois$ sudo patch Portfile < ~/Desktop/py-xlib-0.15rc1.diff
Password:
patching file Portfile
Hunk #2 FAILED at 22.
1 out of 2 hunks FAILED -- saving rejects to file Portfile.rej
oups ?
Le 04/12/11 10:25, Ryan Schmidt a écrit :
cd $(port dir py-xlib)
sudo patch Portfile< ~/Downloa
On Dec 4, 2011, at 03:21, Frédéric Dubois wrote:
> Sorry Ryan but what am I supposed to do with the file you send ?
> I guess I have to patch something but what and how ?
cd $(port dir py-xlib)
sudo patch Portfile < ~/Downloads/py-xlib-0.15rc1.diff
sudo port install py27-xlib
_
Sorry Ryan but what am I supposed to do with the file you send ?
I guess I have to patch something but what and how ?
Le 04/12/11 10:01, Ryan Schmidt a écrit :
On Dec 4, 2011, at 02:45, Ryan Schmidt wrote:
We usually only update ports to stable versions, but maybe in this case, since
the de
On Dec 4, 2011, at 02:45, Ryan Schmidt wrote:
> We usually only update ports to stable versions, but maybe in this case,
> since the developers of python-xlib are clearly being very relaxed about
> their release schedule, we should make an exception, if 0.15rc1 does resolve
> the problem. (Coul
Remember to Reply All.
On Dec 4, 2011, at 02:17, Frédéric Dubois wrote:
> I suspected something with launchd
>
> Here is the log ...
>
> vpn2:PythonOCC dubois$ python draw.py
> Traceback (most recent call last):
> File "draw.py", line 226, in
>Window(display.Display()).loop()
> File
> "
I suspected something with launchd
Here is the log ...
vpn2:PythonOCC dubois$ python draw.py
Traceback (most recent call last):
File "draw.py", line 226, in
Window(display.Display()).loop()
File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Xl
On Dec 4, 2011, at 01:30, Frédéric Dubois wrote:
> By default its not working because the DISPLAY variable is not giving
> access to a suitable X11 display to python-xlib.
> Once you "export DISPLAY=:0" it works fine.
> Is it normal ?
Ever since Leopard, Apple sets DISPLAY for you, to a special
Hello,
I have a little question concerning python-xlib.
By default its not working because the DISPLAY variable is not giving
access to a suitable X11 display to python-xlib.
Once you "export DISPLAY=:0" it works fine.
Is it normal ?
By the way I use the standard apple X11 but it exists variants
Dear All,
I'm always impressed by the relevance of your answers and by your
reactivity.
Concerning py27-xlib I did the upgrade (thanks), it works, but now I
have to understand how to manage the link
between py-xlib and the X11 display (help appreciated).
Concerning pyQt ... I'll try to do my be
On Dec 3, 2011, at 8:54 AM, Ryan Schmidt wrote:
>
> On Dec 3, 2011, at 04:15, Frédéric Dubois wrote:
>
>> Pythonocc uses occ (or oce), an open-source CAD library, which relies on X11.
>> Therefore I try to uses a python based gui able to manage X11.
>> I tried :
>> - py-xlib but its only availa
On Dec 3, 2011, at 11:07, Brandon Allbery wrote:
> 2011/12/3 Ryan Schmidt
>>> - pyQt + qt4-x11 but this last library is broken.
>>
>> You could try back-porting the changes that have happened in the qt4-mac
>> port. There are probably many changes since it's been years since this was
>> updat
2011/12/3 Ryan Schmidt
> > - pyQt + qt4-x11 but this last library is broken.
>
> You could try back-porting the changes that have happened in the qt4-mac
> port. There are probably many changes since it's been years since this was
> updated. If you get it working, send a diff so we can update th
On Dec 3, 2011, at 04:15, Frédéric Dubois wrote:
> Pythonocc uses occ (or oce), an open-source CAD library, which relies on X11.
> Therefore I try to uses a python based gui able to manage X11.
> I tried :
> - py-xlib but its only available for python 2.4
Seems that's correct. I'm not sure why
Hello,
Pythonocc uses occ (or oce), an open-source CAD library, which relies on
X11.
Therefore I try to uses a python based gui able to manage X11.
I tried :
- py-xlib but its only available for python 2.4
- wxPython but it seems it only compiles i386 and I was not able to
obtain a 64-bits
Remember to Reply All so the discussion stays on the mailing list.
On Dec 2, 2011, at 16:00, Frédéric Dubois wrote:
> ;-) its a long story ... in fact I try to build pythonocc on Mac
> (http://www.pythonocc.org) and
> it seems this package (qt4-x11) is mandatory (even if deprecated as you told
On Dec 2, 2011, at 13:05, Frédéric Dubois wrote:
> I tried to build qt4-x11 on my laptop (Snow Leopard) and it failed.
qt4-x11 hasn't been updated in forever; it was supposed to have been deleted
years ago and replaced with the x11 variant of the qt4-mac port but somehow
that didn't happen. Wh
Hello,
I tried to build qt4-x11 on my laptop (Snow Leopard) and it failed.
You'll find the log file attached.
I'm quiet disappointed by the error message "This version of Mac OS X is
unsupported" ...
Any advice ?
Regards.
--
Frédéric Dubois, Eng, PhD
LMGC - UMR CNRS 5508
Université de Montpe
27 matches
Mail list logo