Re: octave does not build
On Jul 23 15:51:49, michae...@macports.org wrote: > Looks like the link command is missing LAPACK or the equivalent (e.g. maybe: > Atlas, OpenBLAS, Eigen), but since the log doesn't include the actual link > command I can't say for certain. Maybe add some verbosity to the build stage > to show the actual link command? - MLD How do I do that on port(1) level? Or do I need to tweak the actual Portfile with something like --disable-silent-rules? Thanks, Jan > On Mon, Jul 23, 2018, at 3:26 PM, Jan Stary wrote: > > Attached please find a full log of > > > > sudo port -vs install octave -app -docs +gfortran -graphicsmagick -java > > -qt5 +sound -universal > > > > It eventually fails with undefined symbols. > > Am I missing something obvious? > > > > Jan > > > > Email had 1 attachment: > > + main.log.gz > > 60k (application/x-gunzip)
Re: vnc
On 2018-07-24 07:55, James wrote: > For ages I have used Chicken but High Sierra warns me of it being a 32bit app. > macports has cotvnc and also vnc > Any opinions sage words or other Usually I use the builtin VNC client of macOS. You can launch it by opening a vnc:// URL from Finder's "Connect to Server" dialog or with open(1) from a terminal window, for example: open vnc://hostname:5190 Hope that helps, Rainer PS: Please use the new @lists.macports.org addresses as we are no longer on macOS Forge.
Re: vnc
> On 24 Jul 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >> For ages I have used Chicken but High Sierra warns me of it being a 32bit >> app. >> macports has cotvnc and also vnc >> Any opinio,ns sage words or other > > Usually I use the builtin VNC client of macOS. You can launch it by > opening a vnc:// URL from Finder's "Connect to Server" dialog or with > open(1) from a terminal window, for example: > , > open vnc://hostname:5190 > Alas the built-in server does not play nicely with the other kids Conmection failed to ‘sandypit.home' Make sure Screen Sharing or Remote Management (in the Sharing section of System Preferences) is enabled on the remote computer. One of my linux boxes running xvnc Chicken DOES connect James
Re: vnc
What exactly is your question ? The macPorts build of cotvnc is 64-bit and no warnings are offered running it. Presumably you get the warnings running some other build ? If you like this app just bin the one you are using and install the MacPorts one. Chris > On 24 Jul 2018, at 6:55 am, James wrote: > > For ages I have used Chicken but High Sierra warns me of it being a 32bit app. > macports has cotvnc and also vnc > Any opinions sage words or other > Thanks > James > > PS Chicken means ‘Chicken of the VNC’ and cotvnc is a port of it. I assume > one can build it in 64bit mode smime.p7s Description: S/MIME cryptographic signature
Re: octave does not build
This would be a Portfile change, adding in the flag you mention. Here's my
recommendation:
{{{
diff --git a/math/octave/Portfile b/math/octave/Portfile
index b20fb7b622..032ea2dce6 100644
--- a/math/octave/Portfile
+++ b/math/octave/Portfile
@@ -273,7 +273,8 @@ configure.args-append \
configure.args-append \
--with-framework-carbon \
--without-x \
---enable-static
+--enable-static \
+--disable-silent-rules
configure.args-append \
--disable-openmp
}}}
On Tue, Jul 24, 2018, at 3:26 AM, Jan Stary wrote:
> On Jul 23 15:51:49, michae...@macports.org wrote:
> > Looks like the link command is missing LAPACK or the equivalent (e.g.
> > maybe: Atlas, OpenBLAS, Eigen), but since the log doesn't include the
> > actual link command I can't say for certain. Maybe add some verbosity to
> > the build stage to show the actual link command? - MLD
>
> How do I do that on port(1) level?
> Or do I need to tweak the actual Portfile with
> something like --disable-silent-rules?
>
> Thanks,
>
> Jan
Re: vnc
On Jul 24, 2018, at 08:48, Christopher Jones wrote: > What exactly is your question ? The macPorts build of cotvnc is 64-bit and no > warnings are offered running it. Agreed. I use cotvnc all the time and I've seen no problems with it on High Sierra so far. Actually I use the cotvnc-devel port, to get the latest development version.
build error on Snow Leopard trying to fetch a patch file for clang-6.0
---> Fetching distfiles for clang-6.0 ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from https://distfiles.macports.org/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://lil.fr.distfiles.macports.org/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://nue.de.distfiles.macports.org/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://kmq.jp.distfiles.macports.org/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://cjj.kr.distfiles.macports.org/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://aarnet.au.distfiles.macports.org/pub/macports/distfiles/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://jnb.za.distfiles.macports.org/distfiles/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://jog.id.distfiles.macports.org/macports/distfiles/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://llvm.org/releases/6.0.1 ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from https://pek.cn.distfiles.macports.org/macports/distfiles/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from https://sha.cn.distfiles.macports.org/macports/distfiles/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://sea.us.distfiles.macports.org/macports/distfiles/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/llvm ---> Attempting to fetch 2001-xray-Define-O_CLOEXEC-for-older-SDKs-that-don-t-have.patch from http://ywg.ca.distfiles.macports.org/mirror/macports/distfiles/llvm Error: Failed to fetch clang-6.0: The requested URL returned error: 404 Plausible insofar as Snow Leopard would likely need that patch...so where is the file? signature.asc Description: Message signed with OpenPGP
Re: octave does not build
On Jul 24 09:26:18, h...@stare.cz wrote: > On Jul 23 15:51:49, michae...@macports.org wrote: > > Looks like the link command is missing LAPACK or the equivalent (e.g. > > maybe: Atlas, OpenBLAS, Eigen), but since the log doesn't include the > > actual link command I can't say for certain. Maybe add some verbosity to > > the build stage to show the actual link command? - MLD New log attached, with full commands. Jan > > > On Mon, Jul 23, 2018, at 3:26 PM, Jan Stary wrote: > > > Attached please find a full log of > > > > > > sudo port -vs install octave -app -docs +gfortran -graphicsmagick -java > > > -qt5 +sound -universal > > > > > > It eventually fails with undefined symbols. > > > Am I missing something obvious?
verbose builds
In a recent thread, I came over the folowing: On Jul 24 09:26:18, h...@stare.cz wrote: > On Jul 23 15:51:49, michae...@macports.org wrote: > > Looks like the link command is missing LAPACK or the equivalent (e.g. > > maybe: Atlas, OpenBLAS, Eigen), but since the log doesn't include the > > actual link command I can't say for certain. Maybe add some verbosity to > > the build stage to show the actual link command? - MLD > > How do I do that on port(1) level? > Or do I need to tweak the actual Portfile with > something like --disable-silent-rules? On Jul 24 11:17:18, michae...@macports.org wrote: > This would be a Portfile change, adding in the flag you mention. > ---enable-static > +--enable-static \ > +--disable-silent-rules Would it be useful if port(1) had --disable-silent-rules among configure.args by default? Or at least with port -vs? Not having the actual commands renders the main.log a bit useless. Jan
