Re: broken ports
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 reinstall because i believe that is a soluion. David On 09/02/2009, Frank Shute wrote: > 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 hopefully your system is then back to normal. >> >> I tried all this and rtorrent would still not install, with the same >> error at configure. I was however able to pkg_deinstall the gcc it >> installed. That didn't solve any problems though. >> >> I feel that it might be easier to focus on the following compiling >> problem that still exists: >> >> viper:~$ gcc -o hello hello.c >> /usr/bin/ld: cannot find -lgcc_s > > What this is telling you is the linker, ld(1), can't find the gcc_s > library. ldconfig(8) tells ld where to look. > > What does: > > $ ldconfig -r | grep gcc_s > > tell you now that you've removed that compiler? You should get > something like: > > $ ldconfig -r | grep gcc_s > 30:-lgcc_s.1 => /lib/libgcc_s.so.1 > > i.e. It's looking in the system libs. > > If it still tells you that the lib is under /usr/local/lib, then > there's your problem & you have to regenerate a fresh hints file, I > think. > > The problem is that I've never (IIRC) installed a compiler from > ports & I don't know how it screws with the compiler toolchain & hence > how to put it right. Hence, I've cc'd this to hackers@ in the hope that > someone who is more familiar with the toolchain can give advice. > > > Regards, > > -- > > Frank > > > Contact info: http://www.shute.org.uk/misc/contact.html > > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: broken ports
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 hopefully your system is then back to normal. > > I tried all this and rtorrent would still not install, with the same > error at configure. I was however able to pkg_deinstall the gcc it > installed. That didn't solve any problems though. > > I feel that it might be easier to focus on the following compiling > problem that still exists: > > viper:~$ gcc -o hello hello.c > /usr/bin/ld: cannot find -lgcc_s What this is telling you is the linker, ld(1), can't find the gcc_s library. ldconfig(8) tells ld where to look. What does: $ ldconfig -r | grep gcc_s tell you now that you've removed that compiler? You should get something like: $ ldconfig -r | grep gcc_s 30:-lgcc_s.1 => /lib/libgcc_s.so.1 i.e. It's looking in the system libs. If it still tells you that the lib is under /usr/local/lib, then there's your problem & you have to regenerate a fresh hints file, I think. The problem is that I've never (IIRC) installed a compiler from ports & I don't know how it screws with the compiler toolchain & hence how to put it right. Hence, I've cc'd this to hackers@ in the hope that someone who is more familiar with the toolchain can give advice. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
How to troubleshoot why ath0 can't connect to a passwordless wireless network?
I have a several wireless networks without password that my linux box easily connects to. On FreeBSD 'ifconfig ath0 up scan' command shows it. 'ifconfig ath0 ssid up' brings interface to 'associated' state. But dhclient fails to set it up. I have another device on the same system: ral0. It sometimes connects to these networks ok, sometimes has the same problem. What can I do to understand what may be a problem with ath0 in my case? I tried to use tcpdump. It shows outbound DHCP packets and nothing is inbound. I asked similar question here before, somebody asked me to downgrade atheros driver to one particular lower version. But this didn't help. Relevant dmesg lines are: ath_hal: 0.9.30.13 (AR5210, AR5211, AR5212, AR5216, RF5111, RF5112, RF2413, RF5413, RF2133) ath0: mem 0xcffe-0xcffe irq 16 at device 5.0 on pci0 ath0: mac 7.8 phy 4.5 radio 5.6 I use 71-PRERELEASE Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
