Re: libcryptopp needs updating (is Raphael will with us?)

2013-05-23 Thread Tabitha McNerney
Hi Raphael,

Thank you so very much for updating libcryptopp! I wasn't aware that I
could get the maintainer email address the way you suggested. Instead, I
had searched my email archives for MacPorts and sent the email to
at...@mps.mpg.de (that may have been a different Raphael? Sorry).

-Tabitha



On Wed, May 22, 2013 at 1:59 AM, Raphael Straub raph...@macports.orgwrote:

 Hi,

 Tabitha McNerney wrote:
  I noticed that the port for libcryptopp is out of date (current port
 fetches version 5.6.1 which was released in 2010 ... a 2013 version came
 out, 5.6.2). I think Raphael Attie was one of the maintainers and I tried
 emailing him but his email bounced back to me.

 you must have used the wrong e-mail address. port info --maintainer
 libcryptopp tells you the right one.

  Is there anyone who could easily update the libcryptopp port if its not
 an inconvenience to do so?

 I updated libcryptopp to version 5.6.2 in r106315, see 
 https://trac.macports.org/changeset/106315.

 Regards,
 Raphael


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


Re: Refresher on gcc port and the executables

2013-05-23 Thread Tabitha McNerney
On Wed, May 22, 2013 at 1:15 PM, Lawrence Velázquez lar...@macports.orgwrote:

 On May 22, 2013, at 8:17 AM, Ryan Schmidt ryandes...@macports.org wrote:

  On May 22, 2013, at 05:25, Tabitha McNerney wrote:
 
  Its been some time since I looked more deeply at the GCC ports. On a
 new Mac recently I installed MacPorts and then specifically installed gcc47
 into my port prefix path /opt/local
 
  I looked today and realized there are several binaries (in
 /opt/local/bin), such as:
 
  gcc-ranlib-mp-4.7
  gcc-nm-mp-4.7
  gcc-mp-4.7
  gcc-ar-mp-4.7
  g++-mp-4.7
 
  and:
 
  x86_64-apple-darwin12-gcc-ranlib-mp-4.7
  x86_64-apple-darwin12-gcc-nm-mp-4.7
  x86_64-apple-darwin12-gcc-mp-4.7
  x86_64-apple-darwin12-gcc-ar-mp-4.7
  x86_64-apple-darwin12-gcc-4.7.2
  x86_64-apple-darwin12-g++-mp-4.7
 
  I forgot what the difference means in the above examples.

 There is no difference. They're hard links to the same files:

 % for f in {gcc{-ranlib,,-nm,-ar},g++}-mp-4.7; do
 forstat -f 'inode %i: %N'
 /opt/local/bin/{,x86_64-apple-darwin12-}$f;
 forecho;
 for done
 inode 40693975: /opt/local/bin/gcc-ranlib-mp-4.7
 inode 40693975: /opt/local/bin/x86_64-apple-darwin12-gcc-ranlib-mp-4.7

 inode 40693973: /opt/local/bin/gcc-mp-4.7
 inode 40693973: /opt/local/bin/x86_64-apple-darwin12-gcc-mp-4.7

 inode 40693974: /opt/local/bin/gcc-nm-mp-4.7
 inode 40693974: /opt/local/bin/x86_64-apple-darwin12-gcc-nm-mp-4.7

 inode 40693972: /opt/local/bin/gcc-ar-mp-4.7
 inode 40693972: /opt/local/bin/x86_64-apple-darwin12-gcc-ar-mp-4.7

 inode 40693966: /opt/local/bin/g++-mp-4.7
 inode 40693966: /opt/local/bin/x86_64-apple-darwin12-g++-mp-4.7

 The argv[0] each executable sees does depend on the name used to call it,
 so runtime behavior might be different, or even incorrect. (I have not
 tried it.) But they're still just different names for the same files.



Thank you for pointing that out, I hadn't inspected enough to realize they
are hard links.




  If I want to compile some C or C++ code without any help from Apple's
 tools (for example the way I might do on a Linux system), would I simply
 use the top list (gcc* and g++*) and avoid the bottom list (x86*)?
 
  Yes.

 How divorced are you hoping to get from Apple's tools? Our GCC ports
 still use, at a minimum, Apple's assembler and archiver (via cctools) and
 linker (via ld64), as well as OS X's bundled zlib.


