Re: How to make c++ realize empty character constant ''?

2013-12-09 Thread Chris Jones



If you're trying to make a C/C++ string, perhaps you want '\0'. But I
can't tell what language you are working with or what exactly you are
trying to accomplish.


The code that was posted by the OP sure isn't C++... Been a while since 
I used it, but looks like fortran to me..


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: fife Unknown Horizons Game

2013-12-09 Thread Ryan Schmidt

On Dec 8, 2013, at 20:01, Mark Anderson wrote:

 I tried sometime ago, fife is not the easiest thing to build on the mac. But 
 I'd be willing to help out. If you can help figure out how to get it to 
 compile, we can make a port file.

I appear to have tried to update the port to 0.3.3r3 in August. Let me see what 
I can do.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: port install painfully slow

2013-12-09 Thread Brian D. McGrew
On Sun, Dec 8, 2013 at 8:49 AM, Brian D. McGrew 
br...@visionpro.commailto:br...@visionpro.com wrote:
dyld: DYLD_ environment variables being ignored because main executable 
(/usr/bin/sudo) is setuid or setgid

I suggest you find out what is setting these, as MacPorts executes most things 
*not* as root and they can be causing problems (which could be minor or quite 
major). OS X isn't Linux; setting DYLD_* variables for anything other than 
temporary specific testing is almost always wrong.

That is very interesting…  I unset the DYLD_* stuff and all is good.  Never, 
ever seen that before.  We set the DLYD_* stuff on our own for our software 
running on the Mac.  Our package is a native Linux app, however, a few of us 
prefer the Mac so an enterprising architect got us compiling on the Mac and 
it's just worked all along.  Never seen any problems until now.

-b

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: fife Unknown Horizons Game

2013-12-09 Thread Ryan Schmidt

On Dec 9, 2013, at 04:43, Ryan Schmidt wrote:

 On Dec 8, 2013, at 20:01, Mark Anderson wrote:
 
 I tried sometime ago, fife is not the easiest thing to build on the mac. But 
 I'd be willing to help out. If you can help figure out how to get it to 
 compile, we can make a port file.
 
 I appear to have tried to update the port to 0.3.3r3 in August. Let me see 
 what I can do.

0.3.5 appears to build fine on Mountain Lion with the changes I had already 
been working on. I’ll commit it today.

There is a Mavericks-specific build problem with GLee; I filed an upstream bug 
report.


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: port install painfully slow

2013-12-09 Thread Ryan Schmidt

On Dec 9, 2013, at 06:06, Brian D. McGrew wrote:
 On Sun, Dec 8, 2013 at 8:49 AM, Brian D. McGrew wrote:
 dyld: DYLD_ environment variables being ignored because main executable 
 (/usr/bin/sudo) is setuid or setgid
 
 I suggest you find out what is setting these, as MacPorts executes most 
 things *not* as root and they can be causing problems (which could be minor 
 or quite major). OS X isn't Linux; setting DYLD_* variables for anything 
 other than temporary specific testing is almost always wrong.
 
 That is very interesting…  I unset the DYLD_* stuff and all is good.  Never, 
 ever seen that before.  We set the DLYD_* stuff on our own for our software 
 running on the Mac.  Our package is a native Linux app, however, a few of us 
 prefer the Mac so an enterprising architect got us compiling on the Mac and 
 it's just worked all along.  Never seen any problems until now.

Don’t use DYLD_LIBRARY_PATH; it tells the OS you know better than it where 
libraries are located, and to look only in the paths you specify; that’s seldom 
what you want.

You can use DYLD_FALLBACK_LIBRARY_PATH as a stopgap measure; it tells the OS to 
look in the specified locations *after* all the other locations where it would 
normally look.

The correct long-term solution is to fix your libraries so they’re compiled 
with the correct -install_name parameter so that these variables aren’t needed 
at runtime.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: port install painfully slow

