I have made a Portfile for mas that needs the Commandant framework, another
Portfile I made:
https://github.com/Tatsh/ports/blob/master/devel/Commandant/Portfile
https://github.com/Tatsh/ports/blob/master/sysutils/mas/Portfile
On line 17, I clearly wrote:
depends_lib port:Commandant por
Dear Werner,
On Sun, 10 Mar 2019 at 08:24, Werner LEMBERG wrote:
>
> trying
>
> port mpkg lilypond-devel
>
> creates a 1.5GByte bundle, which is far too large to be used for
> distribution. Is there a possibility to reduce the number of packages
> that gets bundled?
>
> As far as I can see, the
> On Mar 10, 2019, at 12:00 PM, Mojca Miklavec wrote:
>
> Dear Werner,
>
> On Sun, 10 Mar 2019 at 08:24, Werner LEMBERG wrote:
>>
>> trying
>>
>> port mpkg lilypond-devel
>>
>> creates a 1.5GByte bundle, which is far too large to be used for
>> distribution. Is there a possibility to reduce
Hi there!
The command sudo port install mysql-connector-java failed.
---> Building mysql-connector-java
Error: Failed to build mysql-connector-java: command execution failed
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_java_my
Old MacBook (March 2010), latest Macports etc.
Been getting this for a while, in my regular "port upgrade outdated":
---> Scanning binaries for linking errors
Warning: Error parsing file
/opt/local/lib/go/src/cmd/vendor/github.com/google/pprof/internal/binutils/testdata/malformed_macho
While someone who can speak authoritatively needs to confirm this, the name
certainly suggests a Mach-O (Mac's object file format) executable that's
purposely malformed as test data for routines that manipulate object files. As
such, it probably _should_ be corrupt, and is probably not cause fo
Or to put it another way, relax: this particular malformed_macho has nothing to
do with what the #MeToo folks complain about. :-)
> On Mar 10, 2019, at 19:11, Richard L. Hamilton wrote:
>
> While someone who can speak authoritatively needs to confirm this, the name
> certainly suggests a Mach-
Known issue, see https://trac.macports.org/ticket/58170
Christopher Chavez
On Sun, Mar 10, 2019 at 5:20 PM -0500, "Dave Horsfall"
wrote:
Old MacBook (March 2010), latest Macports etc.
Been getting this for a while, in my regular "port
Trying to build octave on OS X 10.10.6 Yosemite with Macports 2.4.3.
Sync'd port tree first
Then sudo port install octave... installs a bunch of dependencies but then
faiis with "invalid command name "startupitems".
Tried a few things (like using the clang70 variant as I have a working clang 7
> On Mar 10, 2019, at 10:47 PM, Ulrich Wienands wrote:
>
> Trying to build octave on OS X 10.10.6 Yosemite with Macports 2.4.3.
>
> Sync'd port tree first
>
> Then sudo port install octave... installs a bunch of dependencies but then
> faiis with "invalid command name "startupitems".
> ...
Yo
I noticed that the socket in /var/mysql is called mysql.sock while the
one in /opt/local/var/run/mysql5 is called mysqld.sock (note the 'd'
between 'l' and '.').
I tried using
$ sudo ln -s /var/mysql/mysql.sock /opt/local/var/run/mysql5/mysqld.sock
for some reason that also didn't work.
Then
> On 2019-03-11, at 00:10, MacPorts wrote:
>
> I noticed that the socket in /var/mysql is called mysql.sock while the one in
> /opt/local/var/run/mysql5 is called mysqld.sock (note the 'd' between 'l' and
> '.').
>
> I tried using
>$ sudo ln -s /var/mysql/mysql.sock /opt/local/var/run/my
12 matches
Mail list logo