For a particular project I am working on, my boss asked me if there was a
way to compile some code from source (which depends on and will use of some
advanced cryptography potentially for highly sensitive business), such
that, in his words, it is not dependent on any compiler tools from a
corporation like Apple, Google or Microsoft and he said it should be the
same as what is used by open source Linux distros. So this would mean gcc
but it makes me think I might need to do something unique such as making
gcc from source on my own since my boss doesn't want there to be any
company fingerprints (he's really worried but also its his job that could
be on the line). For special purposes, is it fairly easy to make gcc and
g++ from source, on OS X, in a way that is in fact divorced from the
Apple tools?




  I also have Xcode installed on this Mac and for some code to compile I
 do not want to use Apple's gcc bundled with Xcode. So given the above, do I
 need to use gcc_select and if so any suggestions on how best to do so?
 
  If you want gcc to be a MacPorts compiler instead, use sudo port
 select gcc (which was several years ago known as gcc_select). You can
 learn more about how to use port select by running port help select.

 You might also be able to configure Xcode to run your desired compiler
 directly (e.g., /opt/local/bin/gcc-mp-4.7).


If I do this, the same will apply from what you wrote above, true (about
the assembler, archiver, linker, zlib)?

Thank you for the suggestions!

-Tabitha




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


Re: Refresher on gcc port and the executables

2013-05-23 Thread Mojca Miklavec
On Thu, May 23, 2013 at 9:15 AM, Tabitha McNerney wrote:

 For a particular project I am working on, my boss asked me if there was a
 way to compile some code from source (which depends on and will use of some
 advanced cryptography potentially for highly sensitive business), such that,
 in his words, it is not dependent on any compiler tools from a corporation
 like Apple, Google or Microsoft and he said it should be the same as what
 is used by open source Linux distros. So this would mean gcc but it makes
 me think I might need to do something unique such as making gcc from source
 on my own since my boss doesn't want there to be any company fingerprints
 (he's really worried but also its his job that could be on the line). For
 special purposes, is it fairly easy to make gcc and g++ from source, on OS
 X, in a way that is in fact divorced from the Apple tools?

Read this:
http://scienceblogs.com/goodmath/2007/04/15/strange-loops-dennis-ritchie-a/

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


Re: Refresher on gcc port and the executables

2013-05-23 Thread Ryan Schmidt

On May 23, 2013, at 02:15, Tabitha McNerney wrote:

 For a particular project I am working on, my boss asked me if there was a way 
 to compile some code from source (which depends on and will use of some 
 advanced cryptography potentially for highly sensitive business), such that, 
 in his words, it is not dependent on any compiler tools from a corporation 
 like Apple, Google or Microsoft and he said it should be the same as what 
 is used by open source Linux distros. So this would mean gcc but it makes me 
 think I might need to do something unique such as making gcc from source on 
 my own since my boss doesn't want there to be any company fingerprints (he's 
 really worried but also its his job that could be on the line). For special 
 purposes, is it fairly easy to make gcc and g++ from source, on OS X, in a 
 way that is in fact divorced from the Apple tools?

If you don't trust the compilers provided by Apple in Xcode, then you can't 
trust any compiler built by MacPorts, since MacPorts will build its compilers 
using a compiler from Xcode.

Not trusting your vendor's compiler seems needlessly paranoid. Then again I 
don't write security-critical software.

Using, say, a compiler binary provided by Apple to compile your software does 
not somehow give Apple any rights to your software. That would be silly.

You could ask your boss to clarify his intent, but it sounds like what he wants 
is for the source code you write to not *require* a specific compiler, but to 
be *portable* to any normal C compiler. That's a reasonable requirement, and is 
one that's followed by most of the software ported by MacPorts. The C language 
is standardized, as is C++; assuming you write standards-compliant code, and 
don't use e.g. Apple- or Microsoft-specific language or compiler extensions, 
you should have no problem compiling it on a variety of compilers. You can 
compile your code with a variety of compilers on a variety of systems to verify 
if you're succeeded in this goal.

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


launchctl: failed: -10

2013-05-23 Thread Eneko Gotzon Ares

Hi all computer savvy :) Here Eneko rethinking how to use MacPorts :)

