Re: openssh loads sshd?

2010-07-22 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/21/10 16:39 , Kevin Reid wrote: > I'd like to see all special per-port messages be retrievable *after* > install, and perhaps batched at the end of all installs. As it is, if I'm +1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Com

Re: openssh loads sshd?

2010-07-22 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/21/10 00:59 , Ryan Schmidt wrote: > This message is not unique to this port; all ports that have > MacPorts-generated startupitems get this output displayed. Do you have a > suggestion for how the message could be revised in such a way that woul

Re: Error setting locale in python

2010-07-22 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/22/10 16:22 , Harald Hanche-Olsen wrote: > I get the same result if I clear the environment using env - ... > All the variables whose values are listed as "C" were actually not > set; but setlocale reports them as "C". Not that it matters: Setting

Re: Next gcc46 Problem

2010-07-22 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/22/10 01:55 , Ryan Schmidt wrote: > On Jul 22, 2010, at 00:38, Johannes Ruscheinski wrote: >> On Tue, Jul 20, 2010 at 3:14 PM, Ryan Schmidt wrote: >>> On Jul 20, 2010, at 12:58, Johannes Ruscheinski wrote: gcc-mp-4.6 -std=gnu++0x AutoTest.cc

Re: openssh loads sshd?

2010-07-22 Thread Scott Webster
Perhaps at least the port description could make it clear that it includes a server. I guess in theory I could file a ticket or email the maintainer :) On Wed, Jul 21, 2010 at 5:57 PM, Dan Ports wrote: > On Wed, Jul 21, 2010 at 04:40:31PM -0400, Daniel J. Luke wrote: >> Yep. Maybe we should re-w

Re: Error setting locale in python

2010-07-22 Thread Harald Hanche-Olsen
+ Bryan Blackburn : > Do you have anything else in your env that could be affecting the locale > stuff? If I use those LANG/LC settings you've listed, the MacPorts python > seems okay with it: > > % env LANG= LC_COLLATE="C" LC_CTYPE="en_US.UTF-8" LC_MESSAGES="C" > LC_MONETARY="C" LC_NUMERIC="C"

Re: Error setting locale in python

2010-07-22 Thread Bryan Blackburn
On Thu, Jul 22, 2010 at 08:32:06PM +0200, Harald Hanche-Olsen said: > python2.5 and python2.6 both don't like my locale setting: > > ; python2.6 > Python 2.6.5 (r265:79063, Jul 16 2010, 21:35:10) > [GCC 4.0.1 (Apple Inc. build 5493)] on darwin > Type "help", "copyright", "credits" or "lic

Error setting locale in python

2010-07-22 Thread Harald Hanche-Olsen
python2.5 and python2.6 both don't like my locale setting: ; python2.6 Python 2.6.5 (r265:79063, Jul 16 2010, 21:35:10) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import locale >>> locale.setlocale(locale.LC

Re: how to configure macports Lyx

2010-07-22 Thread Dan Ports
On Thu, Jul 22, 2010 at 09:54:58AM -0600, Srinath Vadlamani wrote: > Any other information on how to make sure Lyx is conifgured to > use /opt/local/share/texmf-texlive-dist/tex/latex? Are you still having problems? If so, can you describe them? I am not really familiar with LyX myself, but woul

xorg-server, launchd, and DISPLAY

2010-07-22 Thread Michael Fitzgerald
Hi all, I'm in the midst of setting up a new 10.6 mac, and have elected to install the MacPorts xorg-server. I am having trouble with the setting of the DISPLAY variable in non-X11 applications (e.g. Terminal, konsole). I have disabled the setting of DISPLAY by Apple's X11 with the following

Re: how to configure macports Lyx

2010-07-22 Thread Srinath Vadlamani
Any other information on how to make sure Lyx is conifgured to use /opt/local/share/texmf-texlive-dist/tex/latex? <>Srinath On Fri, Jul 16, 2010 at 12:23 PM, Srinath Vadlamani wrote: > Very helpful. > Thanks. > > > On Fri, Jul 16, 2010 at 12:11 PM, Dan Ports wrote: > >> >> Will respond to your

Re: cputype problem on snow leopard

2010-07-22 Thread Ryan Schmidt
On Jul 22, 2010, at 07:09, Anne Poupon wrote: > I still can't understand why lipo was not working... I took it again from the > same DVD and now it's working. Strange... My only guess is that some installer of some software out on the Internet, that you downloaded and installed, contained an a

Re: Trying to update a Portfile

2010-07-22 Thread Ryan Schmidt
On Jul 22, 2010, at 06:51, Harry van der Wolf wrote: > This simplifies the Portfile. Building is succesful but.. the install_name is > still not in the libraries. The setting from the cmake portgroup that AFAIK should have fixed this is: -DCMAKE_INSTALL_NAME_DIR=${prefix}/lib If that doesn't d

Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
Thanks ! It's working now. I have now the right answer from lipo, and I was able to install gettext (I suppose the others will install as well). I still can't understand why lipo was not working... I took it again from the same DVD and now it's working. Strange... Anyway, thanks very much for you

Re: Trying to update a Portfile

