Dear all,
When I attempt to compile a C program using -march=native I receive a
bunch of errors about nonexistent instructions in temporary assembler
files. This does not happen without that command.
Does anyone have any bright ideas for how to fix this? Has anyone else
had this problem and been
Le 18 mars 2014 à 07:06, Watson Ladd watsonbl...@gmail.com a écrit :
Dear all,
When I attempt to compile a C program using -march=native I receive a
bunch of errors about nonexistent instructions in temporary assembler
files. This does not happen without that command.
Does anyone have any
Hi
On Tuesday March 18 2014 08:54:04 James Linder wrote:
Somewhat OT so would you mind mailing me directly (unless of interest here)
I think it is (for any developer ...)
So … what did you do and how?
I don't have the exact URLs at hand, but there is a description out there on
how to get
On Tuesday March 18 2014 09:43:57 Vincent Habchi wrote:
If you want to use the -march=native switch, use Clang instead (LLVM-AS
handles new extensions correctly).
Or use -march=native -no-avx , or simply -march=core2 if you insist on having
AVX.
Note that when your code isn't optimised for
Salut René,
Le 18 mars 2014 à 10:44, René J.V. Bertin rjvber...@gmail.com a écrit :
On Tuesday March 18 2014 09:43:57 Vincent Habchi wrote:
If you want to use the -march=native switch, use Clang instead (LLVM-AS
handles new extensions correctly).
Or use -march=native -no-avx , or simply
That’s not what the latest Phoronix tests seemed to point out (but with clang
3.4).
http://www.phoronix.com/scan.php?page=articleitem=llvm34_gcc49_compilersnum=1
I agree. Clang and GCC are pretty much neck and neck these days, as far
as my tests go.
Hi
I’ve given Homebrew a quick try in a VM and it doesn’t seem that different in
functionality. (Except that I do wish we had something like Homebrew-cask.)
So, other than the coolness factor (which I guess comes partly from being
“the new thing”, and partly from using Github for all
On Tuesday March 18 2014 10:31:44 you wrote:
That’s not what the latest Phoronix tests seemed to point out (but with
clang 3.4).
http://www.phoronix.com/scan.php?page=articleitem=llvm34_gcc49_compilersnum=1
I agree. Clang and GCC are pretty much neck and neck these days, as far
as my
On 18/03/14 11:14, Vincent Habchi wrote:
Le 18 mars 2014 à 12:01, René J.V. Bertin rjvber...@gmail.com a écrit :
A bit OT, but is clang the reason libeigen doesn't currently build on OS X 10.9?
Er… I think eigen3 was building fine with clang, except the BLAS part which
requires a Fortran
On Mar 18, 2014, at 12:14, Vincent Habchi wrote:
Le 18 mars 2014 à 12:01, René J.V. Bertin rjvber...@gmail.com a écrit :
A bit OT, but is clang the reason libeigen doesn't currently build on OS X
10.9?
Er… I think eigen3 was building fine with clang, except the BLAS part which
Le 18 mars 2014 à 12:28, Chris Jones jon...@hep.phy.cam.ac.uk a écrit :
... and for fortran support, it is fine to mix gfortran from any gcc
compiler, with clang, as there are no issues with mixing c++ runtimes (as
obviously fortran doesn't need this).
That’s fortunate, because otherwise
On Mar 18, 2014, at 00:30, Jonathan Koren wrote:
I’m on Mavricks with MacPorts 2.2.1
I recently upgraded the meld port (@1.8.4), and now when ever I try to run
it, it blows up with an OSError.
(OSError: [Errno 13] Permission denied:
'/opt/local/share/meld/recent-NbPmhP.meldcmp’ )
Marketing. Ease of use.
Davor Cubranic cubra...@stat.ubc.ca wrote:
On Mar 12, 2014, at 2:12 PM, Art McGee amc...@gmail.com wrote:
The problem is that the presentation of the case for supporting
MacPorts was confusing and unconvincing, so usage statistics are not
going to help in that matter.
On Mar 17, 2014, at 22:42, Davor Cubranic wrote:
I’ve given Homebrew a quick try in a VM and it doesn’t seem that different in
functionality. (Except that I do wish we had something like Homebrew-cask.)
For those of us not familiar with Homebrew: what is this feature? what does it
do?
On Tue, Mar 18, 2014 at 8:28 AM, Ryan Schmidt ryandes...@macports.orgwrote:
On Mar 17, 2014, at 22:42, Davor Cubranic wrote:
I've given Homebrew a quick try in a VM and it doesn't seem that
different in functionality. (Except that I do wish we had something like
Homebrew-cask.)
For those
On Mar 18, 2014, at 1:28pm, Ryan Schmidt-24 wrote:
I’ve given Homebrew a quick try in a VM and it doesn’t seem that
different in functionality. (Except that I do wish we had something
like Homebrew-cask.)
For those of us not familiar with Homebrew: what is this feature? what does
it do?
Just curious. What's the story about the absence of the ports database for
a couple of days it seems?
Thanks.
Comer
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Apple infrastructure is moving things around, and putting them back together.
On Mar 18, 2014, at 13:14, Comer Duncan comer.dun...@gmail.com wrote:
Just curious. What's the story about the absence of the ports database for a
couple of days it seems?
On Tue, Mar 18, 2014 at 6:42 AM, Clemens Lang c...@macports.org wrote:
- homebrew doesn't try as hard as MacPorts to make builds reproducible. If
you install vim, it'll use the first python available. When that's system
python it uses that, if it's homebrew python it'll use that (and if its
On Mar 18, 2014, at 1:36 PM, Arno Hautala a...@alum.wpi.edu wrote:
On Tue, Mar 18, 2014 at 6:42 AM, Clemens Lang c...@macports.org wrote:
- homebrew doesn't try as hard as MacPorts to make builds reproducible. If
you install vim, it'll use the first python available. When that's system
On Tue, Mar 18, 2014 at 1:36 PM, Arno Hautala a...@alum.wpi.edu wrote:
On Tue, Mar 18, 2014 at 6:42 AM, Clemens Lang c...@macports.org wrote:
- homebrew doesn't try as hard as MacPorts to make builds reproducible.
If you install vim, it'll use the first python available. When that's
system
homebrew will or will appear to get a user to their desired state of “I just
need X installed” faster than MacPorts.
Their users simply don’t care about what MacPorts does: it isn’t that homebrew
has a feature, it’s that homebrew won’t seem to get in the way.
On Mar 18, 2014, at 13:36, Arno
Hi,
I'm pretty sure they consider this a strength. I already have Python!
Why is MacPorts trying to install a new version!?
Certainly, but it leads to situations such as
https://github.com/Valloric/YouCompleteMe/issues/8. They might not have to deal
with python because they're not managing
Hi,
homebrew will or will appear to get a user to their desired state of “I just
need X installed” faster than MacPorts.
Their users simply don’t care about what MacPorts does: it isn’t that
homebrew has a feature, it’s that homebrew won’t seem to get in the way.
Sure, I'd consider that to
Not much to do with MacPorts (I hope), but I stumbled across a
/usr/include/MacTypes.h file today on my 10.9.2 VM, dated March 17th around 09h
(=AM). I noticed it because of clashes in the Boolean typedef with the X11
headers that I never had, at least not before I installed Xcode 5.1 . My VM
On Tue, Mar 18, 2014 at 2:10 PM, René J.V. Bertin rjvber...@gmail.comwrote:
Not much to do with MacPorts (I hope), but I stumbled across a
/usr/include/MacTypes.h file today on my 10.9.2 VM, dated March 17th around
09h (=AM). I noticed it because of clashes in the Boolean typedef with the
X11
On Mar 18, 2014, at 3:01 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Mar 18, 2014, at 12:54, Daniel J. Luke dl...@geeklair.net wrote:
GitHub plus not having to learn/use tcl seem to be the major features that
pull people/create interest from what I've seen (but I haven't looked in on
On Mar 18, 2014, at 12:54, Daniel J. Luke dl...@geeklair.net wrote:
GitHub plus not having to learn/use tcl seem to be the major features that
pull people/create interest from what I've seen (but I haven't looked in on
it in a while).
…right, instead of you have to learn/use ruby. Six of
They seemed to acquire a lot of traction on the basis of marketing;
specifically:
- Truthiness (an assortment of “advantages” that turned out not to be,
claims that ignored technical accuracy and nuance, and claims quite simply
rooted in ignorance), and
- Outright negative
On Tue, Mar 18, 2014 at 2:27 PM, Landon Fuller land...@macports.org wrote:
They seemed to acquire a *lot* of traction on the basis of marketing;
specifically:
- Truthiness (an assortment of advantages that turned out not to be,
claims that ignored technical accuracy and nuance, and claims
On Mar 18, 2014, at 3:57 PM, Eric A. Borisch ebori...@macports.org wrote:
However, perhaps we should take a page from their book. Look at the homebrew
homepage (http://brew.sh/)
* It would be nice a similar minimalist, here is what macports does for
you landing page.
* A one line
Hi,
We use MacPorts to install the NRPE client on most of our OS X boxes, but I
have a couple of boxes that have a weird behaviour. After a reboot, the
nrpe.wrapper is loaded:
# ps auxwww | grep nrpe
root 556 0.0 0.0 2467372 1208 ?? Rs4:31PM 0:00.01
On Mar 18, 2014, at 12:57 PM, Eric A. Borisch ebori...@macports.org wrote:
However, perhaps we should take a page from their book. Look at the homebrew
homepage (http://brew.sh/)
* It would be nice a similar minimalist, here is what macports does for
you landing page.
* A one line
* More use of ANSI colors in the log messages (used to distinguish the start
of each port, etc., and maybe with different colors for different phases)…
all tunable, of course, for those who don’t like color.
We should also take a look at `port search', which can currently produce
enormous
On Mar 18, 2014, at 16:35, Clemens Lang wrote:
* A careful review of what we emit, and when (we don’t clearly distinguish
when a port was loaded from a build-bot vs built by hand, unless you know
what to look for), etc.
Agreed. We should also remove some of the clean messages that might be
On 2014-03-18 22:09, James Berry wrote:
For the website, I think the following would help:
* Updated design, colors, etc.
That has always been the plan, but it just needs someone to do it.
I think the last update on the website design dates back to 2007...
I would even replace the website
On 18 Mar 2014, at 23:06 , Rainer Müller rai...@macports.org wrote:
also getting rid of one of the duplicated installation instructions on
website/wiki/guide.
Well, that’s another big endeavour, because we finally should find a way to
condense the information from all three sources + man
Pretty sure It’s opt-in. So it’s the antithesis of NSA :-p
On Mar 18, 2014, at 18:12, mk-macpo...@techno.ms wrote:
Well, the statistics gathering is something I would also like to see
(awaiting the new release impatiently), but it’s a little worrisome, because
it has a touch of NSA
On 18 Mar 2014, at 23:15 , Jeremy Lavergne jer...@lavergne.gotdns.org wrote:
Pretty sure It’s opt-in. So it’s the antithesis of NSA :-p
I am aware of that, of course. ;-)
___
macports-users mailing list
macports-users@lists.macosforge.org
On Tue, Mar 18, 2014 at 5:35 PM, Clemens Lang c...@macports.org wrote:
* More use of ANSI colors in the log messages (used to distinguish the
start
of each port, etc., and maybe with different colors for different
phases)...
all tunable, of course, for those who don't like color.
We
Hi,
No! Homebrew's search functionality is my biggest problem with it. The
columns you mentioned make it hard to read because it makes it harder to
see how they are sorted. The alphabetization seems to be in order by column
at first, but then at some random row the alphabetical order will
On Tue, Mar 18, 2014 at 5:43 PM, Ryan Schmidt ryandes...@macports.org wrote:
Also, consider the OS X startup progress bar, back when OS X had one:
originally it was very accurate, but by Tiger it had been changed to just
advance at a more or less constant rate regardless what was happening;
On Tue, Mar 18, 2014 at 7:48 PM, Clemens Lang c...@macports.org wrote:
For less than 10 results, the following looks nice to my eyes:
gt; port search git
portversion description
--- ---
babl-devel 0.1.11-20140305 Babl is a library for
Yeah, I think tcl is one of the things that confounds people the most. Not
really learned that much anymore. I learned it long ago for CAD tools from
IBM.
But really, both Homebrew and Macports are domain specific languages from
the port writers perspective. You've got to learn it anyway. People
On Tue, Mar 18, 2014 at 3:27 PM, Landon Fuller land...@macports.org wrote:
MacPorts driving you to drink?
I hate that. Turned me off the whole project.
--Mark
___
Mark E. Anderson e...@emer.net
___
macports-users mailing list
At 12:48 AM +0100 3/19/14, Clemens Lang wrote:
[...]
And I'm all for keeping that if there are less than, say 10 search
results. When there are more than 10 results, ...
Much of the time, the volume of search results is inflated due to
perl, python and php subports. (Eg, search for
At 11:06 PM +0100 3/18/14, Rainer Müller wrote:
[...] I would even replace the website with the Trac wiki front page
altogether, also getting rid of one of the duplicated installation
instructions on website/wiki/guide.
I understand that the next release of MacPorts
will check for a correct
On Tuesday, March 18, 2014, Clemens Lang c...@macports.org wrote:
Also, we really need to work on the dependency calculation stuff to print
a plan of action before starting and print progress information (building
port x of y) while building.
I wrote a little script for myself that goes and
On Tue, Mar 18, 2014 at 9:39 PM, Craig Treleaven ctrelea...@cogeco.cawrote:
Our 'extra steps', seem to trip up at least half our new users.
Another big one would be handling major OS upgrades more cleanly. I think
the two issues are that MacPorts detects certain configurations upon
install and
On Tue, Mar 18, 2014 at 9:56 PM, Eric A. Borisch ebori...@macports.orgwrote:
I wrote a little script for myself that goes and queries
packages.macports.org and determines if a port will be built or use a
package; it spits out a dot graph of dependencies colored by which is going
to happen.
On Mar 18, 2014, at 19:02, Arno Hautala a...@alum.wpi.edu wrote:
Another big one would be handling major OS upgrades more cleanly. I think the
two issues are that MacPorts detects certain configurations upon install and
generally all ports need to be rebuilt. Making MacPorts detect the OS
This mostly already exists: it’s currently only for packages that are installed.
port echo requested
port setrequested …
Presently, to get your between-installs behavior, you’d dump the output of echo
requested to a file then read it back in. Hilariously, our Migration page (!!!
this is
52 matches
Mail list logo
