Re: Sierra port problem

2016-10-05 Thread Stanton Sanderson 

> On Oct 5, 2016, at 4:39 PM, David Evans  wrote:
> 
> On 10/5/16 11:48 AM, Stanton Sanderson wrote:
>> Uggrade to Sierra from El Capitan. 
>> 
>> Trying to build  libgda5. Latest developer tools + CL tools. All 
>> dependencies show installed and active. Port fails
>> at 
>> 
>> :info:configure checking whether /opt/local/bin/valac is at least version 
>> 0.26.0... yes
>> :info:configure checking for vapigen vapigen-0.32... no
>> :info:configure configure: Searching for vapigen-0.32 program...
>> :info:configure checking for vapigen-0.32... no
>> :info:configure configure: error: Can't locate vapigen-0.32 >= 0.26.0 program
>> :info:configure Command failed:  cd 
>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_libgda5/libgda5/work/libgda-5.2.4"
>>  && ./autogen.sh --prefix=/opt/local --enable-system-sqlite=no 
>> --enable-gda-gi=yes --enable-gdaui-gi=yes --disable-silent-rules 
>> --with-graphviz --without-gtksourceview --with-ldap=no --with-mdb=no 
>> --with-mysql=no --with-oracle=no --with-firebird=no --with-java=no 
>> --with-jni=no --enable-vala=yes --enable-gdaui-vala=yes 
>> --enable-vala-extensions=yes --with-postgres=/opt/local/lib/postgresql94 
>> --with-bdb=/opt/local --with-bdb-libdir-name=lib/db60 --enable-introspection 
>> :info:configure Exit code: 1
>> :error:configure Failed to configure libgda5, consult 
>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_libgda5/libgda5/work/libgda-5.2.4/config.log
>> :error:configure org.macports.configure for port libgda5 returned: configure 
>> failure: command execution failed
>> 
>> port vala supplies vapigen (if I understand things correctly), but the 
>> version of port vala installed and active is 0.34.0 and libgda5 requests 
>> vapigen 0.32.
>> 
>> Suggestions? Ticket?
> 
> This is due to the recent update of vala to version 0.34.0.  The parameter 
> that specifies the vala version to libgda5
> needs to be updated to match.  Unfortunately, once this is fixed, libgda5 
> fails to build due issues with the latest
> version of sqlite3. See https://trac.macports.org/ticket/52179.
> 
> I hope to have a fix for both issues committed in the next day or so. Thanks 
> for your patience in the meantime.  If
> you'd like to file ticket for this issue feel free to do so.

Thank you, David. I’ll wait for the update.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: OT LaunchDaemon

2016-10-05 Thread Alejandro Imass 
On Sat, Oct 1, 2016 at 11:43 PM, James Linder  wrote:
> Over the years I’ve seen many clever people here, perchance one of them will 
> cast an eye and say THERE . . .
>
> I’m trying to run a rc.local at start up
> I created a launchdaemon
>

Last I checked I think I saw supervisor in MacPorts. With some simple
config supervisor works really well and it really simple (haven't
tested MacPorts version though).

Best,
Alejandro Imass
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Locating libraries installed with MacPorts

2016-10-05 Thread Mick Jordan 

On 10/5/16 3:28 PM, Brandon Allbery wrote:
On Wed, Oct 5, 2016 at 6:21 PM, Mick Jordan > wrote:


I have several libraries installed via MacPorts (that also exists
in /usr/lib FWIW), e.g, libpcre and libz. I was rather surprised
to see that these resolve to the MacPorts location,i.e.,
/opt/local/lib even though I am not passing -L/opt/local/lib to
the link step. I thought this might be because I was using gcc to
do the compilation/linking and that is also installed via
MacPorts, but I get the same behavior when using clang. I added
-Wl,-v to the link step and it lists the directories it is
searching and /opt/local/lib is not included in the list. So my
question is how is ld resolving to /opt/local/include. I have no
environment variables such as LDFLAGS set, although /opt/local/bin
is on my PATH.

I'm running MacPorts 2.3.4 in El Capitan.