About the generated startup items –that will aid in starting dbus with  
launchd–, Terminal says that to start them, and to cause them to  
launch at startup, the following commands must be executed:


%% sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus- 
system.plist

Successfully executed.

%% launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus- 
session.plist

Terminal shows the ensuing error message:
launchctl: CFURLWriteDataAndPropertiesToResource(/Library/LaunchAgents/ 
org.freedesktop.dbus-session.plist) failed: -10


I want to understand and fix the error, but I found very few answers  
in the Internet and, for common men, they are quite difficult to  
understand, so I need your advice. What happens? What to do?


Thank you very much –and have a great life!– ;)
--
Eneko Gotzon Ares

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


Re: launchctl: failed: -10

2013-05-23 Thread Brandon Allbery
On Thu, May 23, 2013 at 9:57 AM, Eneko Gotzon Ares enekogot...@gmail.comwrote:

 %% launchctl load -w /Library/LaunchAgents/org.**
 freedesktop.dbus-session.plist
 Terminal shows the ensuing error message:
 launchctl: CFURLWriteDataAndPropertiesToR**esource(/Library/LaunchAgents/*
 *org.freedesktop.dbus-session.**plist) failed: -10


Are you on Leopard or earlier? -w used to edit the actual plist, which
doesn't work for LaunchAgents as the plist is owned by root. (On Snow
Leopard and later, the disabled status is stored in a per-user state file,
avoiding this issue. This also means it's actually per user instead of all
users.)

On older OS X, you'll need to edit the plist as root and change the value
of the Disabled key to False, then run the launchctl command without -w (or
just log out and back in).

-- 
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


wine/quicktime installer

2013-05-23 Thread René J.V. Bertin
Hello,

Am I alone in not being able to install Apple QuickTime under the current wine 
version (1.5.29)?

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


Re: wine/quicktime installer

2013-05-23 Thread Chris Jones


On 23 May 2013, at 05:29 PM, René J.V. Bertin rjvber...@gmail.com wrote:

 Hello,
 
 Am I alone in not being able to install Apple QuickTime under the current 
 wine version (1.5.29)?

Just curious, but why would you want to... You are already on a mac, so just 
install the native version ?

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


Re: wine/quicktime installer

2013-05-23 Thread René J.V. Bertin

On May 23, 2013, at 22:28, Chris Jones wrote:
 
 Hello,
 
 Am I alone in not being able to install Apple QuickTime under the current 
 wine version (1.5.29)?
 
 Just curious, but why would you want to... You are already on a mac, so just 
 install the native version ?
 

Well, I may not have tried hard enough, but I doubt that the win32 apps using 
QuickTime (and QT components) that I develop would work with the Mac version 
O:^)

It'd be very nice to be able to avoid firing up a VM for just a couple of 
tweaks to my code!

R.

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


Re: launchctl: failed: -10

2013-05-23 Thread Eneko Gotzon Ares

On 23 May 2013, at 16:10, Brandon Allbery wrote:

%% launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus- 
session.plist

Shows error message:
launchctl: CFURLWriteDataAndPropertiesToResource(/Library/ 
LaunchAgents/org.freedesktop.dbus-session.plist) failed: -10


Are you on Leopard or earlier?

Yes, I'm running Leopard.

On older OS X, you'll need to edit the p-list as root and change the  
value of the Disabled key to False, then run the launchctl command  
without -w (or just log out and back in).

It is my first attempt as root (or superuser). Go for it!

Brandon, thank you very much for illuminate my way :) and take care.
--
Eneko Gotzon Ares

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


Problems installing ffmpeg 1.2.1

2013-05-23 Thread John King
Having a problem getting the 1.2.1 version installed.  When I search for 
ffmpeg in available ports, the result I see is ffmpeg 1.2.1 and the 
associated Portfile also lists 1.2.1 as the version.


However, when I run sudo port install ffmpeg +nonfree, I get version 
1.1.2 installed.


If I then uninstall 1.1.2 and run ffmpeg @1.2.1+nonfree I still get the 
1.1.2 version installed.


Is there some other syntax or procedure to force the installation of 
1.2.1 rather than 1.1.2?  Maybe download the Portfile and run it locally?


I need the 1.2.1 version to use some specific encoding command line 
parameters.


--
John King
Applications Programmer
Learning Systems Group
Educational Technology Services
9 Dwinelle Hall - Mail
117 Dwinelle Hall - Office
University of California
Berkeley, CA 94720-2535
Phone: 510-529-5074
Email: jo...@media.berkeley.edu

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


Re: Problems installing ffmpeg 1.2.1

2013-05-23 Thread Brandon Allbery
On Thu, May 23, 2013 at 7:11 PM, John King jo...@media.berkeley.edu wrote:

 Having a problem getting the 1.2.1 version installed.  When I search for
 ffmpeg in available ports, the result I see is ffmpeg 1.2.1 and the
 associated Portfile also lists 1.2.1 as the version.

 However, when I run sudo port install ffmpeg +nonfree, I get version
 1.1.2 installed.


At a guess, it's getting installed and then immediately deactivated and
replaced with the older version because of dependencies broken by the new
one. Use upgrade instead of install to make sure those dependencies are
also updated to use the new version; or if that also ends up re-downgrading
you in the rev-upgrade step following the upgrade, then make a note of the
ports which were noted as broken in rev-upgrade and file Trac tickets
against them, as that would indicate they have dependencies they are not
declaring properly.

-- 
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


MacPorts opt folder: Hidden one?

2013-05-23 Thread Eneko Gotzon Ares
Due to difficulties accessing the content of the user accounts I have  
had to reinstall the system, and I took the opportunity to also  
reinstall MacPorts. Now, its opt folder is a hidden one: Is that its  
normal status?


This is not a problem, just a question. Thanks.
--
Eneko Gotzon Ares

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


Re: Problems installing ffmpeg 1.2.1

2013-05-23 Thread Ryan Schmidt
On May 23, 2013, at 18:39, Brandon Allbery wrote:
 On Thu, May 23, 2013 at 7:11 PM, John King wrote:
 Having a problem getting the 1.2.1 version installed.  When I search for 
 ffmpeg in available ports, the result I see is ffmpeg 1.2.1 and the 
 associated Portfile also lists 1.2.1 as the version.
 
 However, when I run sudo port install ffmpeg +nonfree, I get version 1.1.2 
 installed.
 
 At a guess, it's getting installed and then immediately deactivated and 
 replaced with the older version because of dependencies broken by the new one.

I'm not aware of any feature in MacPorts that would cause that to happen—aside 
from explicitly requesting that (e.g. sudo port activate ffmpeg 
@1.1.2_0+gpl2), but John isn't doing that.

 Use upgrade instead of install to make sure those dependencies are also 
 updated to use the new version;

install and upgrade both upgrade dependencies first—unless you explicitly 
request for that not to happen, by using the -n flag, but John isn't doing 
that.

 or if that also ends up re-downgrading you in the rev-upgrade step following 
 the upgrade, then make a note of the ports which were noted as broken in 
 rev-upgrade and file Trac tickets against them, as that would indicate they 
 have dependencies they are not declaring properly.

John, have you run sudo port selfupdate to make sure your ports and MacPorts 
base are up to date? If so, and this is still happening, is it possible you 
have deliberately set up a local portfile repository, which contains this older 
ffmpeg 1.1.2 port? Check your sources.conf file for unusual entries.


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


Re: wine/quicktime installer

2013-05-23 Thread Ryan Schmidt

On May 23, 2013, at 11:29, René J.V. Bertin wrote:

 Am I alone in not being able to install Apple QuickTime under the current 
 wine version (1.5.29)?

I have not tried it. What problems do you experience?

You may be better off asking the wine people directly, since the problem you're 
experiencing is unlikely to be unique to MacPorts. We're just more or less 
packaging the official wine software into MacPorts; we're not patching or 
modifying it in a way that should affect how it works.

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


Re: MacPorts opt folder: Hidden one?

2013-05-23 Thread Adam Mercer
On Thu, May 23, 2013 at 7:37 PM, Eneko Gotzon Ares
enekogot...@gmail.com wrote:
 Due to difficulties accessing the content of the user accounts I have had to
 reinstall the system, and I took the opportunity to also reinstall MacPorts.
 Now, its opt folder is a hidden one: Is that its normal status?

I think this is the default behaviour in Mountain Lion. If you want to
show it in the Finder you should be able to do this by running the
following in a terminal:

$ chflags nohidden /opt

Cheers

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