Re: What happened to qt4-mac's qmake utility (re High Sierra v. Lion)?

[Ian Wadham]

> On 23 Nov 2017, at 4:38 pm, Nicolas Pavillon  
> wrote:
> I don’t think the change in prefix is platform dependent. This happened quite 
> some time ago to allow co-installation of both qt5 and qt4-mac (see 
> https://trac.macports.org/changeset/140960). As far as ports are concerned, 
> their compilation should have been fixed also quite some time ago.
> If you need to find specific qt4 components in your own codes, I imagine that 
> setting QTDIR should be enough (just a wild guess), which
> is now set to ${prefix}/libexec/qt4.

Thanks, Nicolas, I might try that. Nice to see you are still around... :-)
Cheers, Ian W.

>> On Nov23, 2017, at 12:36, Ian Wadham  wrote:
>> 
>> I have been setting up a new MacBook Pro 13-inch with High Sierra.
>> Macports is building and running fine with qt4-mac, kdegames4 and kmymoney4
>> requested and a long list of dependencies installed.
>> 
>> Now I am trying to resurrect some of the KDE 4 source-code and applications
>> I used to work on when I was a KDE developer. I brought across a bunch of 
>> source
>> from my old MacBook Pro (2011 vintage and using Lion). But when I went to 
>> build
>> it CMake failed during its checks of the software and hardware environment, 
>> which
>> it does before starting to generate a makefile and build.
>> 
>> Specifically, CMake could not find qmake, Qt’s utility for generating 
>> builds. Using
>> “port contents” I found that qt4-mac @4.8.7_5 has qmake installed at 
>> /opt/local/bin
>> on Lion, but on High Sierra it is at /opt/local/libexec/qt4/bin, which is 
>> not in my $PATH.
>> 
>> So why has qmake moved?
>> 
>> And what should I add to my $PATH, /opt/local/libexec/qt4/bin? Or would 
>> /opt/local/libexec
>> be enough (and more general)? Or perhaps CMake needs some option?
>> 
>> All the best, Ian W.
>> 
> 

Re: What happened to qt4-mac's qmake utility (re High Sierra v. Lion)?

[Ian Wadham]

> On 23 Nov 2017, at 4:38 pm, Ryan Schmidt  wrote:
> 
> 
> On Nov 22, 2017, at 21:36, Ian Wadham wrote:
> 
>> I have been setting up a new MacBook Pro 13-inch with High Sierra.
>> Macports is building and running fine with qt4-mac, kdegames4 and kmymoney4
>> requested and a long list of dependencies installed.
>> 
>> Now I am trying to resurrect some of the KDE 4 source-code and applications
>> I used to work on when I was a KDE developer. I brought across a bunch of 
>> source
>> from my old MacBook Pro (2011 vintage and using Lion). But when I went to 
>> build
>> it CMake failed during its checks of the software and hardware environment, 
>> which
>> it does before starting to generate a makefile and build.
>> 
>> Specifically, CMake could not find qmake, Qt’s utility for generating 
>> builds. Using
>> “port contents” I found that qt4-mac @4.8.7_5 has qmake installed at 
>> /opt/local/bin
>> on Lion, but on High Sierra it is at /opt/local/libexec/qt4/bin, which is 
>> not in my $PATH.
>> 
>> So why has qmake moved?
>> 
>> And what should I add to my $PATH, /opt/local/libexec/qt4/bin? Or would 
>> /opt/local/libexec
>> be enough (and more general)? Or perhaps CMake needs some option?
> 
> qmake and other qt programs and files moved so that the qt4-mac and qt5 ports 
> could be installed simultaneously. Ports using qt are meant to use the 
> various qt portgroups, which set variables that the port can use to access 
> the locations of those files. If you're trying to build your own software 
> outside of MacPorts but using MacPorts qt, I guess you'll have to put the 
> right path into your $PATH. The right path is the one that contains the 
> binary you want to use. I don't know if modifying the $PATH is enough for 
> cmake to be able to find things.

Good answer. Thanks, Ryan. Putting Qt’s libexec on the $PATH does placate CMake 
and the build then proceeds normally.
Cheers, Ian W.

Re: livecheck timeout

[Ryan Schmidt]

On Nov 21, 2017, at 11:31, db wrote:

