Re: eclipse install (broken ports tree)

2009-08-06 Thread Coert Waagmeester
On Wed, 2009-08-05 at 14:50 -0800, Mel Flynn wrote: On Wednesday 05 August 2009 13:53:22 Coert Waagmeester wrote: I tried it via the ports, but this error keeps popping up: Missing pkg-descr for patch-2.5.9. I believe you have a defective ports tree. You should have the following file:

Re: eclipse install (SOLVED broken ports tree)

2009-08-06 Thread Coert Waagmeester
On Thu, 2009-08-06 at 09:08 +0200, Coert Waagmeester wrote: On Wed, 2009-08-05 at 14:50 -0800, Mel Flynn wrote: On Wednesday 05 August 2009 13:53:22 Coert Waagmeester wrote: I tried it via the ports, but this error keeps popping up: Missing pkg-descr for patch-2.5.9. I believe

Re: eclipse install (SOLVED broken ports tree)

2009-08-06 Thread Mel Flynn
On Thursday 06 August 2009 00:07:33 Coert Waagmeester wrote: I have PKGDIR variable exported. Ack, yeah. Should've thought of that. It's a badly chosen variable name for pkg_add. You could make an alias though: alias pkg_keep='env PKGDIR=/path/to/whatever pkg_add -K' -- Mel

Re: broken ports

2009-02-09 Thread Frank Shute
On Mon, Feb 09, 2009 at 07:30:44AM +, David Collins wrote: What does: $ ldconfig -r | grep gcc_s give you? viper:~$ ldconfig -r | grep gcc_s 247:-lgcc_s.1 = /usr/local/lib/gcc-4.2.5/libgcc_s.so.1 On my FreeBSD 7.1-RELEASE-p2 amd64: $ cc -v Using built-in specs.

Re: broken ports

2009-02-09 Thread David Collins
I think the problem is that somebody has installed a compiler out of ports on your machine it's associated libraries. See what cc -v says. My cc is exactly the same as yours viper:~$ cc -v Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler

Re: broken ports

2009-02-09 Thread Frank Shute
On Mon, Feb 09, 2009 at 09:08:28AM +, David Collins wrote: I think the problem is that somebody has installed a compiler out of ports on your machine it's associated libraries. See what cc -v says. My cc is exactly the same as yours viper:~$ cc -v Using built-in specs. Target:

Re: broken ports

2009-02-09 Thread David Collins
Then you should be able to build rtorrent. Then what I'd do is deinstall gcc42: # pkg_deinstall -f gcc-4.2.5_20080702 Comment out the CC line in /etc/make.conf run ldconfig: # /etc/rc.d/ldconfig start and hopefully your system is then back to normal. I tried all this and rtorrent

Re: broken ports

2009-02-09 Thread Frank Shute
On Mon, Feb 09, 2009 at 07:52:58PM +, David Collins wrote: Then you should be able to build rtorrent. Then what I'd do is deinstall gcc42: # pkg_deinstall -f gcc-4.2.5_20080702 Comment out the CC line in /etc/make.conf run ldconfig: # /etc/rc.d/ldconfig start and

Re: broken ports

2009-02-09 Thread David Collins
Thank you for your input. I feel like this problem is too far over my head to be able to give adequate enough debugging. I am not against any alternative methods of resolving this (even removing and reinstalling ports) rather than fixing, I just don't want to have to jump into sysinstall or

Re: broken ports

2009-02-08 Thread David Collins
How did you uninstall that port after which everything fails at the configure stage? Which port was it? It was rtorrent that I uninstalled, I used make deinstall Check a couple of things: $ which c++ and: $ locate gcc_s | grep lib viper:~$ which c++ /usr/bin/c++ also viper:~$ which

Re: broken ports

2009-02-08 Thread Frank Shute
On Sun, Feb 08, 2009 at 04:16:53PM +, David Collins wrote: How did you uninstall that port after which everything fails at the configure stage? Which port was it? It was rtorrent that I uninstalled, I used make deinstall Check a couple of things: $ which c++ and: $

Re: broken ports

2009-02-08 Thread David Collins
I'm wondering whether your use of sudo is mucking things up and it's a permissions problem. i.e: it's running make OK but freaking out when it tries to invoke the compiler in the config stuff. I always build my ports using portupgrade as root. Maybe you could try logging in as root then

Re: broken ports

2009-02-08 Thread Frank Shute
On Sun, Feb 08, 2009 at 10:24:52PM +, David Collins wrote: I'm wondering whether your use of sudo is mucking things up and it's a permissions problem. i.e: it's running make OK but freaking out when it tries to invoke the compiler in the config stuff. I always build my ports using

Re: broken ports