2010-07-22 Thread Harry van der Wolf
2010/7/22 Ryan Schmidt > On Jul 22, 2010, at 04:20, Harry van der Wolf wrote: > > > The resulted build, both hugin itself as the hugin dylibs, don't have the > correct path when questioned with the "otool -L ". They do for > the "external" libraries they are linked to like libjpeg etc. > > Both t

Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
Ok, I'll try that ! On Thu, Jul 22, 2010 at 12:06 PM, Ryan Schmidt wrote: > On Jul 22, 2010, at 04:42, Vincent Habchi wrote: > > > Le 22 juil. 2010 à 11:36, Anne Poupon a écrit : > > > >> 3.06 GHz intel core 2 duo ... > > > > Somehow, this is all wrong. You should have a two-way Intel universal >

Re: cputype problem on snow leopard

2010-07-22 Thread Ryan Schmidt
On Jul 22, 2010, at 04:42, Vincent Habchi wrote: > Le 22 juil. 2010 à 11:36, Anne Poupon a écrit : > >> 3.06 GHz intel core 2 duo ... > > Somehow, this is all wrong. You should have a two-way Intel universal lipo: > > PM: /usr/bin/lipo -info /usr/bin/lipo > Architectures in the fat file: /usr/b

Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Le 22 juil. 2010 à 11:53, Anne Poupon a écrit : > sh-3.2# uname -a > Darwin iMac-de-Pauline-Gloaguen.local 10.4.0 Darwin Kernel Version 10.4.0: > Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386 i386 Well, beats me (comme disent les Anglais) ;) Somehow your binaries are messed up

Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
sh-3.2# uname -a Darwin iMac-de-Pauline-Gloaguen.local 10.4.0 Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386 i386 On Thu, Jul 22, 2010 at 11:42 AM, Vincent Habchi wrote: > Le 22 juil. 2010 à 11:36, Anne Poupon a écrit : > > > 3.06 GHz intel core 2 du

Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Le 22 juil. 2010 à 11:36, Anne Poupon a écrit : > 3.06 GHz intel core 2 duo ... Somehow, this is all wrong. You should have a two-way Intel universal lipo: PM: /usr/bin/lipo -info /usr/bin/lipo Architectures in the fat file: /usr/bin/lipo are: x86_64 i386 --- and Snow Leopard does not work wi

Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
3.06 GHz intel core 2 duo ... On Thu, Jul 22, 2010 at 11:32 AM, Vincent Habchi wrote: > Re- > > > sh-3.2# /usr/bin/lipo -info /usr/bin/lipo > > Non-fat file: /usr/bin/lipo is architecture: ppc > > !!! > On what model are you working? > > Vincent > ___

Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Re- > sh-3.2# /usr/bin/lipo -info /usr/bin/lipo > Non-fat file: /usr/bin/lipo is architecture: ppc !!! On what model are you working? Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listin

Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
> strings /usr/bin/lipo | grep x86_64 nothing... > This confirms your lipo command is broken. Somehow, an older version of lipo than the one that shipped with Snow Leopard has been copied to /usr/bin/lipo. Replace it with a copy that came from Snow Leopard, either from your backups, or from > t

Re: Trying to update a Portfile

2010-07-22 Thread Ryan Schmidt
On Jul 22, 2010, at 04:20, Harry van der Wolf wrote: > The resulted build, both hugin itself as the hugin dylibs, don't have the > correct path when questioned with the "otool -L ". They do for > the "external" libraries they are linked to like libjpeg etc. > Both the binary and it's own librar

Re: Trying to update a Portfile

2010-07-22 Thread Harry van der Wolf
2010/7/22 Ryan Schmidt > On Jul 21, 2010, at 08:35, Harry van der Wolf wrote: > > > Thanks for your reply. I was already typing a mail to mention that I had > found it. I "grepped" for other Portfiles having "sourceforge:". > > > > I came to: > > master_sitessourceforge:hugin > > Sinc

Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Le 22 juil. 2010 à 11:16, Ryan Schmidt a écrit : > On Jul 22, 2010, at 03:25, Anne Poupon wrote: > >> sh-3.2# /usr/bin/lipo -info /usr/lib/libz.dylib >> Architectures in the fat file: /usr/lib/libz.dylib are: (cputype (16777223) >> cpusubtype (3)) i386 ppc7400 > > This confirms your lipo comma

Re: cputype problem on snow leopard

2010-07-22 Thread Ryan Schmidt
On Jul 22, 2010, at 03:25, Anne Poupon wrote: > sh-3.2# /usr/bin/lipo -info /usr/lib/libz.dylib > Architectures in the fat file: /usr/lib/libz.dylib are: (cputype (16777223) > cpusubtype (3)) i386 ppc7400 This confirms your lipo command is broken. Somehow, an older version of lipo than the one

Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Salut ! ;) > One last thing: it was not a migration, the computer came whith snow > leopard... What's the output of: strings /usr/bin/lipo | grep x86_64 Bonne journée ! Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http:

Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
Dear all, As advised, I have removed the psql in /usr/local, unfortunately this didn't change the outcome ! I have also tried to install the packages on which postgres depends one after the other. Some of them did go through, but some don't ! For example when trying to install gettext, I have abo