2013-12-09 Thread Brian D. McGrew
 On Dec 9, 2013, at 06:06, Brian D. McGrew wrote:
 On Sun, Dec 8, 2013 at 8:49 AM, Brian D. McGrew wrote:
 dyld: DYLD_ environment variables being ignored because main executable 
 (/usr/bin/sudo) is setuid or setgid
 
 I suggest you find out what is setting these, as MacPorts executes most 
 things *not* as root and they can be causing problems (which could be minor 
 or quite major). OS X isn't Linux; setting DYLD_* variables for anything 
 other than temporary specific testing is almost always wrong.
 
 That is very interesting…  I unset the DYLD_* stuff and all is good.  Never, 
 ever seen that before.  We set the DLYD_* stuff on our own for our software 
 running on the Mac.  Our package is a native Linux app, however, a few of us 
 prefer the Mac so an enterprising architect got us compiling on the Mac and 
 it's just worked all along.  Never seen any problems until now.
 
 Don’t use DYLD_LIBRARY_PATH; it tells the OS you know better than it where 
 libraries are located, and to look only in the paths you specify; that’s 
 seldom what you want.
 
 You can use DYLD_FALLBACK_LIBRARY_PATH as a stopgap measure; it tells the OS 
 to look in the specified locations *after* all the other locations where it 
 would normally look.
 
 The correct long-term solution is to fix your libraries so they’re compiled 
 with the correct -install_name parameter so that these variables aren’t 
 needed at runtime.

Ah, right, thanks for the clarification.  We set DYLD_FALLBACK_LIBRARY_PATH, 
not the other.  But, I don't set that in a new terminal.  I have to run a 
script that sets up my build environment, which is 'usually' the first thing I 
do.  So popping a new terminal and running port without my build environment 
works fine.  But, if I set my env and DYLD_FALLBACK… is set, it no workee…  
very slow, don't know why.  but the fix, I just won't have DYLD_ set when I run 
port.  Still, never seen this before and if anyone knows why it's happening, 
I'd be interested in knowing.

-b
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: How to make c++ realize empty character constant ''?

2013-12-09 Thread Jean Gobin
It seems to me you are trying to assign a character value to a string.

A character is a single 8-bit (or 9 or 10 or 16 or 32 ...) value. A string
is a series of characters, terminated or not.

Assuming you have the proper classes, you overloaded what needs to be, at
best your assignment should look like

frac_str = ;

J.


On Mon, Dec 9, 2013 at 4:51 AM, Chris Jones jon...@hep.phy.cam.ac.ukwrote:


  If you're trying to make a C/C++ string, perhaps you want '\0'. But I
 can't tell what language you are working with or what exactly you are
 trying to accomplish.


 The code that was posted by the OP sure isn't C++... Been a while since I
 used it, but looks like fortran to me..


 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users




-- 
Jean Gobin, Ing., CCENT, CCNA, CCNA Security
http://newsfromjean.blogspot.com/
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Using gcc/gfortran 4.8 in MacPorts

2013-12-09 Thread Gustavo Seabra
Hi all,

Please forgive-me the ignorance if this seems to simple a question.

I installed gcc4.8 from MacPorts, and now I want to use its compilers,
especially gfortran. However, although they are in the path, their names
are different, such as gfortran-mp-4.8, such as they are not seen when
the command gfortran is issued.

I tried to see what is working and got:

$ port select --list gcc

Available versions for gcc:

mp-gcc48

none (active)

however, for gfortran:

$ port select --list gfortran

Warning: Unable to get active selected version: The specified group
'gfortran' does not exist.

Error: The 'list' command failed: The specified group 'gfortran' does not
exist.

I tried to activate the MacPorts gcc set by:

$ sudo port select --set gcc mp-gcc48

Password:

Selecting 'mp-gcc48' for 'gcc' succeeded. 'mp-gcc48' is now active.

And now the correct gcc is working:

$ which gcc

/opt/local/bin/gcc

however, still nothing is set for gfortran:

$ which gfotran

$
(returns nothing)


So, my question is this: how should I activate the whole gcc48 set?
Especially, I need to use gcc/gfortran.

BTW, shouldn't this be activated by default when I install gcc48?

