Re: GCC Version

On 2011-07-22 09:59:35 +0100, Paul C wrote: > http://www.linuxquestions.org/questions/linux-newbie-8/error-in-installing-gcc-4-5-0-a-818033/ > > As detailed in the forum thread in the link the problem I get installing gcc > is not specific to ppc or to MacPorts. It would seem to be a generic probl

Re: Why $ xmlstarlet and not just $ xml as in the man?

Hi, On 2011-04-08 03:10:38 -0500, Ryan Schmidt wrote: > Perhaps "xmlstarlet" used to be called "xml" but was later renamed. No, its official name has always been "xml", but it seems that there are some inconsistences on upstream's side. With MacPorts, the name of the binary is xmlstarlet just be

Re: perl5, perl5.* changes

On 2011-03-01 16:50:53 +, Eric Hall wrote: > I'm quite clear on the need for multiple versions of perl. > For one, I use several perl versions for what I do. IIRC the ghc port > requires perl5.8 for its configuration, newer versions of perl > don't work (this may have changed, though I s

Re: perl5, perl5.* changes

On 2011-02-26 16:47:01 -0500, Daniel J. Luke wrote: > My personal opinion is that we shouldn't bother with the 5.x ports. > We should have moved perl5 from 5.8 to 5.10 to 5.12 and just > rev-bumped the p5 ports when the changes were made ... I completely agree. Like the other ports. > There may b

Re: xordg-libXi -> gtk2, texlive xcommon etc... why ?

On 2010-08-02 20:14:21 +0200, Erwan David wrote: > It keeps the problem of cairo, pango, gtk2, etc... > do they come because of texlive ? There's a dependency texlive -> texlive-bin-extra -> texlive-bin -> poppler -> gtk2 -> pango -> cairo. -- Vincent Lefèvre - Web: 100

Re: xordg-libXi -> gtk2, texlive xcommon etc... why ?

On 2010-08-02 19:30:02 +0200, Erwan David wrote: > upgrading my ports I fnd that the upgrade of xorg-libXi wants to install > whole gtk, a part of texlive, etc.. The reason is xmlto, which has more dependencies than needed: Runtime Dependencies: coreutils, findutils, getopt, libpaper, texlive,

Re: MacPorts 1.8.1 has been released

On 2009-09-29 09:50:00 +1000, Joshua Root wrote: > If you already have MacPorts installed, the preferred method for > updating is to run: > > sudo port selfupdate On Tiger: [...] ===> making install in src/programs ===> making install in src/programs/daemondo mkdir -p build /usr/bin/install -c

Re: how to prevent a package from upgrade

On 2009-07-12 15:52:15 -0500, Ryan Schmidt wrote: > On Jul 12, 2009, at 12:07, S. M. Ibrahim (Lavlu) wrote: > > >in all our production server we are running php-5.2.10 , so as php-5.3 > >is major upgrade, and there is lot's of the change, i don't want to > >upgrade my development systems php versi

Re: Perl error, once and for all

On 2009-03-03 11:49:12 -0800, Bradley Giesbrecht wrote: > Maybe we could add a port "macports-profile" that would be a script > similar to: > /opt/local/share/macports/setupenv.bash Yes, this is a rather standard way of doing such things. > I suppose the file /opt/local/etc/maports_profile.conf

Re: Perl error, once and for all

On 2009-03-03 07:30:18 -0800, Bradley Giesbrecht wrote: > On Mar 1, 2009, at 5:11 PM, Vincent Lefevre wrote: >>> if [ -n "$PERL5LIB" ]; then >>> PERL5LIB="${PERL5LIB}:/opt/local/lib/perl5/vendor_perl" >>> else >>> export PERL5LIB >

Re: Perl error, once and for all

On 2009-03-02 01:18:41 +0100, Vincent Lefevre wrote: > Yes, but MacPorts should not override the user's settings (i.e. it > should test whether PERL5LIB is already set...). One should end up > with something like: > > if [ -n "$PERL5LIB" ]; then > PERL5LIB=

Re: Perl error, once and for all

On 2009-02-28 21:35:59 -0800, Bradley Giesbrecht wrote: > I just want to install something that needs a perl and a p5 module. Do I > really need to RTFM for that? MacPorts can do things for you or tell you what to do. Otherwise, yes, you should RTFM. But this is not specific to perl... > If I wa

Re: Perl error, once and for all

On 2009-03-01 01:00:43 -0800, Scott Haneda wrote: > So, let me get this straight, if MacPorts was to install a .profile with > a certain PERL5LIB env var in it, this issue is solved? Yes, but MacPorts should not override the user's settings (i.e. it should test whether PERL5LIB is already set...)

Re: Perl error, once and for all

On 2009-02-26 10:16:23 -0500, Daniel J. Luke wrote: > On Feb 26, 2009, at 7:28 AM, Scott Haneda wrote: >> Does anyone know how CPAN solves this? > > CPAN installs overwrite the perl-provided module with the newer one > (this is the whole reason why we have a problem). Well, that's a MacPorts spe

Re: Perl error, once and for all

On 2009-02-26 04:28:46 -0800, Scott Haneda wrote: > I think you have to modify the module to "use lib" and supply a path. No need to do that. Just modify PERL5LIB in your environment once and for all (you or MacPorts had to do the same for $PATH, $LIBRARY_PATH, $C_INCLUDE_PATH or whatever, anyw

Re: Perl error, once and for all

On 2009-02-26 05:51:33 +, Eric Hall wrote: > For some (if not all) of the p5-* ports that have recently > sprouted problems, its the man pages that are the issue, not the > modules themselves. I haven't had a chance to look into what > can be done to avoid the man page collisions. The m

Re: Perl error, once and for all

On 2009-02-25 13:21:38 -0800, Scott Haneda wrote: > That feels dirty to me, why not just -f all p5 installs then? No! Any port that needs -f is broken. Note: -f is dangerous. It can trash your system. And it is not compatible with activate/deactivate. -- Vincent Lefèvre - Web:

Re: Universal Binaries

On 2009-01-24 19:25:51 +0100, Harry van der Wolf wrote: > It is something completely different. Most linux, netbsd and freebsd > packages rely on X11. MacOSX has support for x11 but the native > windowing system of MacOSX is aqua. Using the -x11 option means that > you don't build for X11. An incre

Re: Understanding what I am calling the mess that is perl modules

On 2009-01-21 08:04:16 -0500, Kurt Hillig wrote: > If you always use ssh for remote logins then you can test for the > existence of the SSH_CLIENT environment variable. It doesn't exist when > you're logged in locally. You need to be a bit smarter: the SSH_CLIENT environment variable isn't ne

Re: perl5 install errors

On 2009-01-11 21:18:52 -0800, Bradley Giesbrecht wrote: > While struggling to get perl5 reinstalled I noticed a lot of files > referencing /opt/local/bin/perl in /usr/share/bin. What do you mean by "referencing"? Do you have an example? -- Vincent Lefèvre - Web: 100%

Re: Perl 5.8.9 port activation failed

On 2009-01-08 09:51:23 -0700, Frank Schima wrote: > Hi Shawn, > > On Jan 8, 2009, at 9:44 AM, Shawn Protsman wrote: > >> This repeats a number of times. >> >> The MacPorts installation is not outdated so it was not updated >> ---> Activating perl5.8 @5.8.9_1 >> Error: Activating perl5.8 @5.8.9_1 f

Re: unison outdated?

On 2008-12-25 11:48:46 +0100, Joerg van den Hoff wrote: > question: would it be possible to update the maports version, > irrespective of whether the version is declared officially stable -- > it is not at the moment despite b. pierce's recommendation to use > it? Warning! New Unison versions some

Re: Error upgrading xrender on Panther

On 2008-12-15 00:12:25 -0800, Jeremy Huddleston wrote: > The problem lies in some sort of conflict when both /usr/X11R6/lib/ > libX11.dylib and /opt/local/lib/libX11/dylib are linked to by your > executable... so... yeah... my short term solution to offer you is > either > > 1) use all macport

Re: 1.7.0 beta & rc1: libcurl errors

On 2008-12-09 13:45:30 +0100, Rainer Müller wrote: > MacPorts already removes $prefix/bin and $prefix/sbin from PATH on > configure. Does it also handle environment variables such as LIBRARY_PATH, CPATH and C_INCLUDE_PATH? -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 10

Re: mpfr fetch problem

On 2008-11-18 17:09:43 -0600, Altoine Barker wrote: > I can not fetch the mpfr port. It just hangs there attempting to fetch > but not succeeding. I went to the www.mpfr.org website and it appears to > be down FYI, these temporary failures are a known problem. If the admins at Loria (where the ser

Re: Symlinking Emacs.app to the $PATH

On 2008-11-15 10:46:09 -0800, Jordan K. Hubbard wrote: > No, DO use $*, just remember to quote it like you would any other > variable expansion involving filenames. I don't understand this answer. If $* is used, then there is no way to make the difference between cmd a b and cmd "a b" be

Re: Symlinking Emacs.app to the $PATH

On 2008-11-14 10:12:22 -0800, Jordan Hubbard wrote: > JFYI, but to correct a misapprehension here, open does take arguments > (for the launched process) so your original idea would have also worked Here (10.4.11) "open" doesn't take arguments: prunille:~> open -a /Applications/MacPorts/Emacs.a

Re: Symlinking Emacs.app to the $PATH

On 2008-11-14 00:29:03 -0600, Ryan Schmidt wrote: > alias emacs='open -a "/Applications/MacPorts/Emacs.app"' This won't work with options. It's better to write a wrapper script. I use the following one: #!/bin/sh app="Emacs.app/Contents/MacOS/Emacs" #emacs="/Applications/$app" test -x "$emacs" |

Re: mpfr cannot be found

On 2008-11-10 19:52:40 -0800, Barry Olddog wrote: > port is failing to fetch mpfr from both www.mpfr.org and from > svn.macports.org Probably a temporary failure. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated (X)HTML - Blog:

Re: manpath

On 2008-10-28 19:42:48 -0500, Ryan Schmidt wrote: > On Mac OS X 10.4 (and earlier), Apple provides no /private/etc/man.conf. > > On Mac OS X 10.5 (and later?), Apple does provide /private/etc/man.conf > and it does set MANPATH. It's not really MacPorts' place to modify > Apple-provided files so w

Re: manpath

On 2008-10-27 20:01:48 -0500, Ryan Schmidt wrote: > Apple sets the MANPATH to "/usr/share/man:/usr/local/share/man:/usr/ > X11/man" on Leopard for you. So at least Apple doesn't think it should > end with a colon. Apple often does things wrong. Try (while having /opt/local/bin in $PATH): MANPAT

Re: manpath

On 2008-10-27 16:43:58 -0500, Ryan Schmidt wrote: > On Tiger and earlier, MANPATH is empty by default and so having /opt/ > local/bin in PATH is sufficient. However on Leopard and I assume later, > MANPATH is non-empty by default so you need to add /opt/local/share/man > to MANPATH. Even if MAN

Re: manpath

On 2008-10-27 07:29:34 +0100, Rainer Müller wrote: > Shawn Protsman wrote: > > To my surprise I got no entry found when I did a 'man port'. What is > > the recommended method to add port manpages to the path? > > > > Create a '/etc/paths.d/macports'? > > > > Or add to .profile: > > > > export

Re: macports and Xcode

On 2008-10-11 14:50:00 +0200, Emmanuel Hainry wrote: > And those problems would be solved if macports did not rely on third > party tools (gcc, tcl, x11 which have or have had bugs in the past and > apple's versions are not without those bugs). or are out-of-date, leading to problems like: http

Re: perl ports overwriting files, so need -f?

On 2008-09-17 10:00:17 -0400, Daniel J. Luke wrote: > The Makefile.PL that ships with svk clearly states a requirement for > File::Temp 0.17, which is why the p5-file-temp-svkonly port was created > (as 0.17 is newer than what was distributed with perl 5.8.8). I couldn't find any Perl script fr

Re: perl ports overwriting files, so need -f?

On 2008-09-15 12:25:37 -0400, Daniel J. Luke wrote: > Except that you say it as a blanket statement even though you've been > shown at least one case where the port requires the newer version (svk). No, upstream doesn't claim any such dependency on a newer version of a Perl module. You're just s

Re: perl ports overwriting files, so need -f?

On 2008-09-13 00:41:48 +0200, Caspar Florian Ebeling wrote: > Which other ports do this stupid thing, btw? Should they > maybe removed entirely? icon-name-mapping. I sent a mail to nox: I can see in the changelog for icon-name-mapping: r29712 | [EMAIL PROTECTED] | 2007-10-06 22:14:48 +0200 icon

Re: perl ports overwriting files, so need -f?

On 2008-09-12 11:43:06 -0400, Daniel J. Luke wrote: > On Sep 12, 2008, at 8:53 AM, Vincent Lefevre wrote: >> On 2008-09-12 14:45:28 +0200, Caspar Florian Ebeling wrote: >>> On Fri, Sep 12, 2008 at 2:42 PM, Vincent Lefevre >>> <[EMAIL PROTECTED]> wrote: >>

Re: perl ports overwriting files, so need -f?

On 2008-09-12 14:45:28 +0200, Caspar Florian Ebeling wrote: > On Fri, Sep 12, 2008 at 2:42 PM, Vincent Lefevre > <[EMAIL PROTECTED]> wrote: > > On 2008-09-12 13:00:53 +0200, Caspar Florian Ebeling wrote: > >> Do I get it right that one has to force a good part > >

Re: perl ports overwriting files, so need -f?

On 2008-09-12 13:00:53 +0200, Caspar Florian Ebeling wrote: > Do I get it right that one has to force a good part > of the perl ports to make them install? It's better not to install them. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated (X)HTML -

Re: texinfo configuration error

On 2008-08-05 03:28:09 +0200, Normen Mueller wrote: > Alright, I installed lzmautils without any problems. FYI, now it should be installed automatically (in most cases). [*] [*] http://trac.macports.org/ticket/16220 -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% acc

Re: texinfo configuration error

Hi, On 2008-08-05 02:55:41 +0200, Normen Mueller wrote: > Any suggestions what else I could do? Actually I am trying to install > aspell, but this one depends on texinfo. Install lzmautils. I've updated the textinfo port to display an informational message, because MacPorts filters out the re

Re: Is HFS really "scary"?

On 2008-02-06 12:13:32 -0800, Jordan K. Hubbard wrote: > That's probably never going to happen. When you're dealing with grandma > on the phone and she's saying "I can't open my file named ``fluffy!''", > the last thing you need is to go 10 rounds trying to figure out whether > she actually nam

Re: p5-getopt-long and perl5.8 - activation error

On 2008-02-06 12:52:45 -0500, Daniel J. Luke wrote: > On Feb 6, 2008, at 12:45 PM, Vincent Lefevre wrote: >> No-one complained that users have to modify their $PATH. >> With $PERL5LIB, this is the same thing. > > We attempt to automatically modify users' $PATH with the in

Re: p5-getopt-long and perl5.8 - activation error

On 2008-02-06 18:29:21 +0100, N_Ox wrote: > Le 6 févr. 08 à 18:12, Vincent Lefevre a écrit : >> The point is that the end user already needs to change his $PATH. >> So, this wouldn't be a big difference. > > I don't see any kind of link with $PATH here. No-one compl

Re: p5-getopt-long and perl5.8 - activation error

On 2008-02-06 10:40:30 -0500, Daniel J. Luke wrote: > On Feb 5, 2008, at 9:01 PM, Vincent Lefevre wrote: >> On 2008-02-05 10:13:03 -0500, Daniel J. Luke wrote: >>> svk requires newer versions of CORE modules than those that ship with >>> perl5.8 >> >&

Re: Can the port command take advantage of multiple cores?

On 2008-02-06 00:44:51 -0500, Yves de Champlain wrote: > It was a general warning rather than a bug report ... 8 cores and > happens during destroot. I did not keep the output but it had something > to do with "waiting for unfinished jobs" I don't think this is a bug. Doesn't this mean that "m

Re: p5-getopt-long and perl5.8 - activation error

On 2008-02-05 10:13:03 -0500, Daniel J. Luke wrote: > svk requires newer versions of CORE modules than those that ship with > perl5.8 This is strange because I don't see dependencies on particular versions in svk. > The perl community doesn't consider newer released versions of CORE > modules

Re: p5-getopt-long and perl5.8 - activation error

On 2008-02-05 09:35:38 -0500, Daniel J. Luke wrote: > The only reason why that dependency should be specified is if the port > needs the newer version of that module than is provided by perl core. If > the dependency really isn't needed, perhaps you should open a ticket with > the port maintain

Re: p5-getopt-long and perl5.8 - activation error

On 2008-02-04 22:51:00 -0500, Michael Franz wrote: > Ryan, > Does that mean that I should expect the dependencies to have issues? Or, > should I always pass in -f for my installs? > > I re-ran my install command (it was not apahe-ant, it was icedtea), 5 more > packages gave me the same issue. I

Re: Can the port command take advantage of multiple cores?

On 2008-02-02 17:45:35 -0600, Ryan Schmidt wrote: > Not exactly. Not all software supports parallel building. Each port must > be tested to ensure that it works. As ports are tested, > "use_parallel_build yes" is added to the portfile. Then MacPorts will > build those ports using -j$jobs (wher

Re: plans for 64bit support (Joshua Root)

On 2007-12-20 22:22:51 +0100, Markus Weissmann wrote: > If I remember correctly, all powerpc instructions have a length of > 32 bit. That's not different from the ARM. > Given that you need some bits for the opcode, a mere 16 bit remain to > stuff a constant value to it (for the load high/add i

Re: plans for 64bit support (Joshua Root)

On 2007-12-20 17:59:25 +1100, Joshua Root wrote: > [1] > [2] I don't understand why they say that 5 instructions are needed for constants in 64-bit binaries. Can't the PowerPC load the constant

Re: ion3 window manager no longer available

On 2007-12-17 19:04:17 +0100, Joerg van den Hoff wrote: > On Mon, Dec 17, 2007 at 12:22:20PM -0500, William Davis wrote: > > Because using the name ion3 in any form would be a license violation. > > ok, got it. but the debian solution (some other arbitrary name) would > work. so why can't you ju

Re: ion3 window manager no longer available

On 2007-12-17 13:35:00 +0100, Joerg van den Hoff wrote: > since `ion3' actually is a very fine window manager for a > certain type of work, may I ask you to check whether it > would'nt be sufficient to modify the package info line > accordingly with some "wildcard" disclaimer of the k

Re: Ion3 license and possible removal

On 2007-12-14 15:26:12 +0100, Markus Weissmann wrote: > thanks for bringing this up here: Mr. Valkonen's license is absolutely > unbearable. > As an alternative: Perhaps you can bring the port back to the last sane > licensed version - don't know if this is useful and/or possible. > Either that

Re: using libs installed with macports to build a tarball

On 2007-11-23 02:35:47 +0100, Mailing lists wrote: >>> But I don't know where to set it. 'LIBRARY_PATH=$LIBRARY_PATH:/opt/ >>> local/lib ./configure'gives me the same error, and LIBRARY_PATH >>> is not set at all anyway (no /usr/local/lib or /usr/lib) This isn't a correct solution, because

Re: using libs installed with macports to build a tarball

On 2007-11-22 23:46:07 +0100, Mailing lists wrote: > I'm trying to build qjackctl (a gui for Jack audio connection kit) from > its source tarball. qjackctl uses qt4, so I installed qt4-mac from > macports (successfully) but the configure script of qjackctl can't find > it. Do I have to set up an

Re: Speed up build phase with "make -j"

On 2007-10-31 12:26:44 +0100, Markus Weissmann wrote: > On 31.10.2007, at 05:13, Vincent Lefevre wrote: >> I disagree. Port maintainers should test their port to see if they >> work with "make -j". > > Well, you cannot reliably test this. If you're lucky it migh

Re: Speed up build phase with "make -j"

On 2007-10-30 16:20:18 +0100, Markus Weissmann wrote: > On 30.10.2007, at 13:52, Vincent Lefevre wrote: >> The bug could also be reported upstream, so that a ".NOTPARALLEL:" >> is added to the Makefile. > > Well, this simply is not going to work -- this has to be an

Re: Speed up build phase with "make -j"

On 2007-10-30 12:43:52 +0100, Anders F Björklund wrote: > Weissmann Markus: >> Yes, but I meant this to be a per-Portfile choice so a maintainer can mark >> his/her port as being able to build in parallel. Doing this with the >> sledgehammer for all ports that use 'make' might be a bit too much.

Re: Speed up build phase with "make -j"

On 2007-10-28 16:11:48 +0100, Anders F Björklund wrote: > js wrote: >> What causes the build erorr? is it for bad Makefile or problem of "-j" >> option itself? > > Bad makefiles, usually missing dependencies. And this may be difficult to fix. For instance: http://dev.mutt.org/trac/ticket/2538

Re: gnucash 2.2.1 problems (and solutions)

On 2007-10-22 21:48:17 -0400, David Reiser wrote: > How are the help files handled? gnucash uses yelp, which needs mozilla, > seamonkey, or firefox to display the help. That could be where the firefox > dependency arises. Couldn't yelp use a generic command to open files in a browser, so that th

Re: gnucash 2.2.1 problems (and solutions)

On 2007-10-23 08:13:30 +0200, Marc André Selig wrote: > On 10/23/07, Vincent Lefevre <[EMAIL PROTECTED]> wrote: > > prunille:~> port installed gnucash > > The following ports are currently installed: > > gnucash @2.0.5_2+guile16 > > gnucash @2.2.1_0+guile1

Re: gnucash 2.2.1 problems (and solutions)

On 2007-10-22 18:29:47 -0400, William Davis wrote: > 6. of course also port deactivate -f slib-guile and then install > slib-guile16 . Sorry, should have said this explicitly. This wasn't my question. Of course, slib-guile16 is active (and all the installed slib-guile ports is unactive). What I

Re: gnucash 2.2.1 problems (and solutions)

Another thing I don't understand is that installing gnucash requires firefox-x11, whose build fails. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arenaire proje

Re: gnucash 2.2.1 problems (and solutions)

On 2007-10-22 22:44:29 +0200, Marc André Selig wrote: > On 10/22/07, Vincent Lefevre <[EMAIL PROTECTED]> wrote: > > A problem is that gnucash still depends on guile, indirectly: > > No, it does not, at least not with the default variant +guile16. This is what I use. >

Re: gnucash 2.2.1 problems (and solutions)

On 2007-10-22 14:32:55 -0400, William Davis wrote: > 5. THEREFORE make sure you have installed guile16. (you may need to > deactivate guile 1.8.1 in order to activate this) A problem is that gnucash still depends on guile, indirectly: prunille:~> sudo port -v uninstall guile ---> Unable to unin

Re: gnucash 2.2.1 problems (and solutions)

On 2007-10-22 10:25:21 -0700, Kastus Shchuka wrote: > First bump on the road was goffice03. I remembered reading a post in this > list about problems with building gnucash against the latest goffice and > introduction of a new port goffice03 as a result. I had [EMAIL PROTECTED] > already install

Re: Gimp Error

On 2007-10-21 00:36:27 -0400, Daniel J. Luke wrote: > (unless we want to patch all existing software that depends on updates to > perl-distributed modules being installed in this way, or change the search > ordering for macports-provided perl we don't really have another good > option). The use

Re: Gimp Error

On 2007-10-19 21:14:45 -0400, Daniel J. Luke wrote: > no. The file in question is from the p5-pathtools port, it supplies a newer > (but still compatible) version of a library that is included with the > normal perl distribution. Due to some peculiarities with how perl searches > for libraries,

Re: Gimp Error

On 2007-10-19 14:34:11 -0500, Lenore Horner wrote: > Sure, but is that now going to mess up his perl5.8 port? Yes, if you try to upgrade or deactivate and reactivate the perl5.8 port. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated (X)HTML - Blog:

Re: texinfo doesn't function

On 2007-10-11 19:22:48 -0500, Nehemiah Dacres wrote: > the problem with your solution is that macports utilities should still > function dispite the existance of a native equivilant. If I installed ls > from mac ports, it should still work You need to use the correct syntax, which is: "info coreut

Re: texinfo doesnt function

On 2007-10-11 11:23:39 -0400, Daniel J. Luke wrote: > What really happens is that activate/deactivate create the links from the > place where the software is actually installed by macports to ${prefix}. > activate/deactivate didn't exist until image mode was invented. > > Since direct mode instal

Re: Trying to update the slocate database

On 2007-10-11 06:16:13 -0500, Ryan Schmidt wrote: > But now I get: > > slocate: option requires an argument -- c However, though one gets this message, slocate rebuilds the database. > But the manpage does not show that -c requires or even supports an > argument: > >-c Parse '/opt/l

Re: texinfo doesnt function

On 2007-10-10 16:48:40 -0400, Daniel J. Luke wrote: > On Oct 10, 2007, at 3:39 PM, Vincent Lefevre wrote: >> On 2007-10-10 11:38:51 -0400, Daniel J. Luke wrote: >>> post-activate and post-deactivate don't run on macports installs with >>> 'direct' m

Re: texinfo doesnt function

On 2007-10-10 14:42:57 -0500, Ryan Schmidt wrote: > FYI, "info ls" works for me under Mac OS X. It appears to show the ls > manpage. I do not have coreutils or texinfo installed. But this is just a fallback, that won't necessarily give what the user really wants to. The man page should be viewed

Re: delta.macosforge.org and HELO

On 2007-10-10 21:30:07 +0200, Vincent Lefevre wrote: > If someone knows how to configure postfix to select a smarthost for > some domains only, this could be a solution (/etc/postfix/transport > has some documentation, I'll have to try...). Problem solved. Sorry for the duplicates

Re: texinfo doesnt function

On 2007-10-09 14:05:08 -0500, Nehemiah Dacres wrote: > having installed gnu texinfo from macports > upon using "info ls" You need to type "info coreutils" ("info ls" doesn't work either under Debian, so I suppose that this form is not supported). > it responds with > dir: no such file I don't ha

Re: texinfo doesnt function

On 2007-10-10 11:38:51 -0400, Daniel J. Luke wrote: > On Oct 10, 2007, at 11:13 AM, Vincent Lefevre wrote: >> but IMHO, this is incorrect: to be correct, the dir file should be >> updated by post-activate (to install) and post-deactivate (with the >> --delete option of instal

delta.macosforge.org and HELO (was: texinfo doesnt function)

> $ host prunille.vinc17.org > Host prunille.vinc17.org not found: 3(NXDOMAIN) As I said, this is a machine on a local network, not visible from the Internet. But the host can be resolved from the local network. > Many (most?) mailservers won't accept mail from a host who supplies > a HELO hostna

Re: texinfo doesnt function

On 2007-10-09 14:05:08 -0500, Nehemiah Dacres wrote: > having installed gnu texinfo from macports > upon using "info ls" You need to type "info coreutils" ("info ls" doesn't work either under Debian, so I suppose that this form is not supported). > it responds with > dir: no such file I

Re: texinfo port issue

On 2007-09-23 00:04:35 -0500, Nehemiah Dacres wrote: > whenever i invoke texinfo, i get this error > > info: dir: No such file or directory I don't have this problem (some info directories have a "dir" file, but not all, so I assume that it is not necessary). You should give more information. --

Re: Installing gnuplot fails

On 2007-09-15 15:37:28 +0200, Simon Ruderich wrote: > This bug was fixed some hours ago. Use "sudo port sync" to get the > fix and then try it again. BTW, upstream said the real bug was in autoconf (but the latest version wasn't used). So, other ports could suffer from the same problem. -- Vince

Re: texinfo building error

On 2007-09-14 19:25:13 +0200, Vincent Lefevre wrote: > The "else" is taken when you don't have the coreutils mkdir. And the > problem is that the install-sh doesn't have the exec bit set (this is > not a problem in general, but here it is, and upstream isn't awa

Re: texinfo building error

On 2007-09-14 16:09:20 +, Glenn Jones wrote: > Here is the outup for the port install -v texinfo I also needed the configure output. I have: checking for a thread-safe mkdir -p... /opt/local/bin/gmkdir -p I think you get something else, in which case a solution to solve the problem is to ins

Re: texinfo building error

On 2007-09-14 17:31:18 +0200, Vincent Lefevre wrote: > I do not have such a problem. Could you try with the -v option > and send me the output? And also, after you get the failure: grep 'install_sh ' `port dir texinfo`/work/texinfo-4.11/Makefile Here I have: install_sh = $(SH

Re: texinfo building error

On 2007-09-14 14:53:27 +, Glenn Jones wrote: > ---> Building texinfo with target all > Error: Target org.macports.build returned: shell command " cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_texinfo/work/texinfo-4.11" > && make

Re: Remove all ports

On 2007-09-13 21:16:16 -0500, Bill Hernandez wrote: > I don't know if you've installed anything other than MacPorts in > /opt but if you have not, you could probably delete everything in > the /opt directory. ports also install things outside /opt, e.g. symlinks in /Library/LaunchDaemons. -- Vin

Re: MacPorts 1.5.2 now available

On 2007-08-31 18:05:21 -0500, Ryan Schmidt wrote: > On Aug 31, 2007, at 03:36, Vincent Lefevre wrote: >> Then that's a user-side problem. The best fix is to remove/replace this >> incredibly old version of readline. > > Of course. But if MacPorts *seems* to build

Re: MacPorts 1.5.2 now available

On 2007-08-29 20:28:30 -0500, Ryan Schmidt wrote: > But we always want users to compile MacPorts base using the gcc > provided with Apple Xcode. We don't want people attempting to use > any other version of gcc. Does MacPorts ensures that Xcode gcc is used? >> Couldn't MacPorts be made compatible

Re: MacPorts 1.5.2 now available

On 2007-08-28 22:58:16 +0200, N_Ox wrote: > > Le 22 août 07 à 17:25, Vincent Lefevre a écrit : > >> On 2007-08-21 22:15:08 -0400, Jay Sachs wrote: >>> What about: >>> >>> gcc -nostdinc \ >>> -isystem /usr/lib/gcc/i686-apple-da

Re: MacPorts 1.5.2 now available

On 2007-08-22 08:42:20 -0400, Jason Stelzer wrote: > Its not that /usr/local is special, its that it is part of the > standard runtime/compile time search path by default. You should be > able to override its search vial -L at compile time and > DYLD_LIBRARY_PATH at runtime. Yes, for libraries *on

Re: MacPorts 1.5.2 now available

On 2007-08-21 22:15:08 -0400, Jay Sachs wrote: > What about: > > gcc -nostdinc \ > -isystem /usr/lib/gcc/i686-apple-darwin8/4.0.1/include \ > -isystem /usr/include \ > -isystem /System/Library/Frameworks \ > -isystem /Library/Frameworks > > ? It'd be nice not to hardcode this -- it

Re: MacPorts 1.5.2 now available

On 2007-08-21 16:33:11 -0500, Ryan Schmidt wrote: [...] >> ld: Undefined symbols: >> _rl_completion_matches >> _rl_filename_completion_function >> _rl_username_completion_function >> /usr/bin/libtool: internal link edit command failed >> make[2]: *** [Pextlib.dylib] Error 1 >> make[1]: *** [all] Er

Re: mpfr patches first fail then are sloowwwww!

On 2007-07-22 13:13:47 -1000, Tabitha McNerney wrote: > Has anyone else noticed how slow downloading the patches for the > mpfrMacPort is? I need mpfr as a prerequisite for the gcc41 and > gcc42 ports. At first my attempt to install mpfr failed like this: > > # port install mpfr > ---> Fetchin

Re: heimdal/coreutils issue: how to resolve?

On 2007-05-21 00:14:21 -0700, paul beard wrote: > That sounds reasonable, but it looks like my problem is resolved > with some manual cleanup. I removed /opt/local/bin/su and did a > forced reinstall of heimdal. > > white:~ root# port provides /opt/local/bin/su > /opt/local/bin/su is provided by: h

Re: heimdal/coreutils issue: how to resolve?

On 2007-05-20 23:47:13 -0400, Chris Pickel wrote: > On 20 May, 2007, at 23:06, paul beard wrote: >> How can we get aound this contention over /opt/local/bin/su, since both >> heimdal and coreutils claim it as theirs? > > Doesn't/shouldn't coreutils install /opt/local/bin/gsu and not > /opt/local/

Problems with python (was: /bin/date and coreutils)

On 2007-05-10 23:56:05 +0200, Vincent Lefevre wrote: > I've seen many problems after Python upgrades under Debian (e.g. > things that no longer work, probably because incompatibilities > between versions)... Well, not only on Debian. With MacPorts too: the latest python up

Re: scripting environments (was: /bin/date and coreutils)

On 2007-05-11 20:25:24 +0200, Elias Pipping wrote: > Indeed, I'm missing the point. So... make a script that can live with the > bourne shell invoke /bin/sh then The script must be compatible with both Bourne and POSIX shells (because under Solaris, /bin/sh is a Bourne shell). > and if it can't,

  1   2   >