Hi all,
I just committed a fix to the libstdc++ errors people see on the initial
bootstrap from gcc 2.7.2 to EGCS. AFAIK, there are *NO* remaining
bootstrap problems.
If anybody has *ANY* bootstraping problems going from a pre-April 1st
-CURRENT to the latest and greatest I want to hear about it
On Wed, Apr 07, 1999 at 12:51:50AM -0700, David O'Brien wrote:
> AFAIK, there are *NO* remaining bootstrap problems.
NOTE, I am assuming one is *NOT* using the "-j" option.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsu
* From: "David O'Brien"
*
* Hi all,
*
* I just committed a fix to the libstdc++ errors people see on the initial
* bootstrap from gcc 2.7.2 to EGCS. AFAIK, there are *NO* remaining
* bootstrap problems.
I don't know about the bootstrapping problems but 4.0-snaps started
showing up again
> I don't know about the bootstrapping problems but 4.0-snaps started
> showing up again on current.freebsd.org today (19990406)
I wouldn't trust that 4.0-snap. That one should have a broken
/usr/lib/libstdc++. I can send you working versions if you need.
The 19990407 4.0-sna
Brian Somers writes:
>> I'll be in the Reading / London area from Friday morning until
>> Sunday evening. If there are any FreeBSD events taking place send
>> me email and I'll try to pop around...
>
>There's one this evening (Wednesday) in London, but nothing on the
>weekend.
>
>If you're intere
* Dag-Erling Smorgrav (d...@flood.ping.uio.no) [990403 17:33]:
> Existing MD5 passwords will still work. New users will get DES
> passwords.
Thanks, but how do I get all my "old" users to use DES crypted passwords?
Maybe I just should purify my network to loose those DES boxes and run
FreeBSD md
> > The first thing is that I guess the should be ,
>
> My understanding is that it stands for "no damage".
OK - I just thought it might have been a typo.
> > Backing out the last change to ide_pci.c seems to fix the problem.
> > I've lots of flags turned on in the kernel config file (0xa0ffa0f
Anders Andersson writes:
>* Dag-Erling Smorgrav (d...@flood.ping.uio.no) [990403 17:33]:
>
>> Existing MD5 passwords will still work. New users will get DES
>> passwords.
>
>Thanks, but how do I get all my "old" users to use DES crypted passwords?
Well, the short answer is 'you get them to change
Anders Andersson wrote:
> * Dag-Erling Smorgrav (d...@flood.ping.uio.no) [990403 17:33]:
>
> > Existing MD5 passwords will still work. New users will get DES
> > passwords.
>
> Thanks, but how do I get all my "old" users to use DES crypted passwords?
Unfortunately, passwd(1) will helpfully maint
Anders Andersson writes:
> Maybe I just should purify my network to loose those DES boxes and run
> FreeBSD md5 native only, that would be more secure and faster right?
More secure and *slower*. When it comes to password hashing, slower is
better, because it makes brute force and dictionary attac
* Peter Wemm (pe...@netplex.com.au) [990407 11:07]:
>
> Unfortunately, passwd(1) will helpfully maintain the same encryption
> method as was used before. ie: if a user has a MD5 passwd, the new one
> will also be MD5, regardless of the default.
>
> What I've wanted to do for some time is have a
> > OK. Can I assume that you have only one drive on the machine? Have
> > you tried a smaller DMA transfer size (say, to start with,
> > 0xa001a001)?
>
> I actually have three drives and a cdrom on the two IDE busses, but it
> only seems to complain about the first one - I don't know if that is
On Wednesday, 7 April 1999 at 11:44:23 +0200, Soren Schmidt wrote:
>>> OK. Can I assume that you have only one drive on the machine? Have
>>> you tried a smaller DMA transfer size (say, to start with,
>>> 0xa001a001)?
>>
>> I actually have three drives and a cdrom on the two IDE busses, but it
>
> If it's a redirected output file you simply make it O_APPEND, at which
> point the seek offset in the descriptor becomes irrelevant.
As others have pointed out, O_APPEND is much newer than the
offset-sharing behavior.
It also doesn't fix things for inputs. Of course with buffering, it
* From: "David O'Brien"
* I wouldn't trust that 4.0-snap. That one should have a broken
* /usr/lib/libstdc++. I can send you working versions if you need.
*
* The 19990407 4.0-snap should be gold (well silver as we are still using
* the worse of the excptions stack u
> By the way, do I need to rebuild the private XFree86 package when I
> grab a better snap or is that not necessary? (That part is not
> automatic)
I don't believe there are any C++ programs in XFree86, so you would be
Ok. You would have noticed that C++ programs would not link.
--
-- Dav
This version survived for a little longer, but hung (on the 486 box) whilst
doing a recursive ls of a large directory tree. Again, no messages, except
for one which came up as the box was booting, whilst it was starting squid.
The box was OK for about 4 minutes after this message, which was
"rl0:
* From: "David O'Brien"
* I don't believe there are any C++ programs in XFree86, so you would be
* Ok. You would have noticed that C++ programs would not link.
Ok, thanks. BTW, the list of ports that built in 3.1 but failed in
4.0 are in
http://bento.freebsd.org/~asami/errorlogs/4-latest-3
Hello,
I just wanted to make egcs as the default compiler and tried to make world
wit ctm src-cur.3819. I got the error message. Can anyone help ? Thanks.
Clarence
=== Error ===
In file included from
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/xm-i386.h:43
doesn't matter how much i attempt to cvsup and make world in the last 24 hours
i get this error, this is after i made world while interducing EGCS to FreeBSD,
i had to do another make world cuz my C++ compiler couldn't make executables
and that produces this situation.
===> cc_int
make : dont kn
Now /sys/boot can't be compiled with gcc due to non-existent -Os added.
Is it intentional or can be removed for backward compatibility?
--
Andrey A. Chernov
http://nagual.pp.ru/~ache/
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y
To Unsubscribe: send mail to majord...@freebsd.org
w
Tomer Weller wrote:
>
> doesn't matter how much i attempt to cvsup and make world in the last 24 hours
> i get this error, this is after i made world while interducing EGCS to
> FreeBSD,
> i had to do another make world cuz my C++ compiler couldn't make executables
> and that produces this situ
I had this same problem last night after a fresh cvsup. I redid the make
world without my normal -j4 and it completed fine.
-
Jason Tatem "What you want is irrelevant.
VC3, Inc. What you hav
As it was pointed earlier in this list currently make world fails when -jn
option is
used. Try to compile without -jn.
Jason Tatem wrote:
> I had this same problem last night after a fresh cvsup.? I redid the make
> world without my normal -j4 and it completed fine.
>
> -
"Andrey A. Chernov" wrote:
>
> Now /sys/boot can't be compiled with gcc due to non-existent -Os added.
> Is it intentional or can be removed for backward compatibility?
It can be removed for backward compatibility. What it does is
produce a smaller code. Egcs needs it, gcc doesn't.
--
Daniel C.
just wanted to point out i think this is a great mailing list, i just post a msg
and get 4 replys in 30 minutes, keep up the good work guys/gals !
==
Tomer Weller
s...@i.am
well...@netvision.net.il
"Drugs are good, and if you do'em
pepole think that you'
> The 19990407 4.0-snap should be gold (well silver as we are still using
> the worse of the excptions stack unwinding method, jdp and I will change
> this soon)
That snap and those following it are pending... Peter broke the
compat lib stuff last night so the snaps are falling o
In message <19990407081419.28682.qm...@ewok.creative.net.au>, adr...@freebsd.or
G writes:
>Brian Somers writes:
>>> I'll be in the Reading / London area from Friday morning until
>>> Sunday evening. If there are any FreeBSD events taking place send
>>> me email and I'll try to pop around...
>>
>>T
gcc compilation with -pipe -O2:
96 -rwxr-xr-x 1 root wheel - 97379 Mar 14 10:32 coolbrowse*
1064 -rwxr-xr-x 1 root wheel - 1076216 Mar 14 10:32 coolbrowse.static*
2064 -rwxr-xr-x 1 root wheel - 2104523 Mar 14 10:31 cooledit*
2992 -rwxr-xr-x 1 root wheel - 3054807 Mar 14 10:32 coole
On 07-Apr-99 Satoshi - the Wraith - Asami wrote:
> Errors are starting to appear in
>
> http://bento.freebsd.org/~asami/errorlogs/4-latest/
Weird that CoolEdit is on that list.
I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both work
a-ok after patching up ltconfig to make share
I can't get a make world to work with egcs. I deleted the whole obj
directory, and recvsuppped the entire source tree, and it still doesn't
work. Every time I cvsup I get a different error while compiling.
Please Help.
Kenneth Culver
To Unsubscribe: send mail to majord...@freebsd.org
with "un
On 07-Apr-99 Karl Pielorz wrote:
>
>> doesn't matter how much i attempt to cvsup and make world in the last 24
>> hours i get this error, this is after i made world while interducing EGCS
>> to FreeBSD, i had to do another make world cuz my C++ compiler couldn't
>> make executables and that produc
On 07-Apr-99 Kenneth Wayne Culver wrote:
> I can't get a make world to work with egcs. I deleted the whole obj
> directory, and recvsuppped the entire source tree, and it still doesn't
> work. Every time I cvsup I get a different error while compiling.
OK, make sure ye go to /usr/src/gnu/usr.bin/
In article ,
Jeroen Ruigrok/Asmodai wrote:
> gcc compilation with -pipe -O2:
>
> 96 -rwxr-xr-x 1 root wheel - 97379 Mar 14 10:32 coolbrowse*
> 1064 -rwxr-xr-x 1 root wheel - 1076216 Mar 14 10:32 coolbrowse.static*
...
File sizes don't mean much. It would be more interesting to compar
On 07-Apr-99 John Polstra wrote:
> In article ,
> Jeroen Ruigrok/Asmodai wrote:
>> gcc compilation with -pipe -O2:
>>
>> 96 -rwxr-xr-x 1 root wheel - 97379 Mar 14 10:32 coolbrowse*
>> 1064 -rwxr-xr-x 1 root wheel - 1076216 Mar 14 10:32
>> coolbrowse.static*
> ...
>
> File sizes don't
On Wed, 7 Apr 1999, Tomer Weller wrote:
>
> doesn't matter how much i attempt to cvsup and make world in the last 24 hours
> i get this error, this is after i made world while interducing EGCS to
> FreeBSD,
> i had to do another make world cuz my C++ compiler couldn't make executables
> and th
Folks,
I'm wondering if there have been some changes made in the
installation procedure for -CURRENT from -STABLE?
What I'm hoping for is a completely unattended installation
procedure. Once I select what I want installed, I want to be able to
select the installation method, input my conf
On Thu, Apr 08, 1999 at 01:15:32AM +0900, Daniel C. Sobral wrote:
> "Andrey A. Chernov" wrote:
> >
> > Now /sys/boot can't be compiled with gcc due to non-existent -Os added.
> > Is it intentional or can be removed for backward compatibility?
>
> It can be removed for backward compatibility. What
Alex Zepeda wrote:
>
> On Mon, 5 Apr 1999, Matthew Dillon wrote:
>
> > There is nothing beyond -O2. Well, there's -O3, which tries to
> > inline static functions, but that typically isn't beneficial because
> > it really bloats up the code and subroutine calls on intel cpus are
> >
>I'm wondering if there have been some changes made in the
> installation procedure for -CURRENT from -STABLE?
Not enough to give you what you're asking for here, really. :(
> installed, etc I certainly don't want to have to hit return a
> bazillion times to get through the warnings abou
# fsck -p
/dev/rda0s1a: 2291 files, 34981 used, 4010 free (274 frags, 467 blocks, 0.7%
fragmentation)
/dev/rccd0c: CANNOT READ: BLK 16
/dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.
fsck in free(): warning: pointer to wrong page.
fsck in free(): warning: page is already free
In article <19990407221941.a91...@nagual.pp.ru>,
Andrey A. Chernov wrote:
> On Thu, Apr 08, 1999 at 01:15:32AM +0900, Daniel C. Sobral wrote:
> > "Andrey A. Chernov" wrote:
> > >
> > > Now /sys/boot can't be compiled with gcc due to non-existent -Os added.
> > > Is it intentional or can be remove
Yep. It would be very good if you could capture a preferably small
image of a filesystem which makes this happen and make it available
to the committers via a PR
Poul-Henning
In message <19990407205026.a27...@cicely8.cicely.de>, Bernd Walter writes:
># fsck -p
>/dev/rda0s1a: 2291 files, 34981
On 07-Apr-99 Andrey A. Chernov wrote:
> The problem is deeper. When I reemove it, I got this error:
>
> -2100 bytes available
tried with -O2 yet?
> it seems that boot2 needs to be reduced, and I don't know why it becomes
> that big and what can be reduced. First candidates are static cmd[512]
>
On Wed, Apr 07, 1999 at 09:05:35PM +0200, Poul-Henning Kamp wrote:
>
> Yep. It would be very good if you could capture a preferably small
> image of a filesystem which makes this happen and make it available
> to the committers via a PR
>
nothing to capure - because there ist no filesystem.
I ju
In message <19990407211508.a27...@cicely8.cicely.de>, Bernd Walter writes:
>On Wed, Apr 07, 1999 at 09:05:35PM +0200, Poul-Henning Kamp wrote:
>>
>> Yep. It would be very good if you could capture a preferably small
>> image of a filesystem which makes this happen and make it available
>> to the
On Tue, 6 Apr 1999, David O'Brien wrote:
> > Well what would be the chances of getting the pgcc patches committed?
>
> I'm quite interested in doing this, BUT only after the dust has settled
> on the EGCS import and the Alpha build is fixed. Also the 1.1.2 PGCC
> patches aren't available yet.
"Andrey A. Chernov" wrote:
>
> The problem is deeper. When I reemove it, I got this error:
>
> -2100 bytes available
>
> it seems that boot2 needs to be reduced, and I don't know why it becomes
> that big and what can be reduced. First candidates are static cmd[512] and
> kernel[1024]. Please fi
On Thu, Apr 08, 1999 at 08:09:43AM +0900, Daniel C. Sobral wrote:
> > -2100 bytes available
> >
> > it seems that boot2 needs to be reduced, and I don't know why it becomes
> > that big and what can be reduced. First candidates are static cmd[512] and
> > kernel[1024]. Please fix so it can be stil
Andrey A. Chernov wrote:
> On Thu, Apr 08, 1999 at 08:09:43AM +0900, Daniel C. Sobral wrote:
> > > -2100 bytes available
> > >
> > > it seems that boot2 needs to be reduced, and I don't know why it becomes
> > > that big and what can be reduced. First candidates are static cmd[512] and
> > > kerne
* Weird that CoolEdit is on that list.
*
* I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both work
* a-ok after patching up ltconfig to make shared libs.
Did you click on the links to see what it's complaining about?
"It worked here" doesn't mean much in this context, as the
OK - I've made a little progress. It only seems to be the first drive
that it doesn't like. I can boot the system fine with the new kernel
as long as I don't go near wd0. I dunno if it likes wd2.
I've included what seem to be the useful bits of a boot -v as seen by
dmesg for both the new and the o
On Wed, Apr 7, 1999, Kenneth Wayne Culver wrote:
> I can't get a make world to work with egcs. I deleted the whole obj
> directory, and recvsuppped the entire source tree, and it still doesn't
> work. Every time I cvsup I get a different error while compiling.
CVSup now, and build world. Do _
In article , Jeroen
Ruigrok/Asmodai wrote:
> This raises an interesting point I think. Do we need to maintain
> gcc/egcs compatibility? Or do we, since we track CURRENT, say:
> "alas, that's progression for ye?"
Yep, alas, that's progression for ye. We have never supported mix
& match of source
In article <19990408040432.a74...@nagual.pp.ru>,
Andrey A. Chernov wrote:
>
> Yes, of course I am shure. BTW, I see lots of malign options in cc call,
> maybe they play role.
>
> cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin
> -malign-functions=0 -malign-jumps=0 -malign-loop
* From: John Polstra
* Yep, alas, that's progression for ye. We have never supported mix
* & match of sourceballs from different releases. We do our best
* to support running old executables on newer systems, but that's a
* completely different issue.
:
* I am only speaking for John Pols
> I just wanted to make egcs as the default compiler and tried to make world
...
> /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3:
> linux.h: No such file or directory
The fact you are refering to "linux.h" says you've some kind of error...
I never commited linux.h or refere
On Wed, Apr 07, 1999 at 05:50:24PM -0700, John Polstra wrote:
> You removed the "-Os" but you didn't add back the "-O2" that
> originally was there.
Thanx, it works now. It was the reason I overlook.
--
Andrey A. Chernov
http://nagual.pp.ru/~ache/
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++)
> Of course, passwd(1) should ideally be able to be told to ignore the old
> method too - it looks like /etc/auth.conf is in the beginnings of this.
When I proposed changing this and adding a knob in auth.conf, it was said
PAM is really the place for this.
Actually a committed (forgot who) tried
On Wed, 7 Apr 1999, Chris Costello wrote:
> On Wed, Apr 7, 1999, Kenneth Wayne Culver wrote:
> > I can't get a make world to work with egcs. I deleted the whole obj
> > directory, and recvsuppped the entire source tree, and it still doesn't
> > work. Every time I cvsup I get a different error whil
On Wed, 7 Apr 1999, John Polstra wrote:
> In article , Jeroen
> Ruigrok/Asmodai wrote:
>
> > This raises an interesting point I think. Do we need to maintain
> > gcc/egcs compatibility? Or do we, since we track CURRENT, say:
> > "alas, that's progression for ye?"
>
> Yep, alas, that's progressi
Chuck Robey wrote:
> configure:4096: /bin/sh ./libtool --silent --mode=link c++ -o conftest -Os
> -pipe
> -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include
> -I/usr/l
> ocal/include/giflib -s -L/usr/local/lib -L/usr/X11R6/lib conftest.C
> -lkdecore
> -lqt -lXext -lX11
On Wed, 7 Apr 1999, John Polstra wrote:
> Chuck Robey wrote:
>
> > configure:4096: /bin/sh ./libtool --silent --mode=link c++ -o conftest -Os
> > -pipe
> > -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include
> > -I/usr/l
> > ocal/include/giflib -s -L/usr/local/lib -L/usr/X
Chuck Robey wrote:
> Thanks for the clue, John! As much as I hate redoing the KDE and
> gnome ports, it looks like doing that again ...
I don't blame you. I've never even built them, for the simple (lazy)
reason that they looked like they'd be too painful to upgrade.
John
---
John Polstra
On Wed, 7 Apr 1999, John Polstra wrote:
> Chuck Robey wrote:
>
> > Thanks for the clue, John! As much as I hate redoing the KDE and
> > gnome ports, it looks like doing that again ...
>
> I don't blame you. I've never even built them, for the simple (lazy)
> reason that they looked like they'd
* From: Chuck Robey
* I'm very close to relying on packages for them. I'll have to see if
* there are *very* up-to-date packages. If there aren't, and I end up
As long as they build, FTP packages are usually within one week
(usually less) of the ports tree on both 3.1 and 4.0.
-PW
To Uns
my system hangs when booting with update5 of the
ata/atapi driver with the following in my kernel config:
controller ata0
device atadisk0# ATA disks
device atapifd0# ATAPI floppy drives
the boot messages:
Probing for devices on PCI bus 0:
ch
>> it seems that boot2 needs to be reduced, and I don't know why it becomes
>> that big and what can be reduced. First candidates are static cmd[512] and
>> kernel[1024]. Please fix so it can be still compiled with gcc.
>
>Why? The compiler in -current is egcs, not gcc. If you want to
>use the o
Bruce Evans wrote:
> Everything should be buildable with CC=aac (any ANSI compiler), but
> that's asking too much for programs like kernels and boot blocks.
The problem in this case is just that the compilers require
different command line options. It's asking _way_ too much to
require those to
>> Everything should be buildable with CC=aac (any ANSI compiler), but
>> that's asking too much for programs like kernels and boot blocks.
>
>The problem in this case is just that the compilers require
>different command line options. It's asking _way_ too much to
>require those to be identical.
Bruce Evans wrote:
>>The problem in this case is just that the compilers require
>>different command line options. It's asking _way_ too much to
>>require those to be identical.
>
> Actually, they don't. Compiler-specific options can be put in ${CC}.
> Perhaps they even should be.
But in this c
"ftp" on 4.0-very-current (post egcs make world) randomly hangs during
sessions...
I never succeded in finishing a session lately.
To transfer some files from my home to my isp server I had to do an "ftp"
from the server and a "get" to them...
The ftp server works normally and fetch is ok ...
Pr
On Wed, 7 Apr 1999, Chuck Robey wrote:
> > Bzzt. You've got something old that's still using libstdc++.so.2.
> > You can't combine that with something that uses libstdc++.so.3. I.e.,
> > you can't use both versions at the same time. I'd suggest rebuilding
> > the port and everything that it dep
On Wed, 7 Apr 1999, John Polstra wrote:
> Chuck Robey wrote:
>
> > Thanks for the clue, John! As much as I hate redoing the KDE and
> > gnome ports, it looks like doing that again ...
>
> I don't blame you. I've never even built them, for the simple (lazy)
> reason that they looked like they'd
>> Actually, they don't. Compiler-specific options can be put in ${CC}.
>> Perhaps they even should be.
>
>But in this case, we want "-Os" (egcs) or "-O2" (gcc) only for
>building boot -- not for everything. It could be parameterized with
>make macros like "OPT_SMALL" and "OPT_FAST" in the *.mk f
On 08-Apr-99 Satoshi - the Wraith - Asami wrote:
> * Weird that CoolEdit is on that list.
> *
> * I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both
> work
> * a-ok after patching up ltconfig to make shared libs.
>
> Did you click on the links to see what it's complaining abou
> Actually, they don't. Compiler-specific options can be put in ${CC}.
I'm leading him... leading... *BLAM!* *BLAM!* Yes! Got him with
both barrels, and he was really moving too! :-)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body
John Polstra wrote:
> Bruce Evans wrote:
>
> > Everything should be buildable with CC=aac (any ANSI compiler), but
> > that's asking too much for programs like kernels and boot blocks.
>
> The problem in this case is just that the compilers require
> different command line options. It's asking
"David O'Brien" wrote:
> Actually a committed (forgot who) tried to overhall the crypt stuff a few
> months ago and it blew up in his face. I don't think anyone has changed
> since. A shame.
Brandon Gillespie.
I have a copy of his code (almost) ready-to-go.
M
--
Mark Murray
Join the anti-SPAM
79 matches
Mail list logo