How is the program being built? If it uses a build framework such as 
autoconf or cmake, or even just pkgconfig, it will often find things 
itself (and sometimes there's no way to stop it from doing so).


Yes, the act of writing the email turned out to improve my understanding 
of what is happening but, unfortunately, not before I hot the send 
button. The libraries in question were actually compiled by another 
framework where /opt/local/lib was being passed.


Thanks
Mick

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Locating libraries installed with MacPorts

2016-10-05 Thread Brandon Allbery 
On Wed, Oct 5, 2016 at 6:21 PM, Mick Jordan  wrote:

> I have several libraries installed via MacPorts (that also exists in
> /usr/lib FWIW), e.g, libpcre and libz. I was rather surprised to see that
> these resolve to the MacPorts location,i.e., /opt/local/lib even though I
> am not passing -L/opt/local/lib to the link step. I thought this might be
> because I was using gcc to do the compilation/linking and that is also
> installed via MacPorts, but I get the same behavior when using clang. I
> added -Wl,-v to the link step and it lists the directories it is searching
> and /opt/local/lib is not included in the list. So my question is how is ld
> resolving to /opt/local/include. I have no environment variables such as
> LDFLAGS set, although /opt/local/bin is on my PATH.
>
> I'm running MacPorts 2.3.4 in El Capitan.
>

How is the program being built? If it uses a build framework such as
autoconf or cmake, or even just pkgconfig, it will often find things itself
(and sometimes there's no way to stop it from doing so).

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Locating libraries installed with MacPorts

2016-10-05 Thread Ryan Schmidt 

> On Oct 5, 2016, at 5:21 PM, Mick Jordan  wrote:
> 
> I have several libraries installed via MacPorts (that also exists in /usr/lib 
> FWIW), e.g, libpcre and libz. I was rather surprised to see that these 
> resolve to the MacPorts location,i.e., /opt/local/lib even though I am not 
> passing -L/opt/local/lib to the link step. I thought this might be because I 
> was using gcc to do the compilation/linking and that is also installed via 
> MacPorts, but I get the same behavior when using clang. I added -Wl,-v to the 
> link step and it lists the directories it is searching and /opt/local/lib is 
> not included in the list. So my question is how is ld resolving to 
> /opt/local/include. I have no environment variables such as LDFLAGS set, 
> although /opt/local/bin is on my PATH.
> 
> I'm running MacPorts 2.3.4 in El Capitan.

I'm not able to reproduce this problem.


$ echo 'int main(void) { return 0; }' > main.c
$ clang main.c -lz
$ otool -L a.out 
a.out:
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 
1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 1226.10.1)


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Locating libraries installed with MacPorts

2016-10-05 Thread Mick Jordan 
I have several libraries installed via MacPorts (that also exists in 
/usr/lib FWIW), e.g, libpcre and libz. I was rather surprised to see 
that these resolve to the MacPorts location,i.e., /opt/local/lib even 
though I am not passing -L/opt/local/lib to the link step. I thought 
this might be because I was using gcc to do the compilation/linking and 
that is also installed via MacPorts, but I get the same behavior when 
using clang. I added -Wl,-v to the link step and it lists the 
directories it is searching and /opt/local/lib is not included in the 
list. So my question is how is ld resolving to /opt/local/include. I 
have no environment variables such as LDFLAGS set, although 
/opt/local/bin is on my PATH.


I'm running MacPorts 2.3.4 in El Capitan.

Thanks
Mick

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Sierra port problem

2016-10-05 Thread David Evans 
On 10/5/16 11:48 AM, Stanton Sanderson wrote:
> Uggrade to Sierra from El Capitan. 
> 
> Trying to build  libgda5. Latest developer tools + CL tools. All dependencies 
> show installed and active. Port fails
> at 
> 
> :info:configure checking whether /opt/local/bin/valac is at least version 
> 0.26.0... yes
> :info:configure checking for vapigen vapigen-0.32... no
> :info:configure configure: Searching for vapigen-0.32 program...
> :info:configure checking for vapigen-0.32... no
> :info:configure configure: error: Can't locate vapigen-0.32 >= 0.26.0 program
> :info:configure Command failed:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_libgda5/libgda5/work/libgda-5.2.4"
>  && ./autogen.sh --prefix=/opt/local --enable-system-sqlite=no 
> --enable-gda-gi=yes --enable-gdaui-gi=yes --disable-silent-rules 
> --with-graphviz --without-gtksourceview --with-ldap=no --with-mdb=no 
> --with-mysql=no --with-oracle=no --with-firebird=no --with-java=no 
> --with-jni=no --enable-vala=yes --enable-gdaui-vala=yes 
> --enable-vala-extensions=yes --with-postgres=/opt/local/lib/postgresql94 
> --with-bdb=/opt/local --with-bdb-libdir-name=lib/db60 --enable-introspection 
> :info:configure Exit code: 1
> :error:configure Failed to configure libgda5, consult 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_libgda5/libgda5/work/libgda-5.2.4/config.log
> :error:configure org.macports.configure for port libgda5 returned: configure 
> failure: command execution failed
> 
> port vala supplies vapigen (if I understand things correctly), but the 
> version of port vala installed and active is 0.34.0 and libgda5 requests 
> vapigen 0.32.
> 
> Suggestions? Ticket?

This is due to the recent update of vala to version 0.34.0.  The parameter that 
specifies the vala version to libgda5
needs to be updated to match.  Unfortunately, once this is fixed, libgda5 fails 
to build due issues with the latest
version of sqlite3. See https://trac.macports.org/ticket/52179.

I hope to have a fix for both issues committed in the next day or so. Thanks 
for your patience in the meantime.  If
you'd like to file ticket for this issue feel free to do so.




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Sierra port problem

2016-10-05 Thread Stanton Sanderson 
Uggrade to Sierra from El Capitan. 

Trying to build  libgda5. Latest developer tools + CL tools. All dependencies 
show installed and active. Port fails
at 

:info:configure checking whether /opt/local/bin/valac is at least version 
0.26.0... yes
:info:configure checking for vapigen vapigen-0.32... no
:info:configure configure: Searching for vapigen-0.32 program...
:info:configure checking for vapigen-0.32... no
:info:configure configure: error: Can't locate vapigen-0.32 >= 0.26.0 program
:info:configure Command failed:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_libgda5/libgda5/work/libgda-5.2.4"
 && ./autogen.sh --prefix=/opt/local --enable-system-sqlite=no 
--enable-gda-gi=yes --enable-gdaui-gi=yes --disable-silent-rules 
--with-graphviz --without-gtksourceview --with-ldap=no --with-mdb=no 
--with-mysql=no --with-oracle=no --with-firebird=no --with-java=no 
--with-jni=no --enable-vala=yes --enable-gdaui-vala=yes 
--enable-vala-extensions=yes --with-postgres=/opt/local/lib/postgresql94 
--with-bdb=/opt/local --with-bdb-libdir-name=lib/db60 --enable-introspection 
:info:configure Exit code: 1
:error:configure Failed to configure libgda5, consult 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_libgda5/libgda5/work/libgda-5.2.4/config.log
:error:configure org.macports.configure for port libgda5 returned: configure 
failure: command execution failed

port vala supplies vapigen (if I understand things correctly), but the version 
of port vala installed and active is 0.34.0 and libgda5 requests vapigen 0.32.

Suggestions? Ticket?


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Apache and the macOS Firewall (was Re: MacPorts question)

2016-10-05 Thread mf2k 

> On Sep 29, 2016, at 2:05 PM, Ryan Schmidt  wrote:
> 
> 
>> On Sep 29, 2016, at 10:30 AM, Zachary Waibel  wrote:
>> 
>> Here’s my question: 
>> 
>> I've installed the latest MacPorts and my issue is that if I start apache2 
>> using the command "sudo port load apache2” I can then find my website from 
>> outside my network.  However, after restarting my Mac and I cannot find my 
>> website anymore.  It turns out if I turn off macOS’s Firewall I can then 
>> find the website from the outside again.  The other way I can solve it is by 
>> doing "sudo port unload apache2” and then "sudo port load apache2”, which 
>> seems to open port 80.  However, after a restart the port is not opened, but 
>> apache2 is running.  So is MacPorts not compatible with El Capitan’s 
>> Firewall?
>> 
>> Thank you for any help!
> 
> Writing to the macports-users mailing list is probably the right thing to do. 
> I'm Cc'ing the list now. To reply, please make sure you're subscribed to the 
> list first.
> 
> I've also been frustrated with the new macOS firewall for some years. I don't 
> understand it. Maybe someone else on the list does and can give us both some 
> advice.

OK, the solution was actually very simple. I added the httpd application to the 
Firewall. It is located here:

/opt/local/apache2/bin/httpd

This survived a reboot for me. 

Steps to add it (sorry if this is obvious):
 1. Starting from the Terminal type:
- cd /opt/local/apache2/bin/
- open .
 2. Open System Preferences->Security & Privacy->Firewall tab.
 3. Click the lock to unlock it.
 4. Click Firewall Options…
 5. Click +
 6. In Finder, drag “httpd” (now visible in Finder from Step 1) to the dialog. 



Please let me know if this works for you too and I will add these steps to the 
wiki. 


Cheers!
Frank

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users