Thanks,
Gustavo Seabra http://goo.gl/7Cphf
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Using gcc/gfortran 4.8 in MacPorts

2013-12-09 Thread Brandon Allbery
On Mon, Dec 9, 2013 at 9:30 AM, Gustavo Seabra gustavo.sea...@gmail.comwrote:

 however, still nothing is set for gfortran:

 $ which gfotran

 $
 (returns nothing)


pyanfar:10004 Z$ type gfortran
gfortran is /opt/local/bin/gfortran

Check for typos :)

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: How to make c++ realize empty character constant ''?

2013-12-09 Thread Brandon Allbery
On Sun, Dec 8, 2013 at 1:35 PM, Gmail yangz...@gmail.com wrote:

 I am trying to compile the following statements using CPP.


This is a (formerly common) abuse of CPP and nobody can guarantee the
result. I *very strongly* recommend you contact whoever provided whatever
it is you are working with and get them to stop using cpp.

The message you got was a warning, not an error. This warning can be
suppressed (add parameters: -Wno-invalid-pp-token -Wno-unicode
-Wno-trigraphs) but very little can be done if clang's cpp is producing
output you don't expect.

Worst case you can try making a gcc the user default compiler:

sudo port install gcc48  sudo port select --set gcc mp-gcc48

and then find and run its cpp. I can't guarantee future versions of gcc
will continue to work, though, as there is no guarantee whatsoever that cpp
will work on things that are not C/C++.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: port install painfully slow

2013-12-09 Thread Brandon Allbery
On Mon, Dec 9, 2013 at 7:43 AM, Brian D. McGrew br...@visionpro.com wrote:

 Ah, right, thanks for the clarification.  We set
 DYLD_FALLBACK_LIBRARY_PATH, not the other.  But, I don't set that in a new
 terminal.  I have to run a script that sets up my build environment, which
 is 'usually' the first thing I do.  So popping a new terminal and running
 port without my build environment works fine.  But, if I set my env and
 DYLD_FALLBACK… is set, it no workee…  very slow, don't know why.  but the
 fix, I just won't have DYLD_ set when I run port.  Still, never seen this
 before and if anyone knows why it's happening, I'd be interested in knowing.


We can't tell for certain without knowing what your environment looks like,
but it is very likely that your replacement libraries are shadowing some
standard function in a way that breaks MacPorts (and may affect other OS X
native software although perhaps not as drastically). There are some
debugging DYLD_ variables you can set to show what is getting bound from
where, but without knowing what's in the libraries you have been forcing it
to use we can't even guess.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Using gcc/gfortran 4.8 in MacPorts

2013-12-09 Thread Gustavo Seabra
Oops.. Sorry!

Gustavo Seabra http://goo.gl/7Cphf
Professor Adjunto, Departamento de Química Fundamental
Coordenador, CENAPAD-PE
Universidade Federal de Pernambuco
Fone: +55-81-2126-7450


On Mon, Dec 9, 2013 at 11:42 AM, Brandon Allbery allber...@gmail.comwrote:

 On Mon, Dec 9, 2013 at 9:30 AM, Gustavo Seabra 
 gustavo.sea...@gmail.comwrote:

 however, still nothing is set for gfortran:

 $ which gfotran

 $
 (returns nothing)


 pyanfar:10004 Z$ type gfortran
 gfortran is /opt/local/bin/gfortran

 Check for typos :)

 --
 brandon s allbery kf8nh   sine nomine
 associates
 allber...@gmail.com
 ballb...@sinenomine.net
 unix, openafs, kerberos, infrastructure, xmonad
 http://sinenomine.net

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: How to make c++ realize empty character constant ''?

2013-12-09 Thread Gmail
Hi Chris
Yes, it is fortran code. I am not sure why it uses CPP to compile it. From the 
compilation statement, Fortran code is converted to .b file and then to compile 
it. I am not sure why.