> Is it possible to set this? I checked man pages for both port-livecheck and 
> port but couldn't find a way. I have a shell function for a list of ports 
> that stucks on gnutls too long, for some reason.

I'm not aware of a way for a use to set the livecheck timeout.

How long is too long?

I use a script that runs livecheck on all my ports, and does many checks 
simultaneously, to reduce the impact of timeouts and slow servers.

https://github.com/ryandesign/macports-user-ryandesign/blob/master/scripts/portmylivecheck

Re: What happened to qt4-mac's qmake utility (re High Sierra v. Lion)?

[Nicolas Pavillon]

Hi, 

I don’t think the change in prefix is platform dependent. This happened quite 
some time ago to allow co-installation of both qt5 and qt4-mac (see 
https://trac.macports.org/changeset/140960). As far as ports are concerned, 
their compilation should have been fixed also quite some time ago.
If you need to find specific qt4 components in your own codes, I imagine that 
setting QTDIR should be enough (just a wild guess), which
is now set to ${prefix}/libexec/qt4.

Cheers,

Nicolas

> On Nov23, 2017, at 12:36, Ian Wadham  wrote:
> 
> I have been setting up a new MacBook Pro 13-inch with High Sierra.
> Macports is building and running fine with qt4-mac, kdegames4 and kmymoney4
> requested and a long list of dependencies installed.
> 
> Now I am trying to resurrect some of the KDE 4 source-code and applications
> I used to work on when I was a KDE developer. I brought across a bunch of 
> source
> from my old MacBook Pro (2011 vintage and using Lion). But when I went to 
> build
> it CMake failed during its checks of the software and hardware environment, 
> which
> it does before starting to generate a makefile and build.
> 
> Specifically, CMake could not find qmake, Qt’s utility for generating builds. 
> Using
> “port contents” I found that qt4-mac @4.8.7_5 has qmake installed at 
> /opt/local/bin
> on Lion, but on High Sierra it is at /opt/local/libexec/qt4/bin, which is not 
> in my $PATH.
> 
> So why has qmake moved?
> 
> And what should I add to my $PATH, /opt/local/libexec/qt4/bin? Or would 
> /opt/local/libexec
> be enough (and more general)? Or perhaps CMake needs some option?
> 
> All the best, Ian W.
> 

Re: openmpi is not using gcc7

[David Strubbe]

Hello Chao-Chin,

This is not a bug. Note the text in the port description for
openmpi-default: "THIS SUBPORT WRAPS MACPORTS' DEFAULT COMPILER FOR C/C++
(AND THE FORTRAN COMPILER SELECTED BY THE VARIANT, IF ANY)" So, you have
built OpenMPI for clang for C/C++ and gfortran (from gcc7) for Fortran. If
you want openmpi with gcc7 for C, then yes you should install openmpi-gcc7
instead.

David

On Wed, Nov 22, 2017 at 11:51 AM, Chao-Chin Yang 
wrote:

> Hi,
>
> I installed openmpi with gcc7 by:
>
> $ sudo port install openmpi +threads
> …
> $ port installed | grep openmpi
> openmpi @1.10.3_0 (active)
> openmpi-default @1.10.3_0+gcc7+threads (active)
> $ port select mpi
> Available versions for mpi:
> none
> openmpi-mp-fortran (active)
>
> However, gcc is not invoked by the mpi wrapper:
>
> $ which mpicc
> /opt/local/bin/mpicc
> $ mpicc --show
> /usr/bin/clang -I/opt/local/include/openmpi-mp
> -L/opt/local/lib/openmpi-mp -lmpi
>
> It is using Apple’s native, not gcc at all.  And the mpi wrapper is a
> series of links to opal_wrapper, which is a binary.
>
> Has anyone had this problem also?  Is it a bug in the port file?  How can
> I fix this without installing openmpi-gcc7 and force the mpi selection?
>
> Sincerely,
> Chao-Chin
>
>

What happened to qt4-mac's qmake utility (re High Sierra v. Lion)?

[Ian Wadham]

I have been setting up a new MacBook Pro 13-inch with High Sierra.
Macports is building and running fine with qt4-mac, kdegames4 and kmymoney4
requested and a long list of dependencies installed.

Now I am trying to resurrect some of the KDE 4 source-code and applications
I used to work on when I was a KDE developer. I brought across a bunch of source
from my old MacBook Pro (2011 vintage and using Lion). But when I went to build
it CMake failed during its checks of the software and hardware environment, 
which
it does before starting to generate a makefile and build.

Specifically, CMake could not find qmake, Qt’s utility for generating builds. 
Using
“port contents” I found that qt4-mac @4.8.7_5 has qmake installed at 
/opt/local/bin
on Lion, but on High Sierra it is at /opt/local/libexec/qt4/bin, which is not 
in my $PATH.

So why has qmake moved?

And what should I add to my $PATH, /opt/local/libexec/qt4/bin? Or would 
/opt/local/libexec
be enough (and more general)? Or perhaps CMake needs some option?

All the best, Ian W.

openmpi is not using gcc7

[Chao-Chin Yang]

Hi,

I installed openmpi with gcc7 by:

$ sudo port install openmpi +threads
…
$ port installed | grep openmpi
openmpi @1.10.3_0 (active)
openmpi-default @1.10.3_0+gcc7+threads (active)
$ port select mpi
Available versions for mpi:
none
openmpi-mp-fortran (active)

However, gcc is not invoked by the mpi wrapper:

$ which mpicc
/opt/local/bin/mpicc
$ mpicc --show
/usr/bin/clang -I/opt/local/include/openmpi-mp -L/opt/local/lib/openmpi-mp -lmpi

It is using Apple’s native, not gcc at all.  And the mpi wrapper is a series of 
links to opal_wrapper, which is a binary.

Has anyone had this problem also?  Is it a bug in the port file?  How can I fix 
this without installing openmpi-gcc7 and force the mpi selection?

Sincerely,
Chao-Chin

Re: Questions on the update to Apache 2.4

[William H. Magill]

> On Nov 22, 2017, at 1:58 PM, Craig Treleaven  wrote:
> 
> Minor further questions…I’m a real neophyte at web servers so be gentle!
> 
> It seems that mod_rewrite and mod_deflate are both commented out by default.  
> I believe they were both enabled in the prior version.  Is there any 
> particular reason for the change?  
> 
> Is it safe to use an httpd.conf file from Apache 2.2 with the new version?  
> Or is it important to start with the new template and make necessary changes 
> to it?
> 
> Craig

I can’t comment on the Mod_rewrite and mod_delete as I don’t use them on my 
server.

As for using (attempting to use) the 2.2. config file — don’t do it. There are 
some important differences which will cause thing to fail.
Diff the two config files and then pick “2.2 old stuff” and put it in the 2.4 
config file.

For example:

2.2 Deny from all
vs
2.4  Require all denied



T.T.F.N.
William H. Magill
# iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.13.1
# Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.13.1
# MacPro5,1 Quad-Core Intel Xeon [2.8 GHz - 16 GB 1066 MHz] OSX 10.13.1
mag...@icloud.com
mag...@mac.com
whmag...@gmail.com

Re: Questions on the update to Apache 2.4

[Marius Schamschula]

Craig,

> On Nov 22, 2017, at 12:58 PM, Craig Treleaven  wrote:
> 
> Minor further questions…I’m a real neophyte at web servers so be gentle!
> 
> It seems that mod_rewrite and mod_deflate are both commented out by default.  
> I believe they were both enabled in the prior version.  Is there any 
> particular reason for the change?  

The fact that they show up in the httpd.conf file means that they are 
installed. I’m not sure what the set of modules enabled by default was with 
apache 2.2.x. Just uncomment those lines.

> Is it safe to use an httpd.conf file from Apache 2.2 with the new version?  
> Or is it important to start with the new template and make necessary changes 
> to it?

I would run diff. As noted in the Portfile notes, there are some differences 
between 2.2.x and 2.4.x in terms of the .conf files. Particularly, regarding 
access clauses.

> Craig

Marius
--
Marius Schamschula

Re: Questions on the update to Apache 2.4

[Craig Treleaven]

Minor further questions…I’m a real neophyte at web servers so be gentle!

It seems that mod_rewrite and mod_deflate are both commented out by default.  I 
believe they were both enabled in the prior version.  Is there any particular 
reason for the change?  

Is it safe to use an httpd.conf file from Apache 2.2 with the new version?  Or 
is it important to start with the new template and make necessary changes to it?

Craig