2009-02-08 Thread David Collins
What does: $ ldconfig -r | grep gcc_s give you? viper:~$ ldconfig -r | grep gcc_s 247:-lgcc_s.1 = /usr/local/lib/gcc-4.2.5/libgcc_s.so.1 ___ freebsd-questions@freebsd.org mailing list

Re: broken ports

2009-02-06 Thread Frank Shute
On Thu, Feb 05, 2009 at 10:18:52AM +, David Collins wrote: Sorry, forgot about that. Looking at it again I am not sure this is a ports thing, and more of an issue with the compiling tool chain. viper:/usr/ports/net-p2p/rtorrent$ sudo make === Vulnerability check disabled, database

broken ports

2009-02-05 Thread David Collins
Hi, I am not sure if this is better here or in the ports list, but I thought that since it is something that I have done because I don't know what I am doing here would be better A while ago I installed ports and everything was working fine. Recently I thought one of my ports was causing my

Re: broken ports

2009-02-05 Thread Dominic Fandrey
David Collins wrote: Hi, I am not sure if this is better here or in the ports list, but I thought that since it is something that I have done because I don't know what I am doing here would be better A while ago I installed ports and everything was working fine. Recently I thought one of

Re: broken ports

2009-02-05 Thread David Collins
Sorry, forgot about that. Looking at it again I am not sure this is a ports thing, and more of an issue with the compiling tool chain. viper:/usr/ports/net-p2p/rtorrent$ sudo make === Vulnerability check disabled, database not found === Found saved configuration for rtorrent-0.8.2_1 =

Re: broken ports

2005-10-06 Thread Toomas Aas
Reinhard Weismann wrote: does anybody know where to report broken ports, or, where to get information if/why a port currently is broken. From your description I am not at all sure that the port is broken in this case. But since you asked... If you are sure that the port really is broken

Re: broken ports

2005-10-06 Thread Reinhard Weismann
On Thu, 06 Oct 2005 15:12:40 +0300 Toomas Aas [EMAIL PROTECTED] wrote: Reinhard Weismann wrote: does anybody know where to report broken ports, or, where to get information if/why a port currently is broken. From your description I am not at all sure that the port is broken in this case

broken ports

2005-10-04 Thread Reinhard Weismann
does anybody know where to report broken ports, or, where to get information if/why a port currently is broken. in this case on my 5.4-RELEASE-p6 (i386) installations, the port mail/p5-Mail-SpamAssassin (p5-Mail-SpamAssassin-3.1.0) does not compile, i.e. i get [..] Segmentation fault (core

hacking broken ports

2003-11-02 Thread William O'Higgins
I was trying to build mplayer tonight, and I ran into a problem with net/liveMedia. The port that I've got calls for the build done on 10.24.2003. This file was unavailable on *any* of the listed mirrors, with the closest match being one built on 10.30.2003. I got around this problem by putting

Re: hacking broken ports

2003-11-02 Thread Simon Barner
I was trying to build mplayer tonight, and I ran into a problem with net/liveMedia. The port that I've got calls for the build done on 10.24.2003. This file was unavailable on *any* of the listed mirrors, with the closest match being one built on 10.30.2003. I got around this problem by

Re: hacking broken ports

2003-11-02 Thread andi payn
The rest of your question has been answered, but: On Sat, 2003-11-01 at 23:00, William O'Higgins wrote: I found that there was only on reference to the filename in the Makefile, so I changed it, and then I generated an MD5 on the file that I had and put it into distfile. Instead of manually

Announce Broken Ports

2003-07-25 Thread Leonardo Lazarte
As seen in several messages to this and other lists, the PORTS mecanism has been broken. I have read about some patches and possible solutions, but I could not find an easy way to overcome the problem. Shouldn't it be announced clearly, on the FreeBSD site, that there is a problem with PORTS,

Re: Announce Broken Ports

2003-07-25 Thread Joshua Oreman
On Fri, Jul 25, 2003 at 02:00:07PM -0300 or thereabouts, Leonardo Lazarte wrote: As seen in several messages to this and other lists, the PORTS mecanism has been broken. It only seems so because of the dependency on pkg_info -O. I have read about some patches and possible solutions, but I

RE: Announce Broken Ports

2003-07-25 Thread Joshua Lokken
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Leonardo Lazarte Sent: Friday, July 25, 2003 10:00 AM To: freebsd-questions Subject: Announce Broken Ports As seen in several messages to this and other lists, the PORTS mecanism has been broken

Re: Announce Broken Ports

2003-07-25 Thread Kris Kennaway
On Fri, Jul 25, 2003 at 02:00:07PM -0300, Leonardo Lazarte wrote: As seen in several messages to this and other lists, the PORTS mecanism has been broken. I have read about some patches and possible solutions, but I could not find an easy way to overcome the problem. Shouldn't it be