Re: gcc related -current upgrade problems
On Fri, Jul 25, 2003 at 05:45:10PM -0700, Scott M. Likens wrote: > These issues have been addressed in KDE 3.1.3 if you're patient enough > for Will to work out the kinks the ports will be updated in a week or > less. The issue is not KDE related one, rather the base c++ headers trigger all sorts of warnings. Apparently on other operating systems libstdc++ does not trigger these warnings. - alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc related -current upgrade problems
Le Saturday 26 July 2003 00:46, John a écrit : > . > /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:62:25: attempt to use > poisoned "malloc" /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:63:25: > attempt to use poisoned "calloc" > /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:64:25: attempt to use > poisoned "realloc" /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:65:25: > attempt to use poisoned "strdup" mkdep: compile failed Hello, I've seen yesterday the exact same error : (maybe some bad wave coming to us from the outer space ?) one one machine (A). What was surprising in my case was that this error was systematic : I've tried three compilations in a succession to be sure it was not an error due to bad hardware. Then I've transferred the hard disk to another machine (B), and relaunched the "make buildworld" to check that the compiler and the sources on the disk were good (and indeed the make buildworld an make buildkernel succeeded on machine B) then I've re-transferred back the disk to the first machine, and I could then "make buildworld" - big surprise ? the first machine uses a Pentium-4 mobile (a real P-IV, not a Banias) and the second machine uses a Pentium-III TfH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc related -current upgrade problems
On Fri, Jul 25, 2003 at 05:45:10PM -0700, Scott M. Likens wrote: > These issues have been addressed in KDE 3.1.3 if you're patient enough > for Will to work out the kinks the ports will be updated in a week or > less. Much more likely someone else on kde-freebsd is going to solve those problems, if they aren't already. regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc related -current upgrade problems
On Fri, 2003-07-25 at 16:38, James Tanis wrote: > Has anybody had problems compiling, kde most notably, with gcc3.3 in > -current? I'd post the error, which seemed STL related, but I thought I'd ask > first. I tried installing the stlport port on the offchance this would fix > the problem, but that also came to (a much quicker) screeching halt. I > believe it can't find ctime. It's been doing this for sometime, I'm also > wondering if I have any dependencies missing since this last install is the > first time I've ever installed kde without using source originally.. but I > haven't been able to find anything that the ports system could be missing. These issues have been addressed in KDE 3.1.3 if you're patient enough for Will to work out the kinks the ports will be updated in a week or less. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc related -current upgrade problems
Has anybody had problems compiling, kde most notably, with gcc3.3 in -current? I'd post the error, which seemed STL related, but I thought I'd ask first. I tried installing the stlport port on the offchance this would fix the problem, but that also came to (a much quicker) screeching halt. I believe it can't find ctime. It's been doing this for sometime, I'm also wondering if I have any dependencies missing since this last install is the first time I've ever installed kde without using source originally.. but I haven't been able to find anything that the ports system could be missing. On Friday 25 July 2003 19:10, Barney Wolff wrote: > On Fri, Jul 25, 2003 at 06:46:50PM -0400, John wrote: > > rm -rf src obj > > cd /usr > > cvs -Rqd /home/ncvs co -P src > > cd src > > make buildkernel > > You can't buildkernel before buildworld. Do read UPDATING and the > handbook. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc related -current upgrade problems
- Barney Wolff's Original Message - > On Fri, Jul 25, 2003 at 06:46:50PM -0400, John wrote: > > > > rm -rf src obj > > cd /usr > > cvs -Rqd /home/ncvs co -P src > > cd src > > make buildkernel ggrrr.. that should be: 13 make buildworld > /tmp/b.log 2>&1 & > You can't buildkernel before buildworld. Do read UPDATING and the handbook. Yes, I know. I just can't type... :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc related -current upgrade problems
On Fri, Jul 25, 2003 at 06:46:50PM -0400, John wrote: > > rm -rf src obj > cd /usr > cvs -Rqd /home/ncvs co -P src > cd src > make buildkernel You can't buildkernel before buildworld. Do read UPDATING and the handbook. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