On Dec 9, 2013, at 3:51 AM, Chris Jones jon...@hep.phy.cam.ac.uk wrote:

 
 If you're trying to make a C/C++ string, perhaps you want '\0'. But I
 can't tell what language you are working with or what exactly you are
 trying to accomplish.
 
 The code that was posted by the OP sure isn't C++... Been a while since I 
 used it, but looks like fortran to me..
 

Thank you
Bruce
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: fife Unknown Horizons Game

2013-12-09 Thread Jean-François Caron
I was able to compile fifengine from git by following these instructions:

http://wiki.unknown-horizons.org/w/MacOS_build_notes

Once fife is compiled, the Unknown Horizons game is actually just written in 
python, so it should be easy to make a port for it.  Apparently they are trying 
to move away from using the libguichan (currently provided by a port) to some 
other system that isn't available in macports.  But for now it works with only 
minor problems.

Jean-François

On 2013-12-09, at 04:33 , Ryan Schmidt wrote:

 
 On Dec 9, 2013, at 04:43, Ryan Schmidt wrote:
 
 On Dec 8, 2013, at 20:01, Mark Anderson wrote:
 
 I tried sometime ago, fife is not the easiest thing to build on the mac. 
 But I'd be willing to help out. If you can help figure out how to get it to 
 compile, we can make a port file.
 
 I appear to have tried to update the port to 0.3.3r3 in August. Let me see 
 what I can do.
 
 0.3.5 appears to build fine on Mountain Lion with the changes I had already 
 been working on. I’ll commit it today.
 
 There is a Mavericks-specific build problem with GLee; I filed an upstream 
 bug report.
 
 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: fife Unknown Horizons Game

2013-12-09 Thread Ryan Schmidt

On Dec 9, 2013, at 11:35, Jean-François Caron wrote:

 I was able to compile fifengine from git by following these instructions:
 
 http://wiki.unknown-horizons.org/w/MacOS_build_notes

On Mavericks?

If not, you can accomplish the same thing now with:

sudo port sync
sudo port install fife

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: fife Unknown Horizons Game

2013-12-09 Thread Jean-François Caron
Sorry I should have mentioned, I am on Lion 10.7.5.  The fife port failed to 
build for me with the same error as this ticket: 
https://trac.macports.org/ticket/39581  

I now see that it's been updated.

Jean-François

On 2013-12-09, at 09:40 , Ryan Schmidt wrote:

 
 On Dec 9, 2013, at 11:35, Jean-François Caron wrote:
 
 I was able to compile fifengine from git by following these instructions:
 
 http://wiki.unknown-horizons.org/w/MacOS_build_notes
 
 On Mavericks?
 
 If not, you can accomplish the same thing now with:
 
 sudo port sync
 sudo port install fife
 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Using gcc/gfortran 4.8 in MacPorts

2013-12-09 Thread Ryan Schmidt
On Dec 9, 2013, at 08:30, Gustavo Seabra wrote:

 BTW, shouldn't this be activated by default when I install gcc48?

No; MacPorts doesn’t distinguish between ports you requested to install and 
ports that were installed as a dependency. If gcc48 is installed, MacPorts 
doesn’t know whether you want “gcc” et al to be changed to point to it. You 
might even have multiple gcc ports installed. You inform MacPorts which one you 
want “gcc” to point to, if any, by using “port select gcc”.


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Using gcc/gfortran 4.8 in MacPorts

2013-12-09 Thread Gustavo Seabra
On Mon, Dec 9, 2013 at 4:03 PM, Ryan Schmidt ryandes...@macports.orgwrote:

 On Dec 9, 2013, at 08:30, Gustavo Seabra wrote:

  BTW, shouldn't this be activated by default when I install gcc48?

 No; MacPorts doesn’t distinguish between ports you requested to install
 and ports that were installed as a dependency. If gcc48 is installed,
 MacPorts doesn’t know whether you want “gcc” et al to be changed to point
 to it. You might even have multiple gcc ports installed. You inform
 MacPorts which one you want “gcc” to point to, if any, by using “port
 select gcc”.


OK, I see now.
Thanks,
Gustavo Seabra http://goo.gl/7Cphf
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users