Ryan Schmidt writes:
>> On Jun 11, 2016, at 10:11 AM, Gideon Simpson
>> wrote:
>>
>> I have an intel mkl license, and I know that numpy/scipy can be built
>> against it for a performance boost. I was wondering two things:
>>
>> 1. Is it possible that we could have a variant of numpy/scipy t
j. van den hoff writes:
> on one of two machines (both running 10.10.5 and current `port')
> installation of py-hgsubversion fails with (end of logfile):
>
> 8<--
> ...
> CC='/usr/bin/clang'
> CC_PRINT_
j. van den hoff writes:
> On Wed, 16 Mar 2016 19:41:39 +0100, Sean Farley wrote:
>
>>
>> j. van den hoff writes:
>>
>>> on one of two machines (both running 10.10.5 and current `port')
>>> installation of py-hgsu
j. van den hoff writes:
> if it helps, I'll type in everything you want (expect `/bin/rm -r' I mean
> ;-)) to get more info and solve the issue. just let me know (possibly
> off-list as well).
My best guess at debugging would be to clean and extract the port:
$ sudo port -v clean py27-hgs
Carlo Tambuatco writes:
> Uninstalling pypy @4.0.1_0 and installing pypy @5.0.0 seems to have done the
> trick.
>
> What went wrong?
It seems that pypy looks for an installed version.
___
macports-users mailing list
macports-users@lists.macosforge.or
Carlo Tambuatco writes:
> Upgrading pypy @4.0.1_0 to pypy @5.0.0 fails with following error:
>
> Building pypy
> Error: org.macports.build for port pypy returned: command execution failed
> Please see the log file for port pypy for details:
>
> /opt/local/var/macports/logs/_opt_local_var_ma
Gideon Simpson writes:
> Since vtk5 seems to be broken on el capitan, dolfin won’t install. Is it
> possible to work around that?
Is there a ticket for this? I have vtk5+python+tcltk installed just fine.
___
macports-users mailing list
macports-user
Jerry writes:
> On Jan 21, 2016, at 9:20 PM, David Strubbe wrote:
>
> David, thank you for this explanation. Installing py33-scipy +gfortran
> worked. However, I have these notes.
>
>> As the message says, you need to select a Fortran variant. You have not. You
>> can see this from the fact t
Fielding, Eric J (329A) writes:
> I only use IPython occasionally, so I just now found out that the new version
> of IPython 4.0 has major changes, and MacPorts has installed the new version
> in one of my port upgrades. We used to run “ipython notebook” to get the
> notebook version of IPyth
Ryan Schmidt writes:
> Dear MacPorts users and developers,
>
> I'm pleased finally to be able to tell you that I have been hired to be your
> new Mac OS Forge administrator. I have been involved in improving MacPorts
> for years as a committer and as a manager, and now as a Mac OS Forge
> adm
Joshua Root writes:
> The MacPorts Project is pleased to announce the release of version
> 2.3.4. This is a bugfix release with small changes only. See the
> ChangeLog [1] for the list of changes.
Thanks man!
___
macports-users mailing list
macports-u
Dominik Reichardt writes:
> Hi,
>
> I’m itching to switch but often need MacPorts. Do any of you have experience
> yet with it *AND* MacPorts?
Join the club :-(
> In previous switches, I switched by using the development version of MacPorts
> and following the migration steps of any major OS
Peter Danecek writes:
> Any news on this?
> Or should I have a look at it?
Ack, I completely forgot about this. If you can do it, that'd be great.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman
Peter Danecek writes:
> Hi all,
> should this thread become a ticket?
> This issue was observed by a one of my colleagues as well. I have not YET run
> into it.
I was going to get around to doing it tonight at our python group
meetup, if no one else got to it before then.
_
Gideon Simpson writes:
> This appears to have something to do with the recent upgrade of
> py27-jsonschema from 2.4.0 to 2.5.1. As soon as I downgraded this to the
> earlier version, things ran as they had in the past.
> -gideon
Yep, it would seem there is a new dependency based on this comm
Gideon Simpson writes:
> On one my machines I still have 10.9 installed and with the recent update to
> dolfin (which works fine on my 10.10 machine), I now get errors during the
> build:
>
> _opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_dolfin/dolfin/work/dolf
Ryan Schmidt writes:
> On Jan 9, 2015, at 1:34 PM, Sean Farley wrote:
>>
>> Ryan Schmidt writes:
>>
>>> On Jan 9, 2015, at 1:16 PM, Marius Schamschula wrote:
>>>>
>>>> freecad used to declare +gcc48 as the default variant until
>>
Ryan Schmidt writes:
> On Jan 9, 2015, at 1:16 PM, Marius Schamschula wrote:
>>
>> freecad used to declare +gcc48 as the default variant until
>> https://trac.macports.org/changeset/130949 was committed. Given that this
>> change set deleted fortran related default variants for a number of
>
Brandon Allbery writes:
> On Sun, Oct 19, 2014 at 8:52 PM, Jason Mitchell
> wrote:
>
>> Is there a buildbot in the works for Yosemite ports? I checked
>> https://build.macports.org/buildslaves but didn't see anything for
>> Yosemite yet. Maybe I've misunderstood the process, or am just being
Jeremy Lavergne writes:
> It seems parmetis is still version 4.0.3.
Unfortunately, parmetis is not the same as metis. George decided to keep
two separate projects. I have done the leg work to make parmetis depend
on metis.
> On Oct 23, 2014, at 10:01 AM, L.Bryce Whitson Jr. wrote:
>
>> I have a
Gideon Simpson writes:
> I have macports petsc 3.5.2 installed, and i tried installing sudo port
> install dolfin +mpich +suitesparse +petsc +slepc. I got an error that looks
> like there was some break in the functionality of Petsc, at least with regard
> to dolfin:
>
> _opt_local_var_macpo
Daniel Watkins writes:
> I attempted to install petsc using the command
> sudo port install petsc +mpich +superlu +suitesparse
> and was unsuccessful. The log file is attached.
Ouch. This appears to be a compiler bug with clang. What OS and version
of Xcode are you running?
_
Gideon Simpson writes:
> I did a port clean dolfin and port uninstall dolfin, and then followed it up
> with sudo port install dolfin +gcc48 +mpich
More than likely, it is this error:
https://trac.macports.org/ticket/45157
___
macports-users mailing
Gideon Simpson writes:
> I did a port uninstall and a port clean, and I got the same error.
Huh. I'll try to reproduce this, then.
> I do have petsc/slepc installed with mpich, if that’s part of the problem. I
> suspect that petsc is built as a C library, while dolfin is C++. Perhaps
> that
Ryan Schmidt writes:
> On Sep 29, 2014, at 7:45 PM, Gideon Simpson wrote:
>>
>> I don’t seem to have that file
>
> Ok, looks like the compiler name is just being specified as "mpicc-mpich-mp",
> without a path, and cmake is incorrectly inferring that it is in the build
> directory.
>
> Do you
Clemens Lang writes:
> Hi,
>
>> Run "port select" to read the help message about the select mechanism. I
>> would think it's also documented elsewhere in more detail, though not,
>> apparently, via "port help select".
>
> It is, in 2.3.1, but not in trunk. See
>
> http://trac.macports.org/brow
Comer Duncan writes:
> I have today run across a failure to update py27-zmq. The output seems
> non-instructive so I am hoping to get some help. I paste the output of my
> attempt here:
>
> comermacpro:MarkFiniteDiffDerivativs comerduncan$ sudo port upgrade py27-zmq
Ah, there's your problem:
Adam Mercer writes:
> On Thu, Mar 20, 2014 at 2:55 PM, Sean Farley wrote:
>
>> I tend to agree with you but need help seeing how this worked
>> before. What path did automake pick up before this change?
>
> If you look at the patch you can see the original paths:
>
Adam Mercer writes:
> Hi
>
> Since automake was bumped to 1.14.1_1 it can't be used to build any
> python software outside of MacPorts as it always tries to install the
> python modules into MacPorts prefix. I understand why we want to
> ensure that ports always installs modules into the MacPort
Shiyuan writes:
> Hi all,
> I am on Mac 10.8.5 and Xcode 5.0.2 is installed. From Xcode
> Preference/Downloads, I can see that the command line tool is installed. I
> also installed again the command line too (released in 10/2013)l from the
> following link
> https://developer.apple.com/down
On Thu, Nov 14, 2013 at 8:29 PM, Arturo Rinaldi wrote:
> Il 15/11/13 01:37, Ryan Schmidt ha scritto:
>
> On Nov 14, 2013, at 15:27, Arturo Rinaldi wrote:
>
> Hi folks, I need some help to build my own port of these two packages. I
> want to update them to their latest version (1.3.1 and 1.8.0 resp
On Wed, Jun 26, 2013 at 7:27 AM, Rainer Müller wrote:
> On 2013-06-26 13:19, Rodolfo Aramayo wrote:
>> Many projects out there are transitioning to trello
>>
>> https://trello.com/
>
> What the heck does it do? The website tells me something about
> organizing things. There seems to be an app, but
On Thu, Feb 14, 2013 at 4:04 PM, Lawrence Velázquez wrote:
> On Feb 14, 2013, at 4:44 PM, Marion Dumas wrote:
>
>> I wanted to de-install and re-install Emacs on my mac (10.5.8). I
>> de-installed Emacs.app by simply deleting the contents. I then downloaded
>> the emacsformac dmg installer but
Marion Dumas writes:
> Hello,
>
> I wanted to de-install and re-install Emacs on my mac (10.5.8). I de-
> installed Emacs.app by simply deleting the contents. I then downloaded
> the emacsformac dmg installer but it just doesn't work: the
> application crashes at launch. I tried installing t
On Thu, Jan 31, 2013 at 8:25 PM, Lawrence Velázquez wrote:
> On Jan 31, 2013, at 8:46 PM, Sean Farley wrote:
>
>> I just want to point out that this is where having a gui that is open
>> source would really help: the responsibility wouldn't have to be
>> shouldered
On Thu, Jan 31, 2013 at 7:34 PM, Ian Wadham wrote:
> On 01/02/2013, at 11:05 AM, Ryan Schmidt wrote:
>> On Jan 31, 2013, at 16:53, Ian Wadham wrote:
>>> I did "sudo port install -k -s pallet"
>>
>> Single-letter flags like -k and -s have no effect unless you put them
>> immediately after the word
On Wed, Jan 16, 2013 at 10:06 PM, Jeremy Huddleston Sequoia
wrote:
>
> On Jan 16, 2013, at 19:44, Sean Farley wrote:
>>>> I personally have had clang++ bugs with libmesh, moose, armadillo, and
>>>> dolfin.
>>>
>>> There are plenty of g++ bugs as w
On Wed, Jan 16, 2013 at 9:32 PM, Ryan Schmidt wrote:
>
> On Jan 16, 2013, at 19:49, Sean Farley wrote:
>
>> On Wed, Jan 16, 2013 at 7:16 PM, Jeremy Huddleston Sequoia wrote:
>>>
>>> That being said, is there something wrong with clang++ that is causing you
>
On Wed, Jan 16, 2013 at 9:19 PM, Jeremy Huddleston Sequoia
wrote:
>
> On Jan 16, 2013, at 17:49, Sean Farley wrote:
>
>> On Wed, Jan 16, 2013 at 7:16 PM, Jeremy Huddleston Sequoia
>> wrote:
>>>
>>> On Jan 15, 2013, at 8:52 AM, Sean Farley wrote:
>>
On Wed, Jan 16, 2013 at 7:16 PM, Jeremy Huddleston Sequoia
wrote:
>
> On Jan 15, 2013, at 8:52 AM, Sean Farley wrote:
>
>> On Mon, Jan 14, 2013 at 8:32 AM, David Barto wrote:
>>> fails because the /usr/lib/libstdc++.so is found first. What can I do to
>>> find
On Mon, Jan 14, 2013 at 8:32 AM, David Barto wrote:
> fails because the /usr/lib/libstdc++.so is found first. What can I do to
> find the proper /opt/local/lib/libstdc++.so?
>
> I've not modified the search paths in any way, I'm just trying to compile a
> c++ program using the newer standard featu
On Mon, Dec 17, 2012 at 3:46 PM, Amy Anderson wrote:
> Hi macport users,
>
> I am trying to run this script in python and the script is now working with
> the test data (eigen problem solved) but when I input my own data to be
> called by script I got the following errors.
>
> [moriaht-5:~/Desktop
On Mon, Dec 10, 2012 at 12:01 AM, Jasper Frumau wrote:
> Thanks Sean. Looking forward to the patch!
Ok, I've just posted my patches to get it working here:
https://trac.macports.org/ticket/37254
Hopefully, they can be tested and committed by a macports developer
soon. Let me know if there are a
On Mon, Dec 10, 2012 at 12:47 PM, Rodolfo Aramayo wrote:
> I am experiencing problems building py25-cairo in all my computers
> I am attaching the log file
> Will wait for ideas before filing a bug report?
This is due to py25-cairo needing to have an older version of
py2cairo, as reported here:
On Sun, Dec 9, 2012 at 11:55 PM, Jasper Frumau wrote:
> cairo failed to build. Here is the tail of the main log:
>
> tail -n 20
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py-cairo/py25-cairo/main.log
> :info:build ^
> :info:bu
On Tue, Dec 4, 2012 at 12:25 PM, Trémouilles David wrote:
> Maybe I was not precise enough. I meant py33-ipython
> ipython version for python33. Are your running precisely
> this version with the few patches you mentioned ?
Yep, I understood. I still don't know how that path of yours got there
/
On Mon, Dec 3, 2012 at 10:35 AM, Amy Anderson wrote:
> Dear macports-users,
>
> I am a new macports, python, and scipy user and I am looking for some help
> to troubleshoot an error I have been getting when trying to run a script in
> python. The script I am trying to run is called pyCluster ROI a
On Mon, Dec 3, 2012 at 11:06 PM, Trémouilles David wrote:
> Hello,
>
> Is ipython3 working for you ?
I have a few patches that update ipython to 0.13.1 and correctly fixes
a missing py-matplotlib dependency. That might be what you're seeing
here, but I'm not 100% sure. (I'll be sending these patc
On Sat, Nov 3, 2012 at 7:04 PM, Clemens Lang wrote:
> On Sat, Nov 03, 2012 at 03:23:27PM -0400, Lenore Horner wrote:
>> I see there is a ticket from a few weeks ago that may be related, but
>> there's not closure or work-around suggested.
>> https://trac.macports.org/ticket/36608
>
> The solution
On Fri, Sep 28, 2012 at 8:41 AM, Ryan Schmidt wrote:
>
> On Sep 28, 2012, at 06:27, Trémouilles David wrote:
>
>> ---> Fetching archive for hs-pandoc-types
>> ---> Attempting to fetch hs-pandoc-types-1.8_0.darwin_11.x86_64.tbz2 from
>> http://lil.fr.packages.macports.org/hs-pandoc-types
>> ---
On Sat, Aug 4, 2012 at 11:35 PM, Phil Dobbin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> just a traceback further to this problem. Hope it helps:
>
> `$ hg log --traceback
[snip]
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/mercurial
> I'm curious if this is still happening. If anyone sees this issue when
> initiating the install from XCode's preferences (*after* this email), please
> let me know.
I can try later this afternoon, if not before and let you (and the list) know.
___
m
> I see that you use many variants in your Portfile. As a rule of thumb most
> functionality should be enabled by default. Couldn’t most be enabled by
> default (possibly as a default_variant)?
Sure; I have no preference either way. My only note is that the
--download-* options shouldn't be used
> Sean, it's up to the maintainers of those ports as to whether they would like
> to incorporate your changes, and for the petsc port, I would encourage you to
> file a bug report with a diff with these changes and explanations about why
> the changes need to be made.
That actually was my plan
> The libraries have not been linked correctly. I assume the first line in
> otool -L /opt/local/lib/petsc/lib/libpetsc.dylib contains the
> worksrcdir, which causes this issue when linking against it.
>
> Please file a bug so the maintainer can fix this.
The PETSc portfile is very wrong, particul
> There was a thread ~1 month ago regarding gfortran that was acting
> strangely. Here's a link to that
> thread: http://lists.macosforge.org/pipermail/macports-dev/2012-May/019098.html
>
> I haven't seen any responses or anything to this, and I was wondering if
> anyone else had run into issues t
> Right. We never really announced the availability of binaries, but they've
> been available for Snow Leopard since last year and Lion since this year.
>
> Is there a reason why you want to build ld64 from source -- is there
> something wrong with the binary on our server? If so, we need to know
> I just tried to "port install ld64", and instead of compiling from source,
> it downloads a .tbz2 package from packages.macports.org which contains the
> binaries. I guess I thought macports always built from source unless you
> added "pkg" to the port command? Thanks for any help.
This is a new
(cc'ing macports-dev)
> The problem is actually with MacPorts 4.3.2. A little more accurately, this
> is NOT an actual bug. The problem is that the behavior you are seeing is
> allowed under the Fortran standard -- that's why selected_int_kind exists in
> the first place.
This is wrong. The Fo
59 matches
Mail list logo
