Re: strangeness with daemondo?
For me, it only associates with the first server and seems to ignore the rest if I start it using “sudo port load ntp”. Starting it with the same parameters as in the plist (/Library/LaunchDaemons/org.macports.ntp.plist), the ntpd daemon runs just fine and associates with all servers. -- Andreas Kusalananda Kähäri System Developer at BILS Uppsala University, Sweden On 28 Oct 2014, at 20:05, Daniel J. Luke dl...@geeklair.net wrote: I just updated the ntp port and am seeing some strange behavior (on Yostemite, I haven't tested it anywhere else yet): If I create a launchd.plist for ntp that runs it directly, things work as expected. If I let Macports create one with the same ntpd command (but using daemondo), ntpd starts but doesn't associate with any peers. Anyone else see anything like this, or have a thought as to what might be causing it? -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Yosemite build debugging? (subversion-javahlbindings)
On Oct 29, 2014, at 1:04 AM, Ryan Schmidt ryandes...@macports.org wrote: On Oct 28, 2014, at 2:09 PM, Daniel J. Luke wrote: (see ticket #45496 - https://trac.macports.org/ticket/45496) I don't use the javahl-bindings, but it's been reported that they crash on Yosemite. What's interesting to me is that the test suite also crashes when run from within MacPorts, but if I do a build outside of MacPorts (as the macports user) the test suite runs fine. Does your build outside of MacPorts set all of the same environment variables that MacPorts does? I recall problems seen in other ports because MacPorts was setting MACOSX_DEPLOYMENT_TARGET which triggered some different behavior. I was missing MACOSX_DEPLOYMENT_TARGET - and indeed adding it gets me the same result outside of MacPorts. Looks like the cause was fixed in our libtool port by larryv in r125325 (and it actually looks like upstream released a new libtool including the libtool.m4 change as 2.4.3). As a minimal change, I think I'll just patch configure for the subversion-javahlbindings port as the other subversion port(s) seem to be working OK. -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: strangeness with daemondo?
On Oct 29, 2014, at 5:15 AM, Andreas Kusalananda Kähäri andreas.kah...@bils.se wrote: For me, it only associates with the first server and seems to ignore the rest if I start it using “sudo port load ntp”. Starting it with the same parameters as in the plist (/Library/LaunchDaemons/org.macports.ntp.plist), the ntpd daemon runs just fine and associates with all servers. I edited the MacPorts generated plist to dump stderr and stdout to a file and added -D4 to get debugging info from ntpd - but I didn't see anything obvious. -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [127553] trunk/dports/devel/subversion-javahlbindings
This isn't quite right. Only M4 templates require the double brackets;
configure scripts need single pairs, otherwise 10.0 through 10.2 won't actually
be detected properly (not that we care about those anymore). See
http://trac.macports.org/browser/trunk/dports/devel/glib2/files/yosemite-symbol-lookup.patch?rev=127207
http://trac.macports.org/browser/trunk/dports/devel/glib2/files/yosemite-symbol-lookup.patch?rev=127207.
vq
On Oct 29, 2014, at 10:45 AM, dl...@macports.org wrote:
Revision
127553 https://trac.macports.org/changeset/127553Author
dl...@macports.org mailto:dl...@macports.orgDate
2014-10-29 07:45:26 -0700 (Wed, 29 Oct 2014)
Log Message
subversion-javahlbindings: patch configure to work around old libtool m4
macro (fixes #45496)
Modified Paths
trunk/dports/devel/subversion-javahlbindings/Portfile
x-msg://91/#trunkdportsdevelsubversionjavahlbindingsPortfile
Added Paths
trunk/dports/devel/subversion-javahlbindings/files/yosemite-patch-configure.diff
x-msg://91/#trunkdportsdevelsubversionjavahlbindingsfilesyosemitepatchconfigurediff
Diff
Modified: trunk/dports/devel/subversion-javahlbindings/Portfile (127552 =
127553)
--- trunk/dports/devel/subversion-javahlbindings/Portfile 2014-10-29
14:23:56 UTC (rev 127552)
+++ trunk/dports/devel/subversion-javahlbindings/Portfile 2014-10-29
14:45:26 UTC (rev 127553)
@@ -4,6 +4,7 @@
name subversion-javahlbindings
version 1.8.10
+revision 1
categories devel java
platformsdarwin
maintainers geeklair.net:dluke blair
@@ -57,7 +58,7 @@
destroot.violate_mtree yes
-patchfiles patch-configure.diff
+patchfiles patch-configure.diff yosemite-patch-configure.diff
pre-configure { reinplace
s|hardcode_direct=yes|hardcode_direct=no|g \
${worksrcpath}/configure
Added:
trunk/dports/devel/subversion-javahlbindings/files/yosemite-patch-configure.diff
(0 = 127553)
---
trunk/dports/devel/subversion-javahlbindings/files/yosemite-patch-configure.diff
(rev 0)
+++
trunk/dports/devel/subversion-javahlbindings/files/yosemite-patch-configure.diff
2014-10-29 14:45:26 UTC (rev 127553)
@@ -0,0 +1,11 @@
+--- configure.orig 2014-10-29 10:20:21.0 -0400
configure2014-10-29 10:22:43.0 -0400
+@@ -10348,7 +10348,7 @@
+ case ${MACOSX_DEPLOYMENT_TARGET-10.0},$host in
+ 10.0,*86*-darwin8*|10.0,*-darwin[91]*)
+ _lt_dar_allow_undefined='${wl}-undefined ${wl}dynamic_lookup' ;;
+-10.[012]*)
++10.[[012]][[,.]]*)
+ _lt_dar_allow_undefined='${wl}-flat_namespace ${wl}-undefined
${wl}suppress' ;;
+ 10.*)
+ _lt_dar_allow_undefined='${wl}-undefined ${wl}dynamic_lookup' ;;
___
macports-changes mailing list
macports-chan...@lists.macosforge.org
mailto:macports-chan...@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-changes
https://lists.macosforge.org/mailman/listinfo/macports-changes
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [127553] trunk/dports/devel/subversion-javahlbindings
On Oct 29, 2014, at 1:56 PM, Lawrence Velázquez lar...@macports.org wrote: This isn't quite right. Only M4 templates require the double brackets; configure scripts need single pairs, otherwise 10.0 through 10.2 won't actually be detected properly (not that we care about those anymore). See http://trac.macports.org/browser/trunk/dports/devel/glib2/files/yosemite-symbol-lookup.patch?rev=127207. thanks, updated in r127563 -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: need a help with PortGroup compilers
Takeshi Enomoto writes:
I am developing a port that relies on makefiles.
I need to set fortran and c++ compilers so I use PortGroup mpi 1.0.
${configure.cxx} has a default value,
but ${configure.f90} is empty.
This is a good question. And I wish I could solve this problem easier.
As far as I read compilers-1.0.tcl ${configure.f90} should be set.
You are correct and I am also stumped.
In wgrib2 I manually set ${configure.f90}.
What is wrong?
A part of a pseudo Portfile:
PortGroup mpi 1.0
use_configure no
compilers.choosef90 cxx
compilers.setup require_fortran
build.env F90=${configure.f90} \
CXX=${configure.cxx}
The compilers should very much be set at this point but I don't know why
they are not. If anyone can shed some light on this, that'd be so
helpful.
A stopgap solution for now is to set build.env in a 'pre-build {}'
block.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
