HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Murray Stokely]

   As discussed at BSDCon, the release engineers are committed to
releasing a relatively stable snapshot of FreeBSD -CURRENT on or
around April 1, 2002.  Obviously, a lot of major components are still
in progress, but a great deal of work has already been accomplished,
and could benefit from the additional exposure that a polished
snapshot with full package set and documentation will provide.

  To this end, we would like to request that commits for the next 7
days to HEAD be made with special care.  -CURRENT is in pretty good
shape right now, so we're not requiring approval for all commits.
However, we do request that re@ be consulted for any commits with a
substantial risk.  This includes non-trivial changes to the VM system,
filesystems, network stack, important userland components, and others.
If unsure about a commit, please ask.  Changes specific to emerging
architectures (sparc64, ia64, powerpc) are exempt from this approval
requirement no matter how substantial the change (as long as it only
affects the given architecture).

  On March 15, a RELENG_5_0_DP1 branch will be created in CVS for
final release polishing.  This will allow us to provide translated
release notes, sync up sysinstall and the package set, bump version
numbers, and tweak default diagnostic settings without further
impacting -CURRENT developers.  Commits to this branch will require
re@ approval.

  For further information about our plans for 5.0 Developer Previews,
and the eventual release of FreeBSD 5.0 in November, please see the
new release engineering section of the FreeBSD web site :

http://www.FreeBSD.org/releng

  If you would like to help out with some of the quality-assurance
work for the upcoming developer preview, please install a -CURRENT
snapshot from :

ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/i386

  - or -

ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386

  And post your findings to current@ or qa@.

(Sorry, Alpha -CURRENT snapshots are harder to come by at the moment,
but Compaq just donated some hardware to alleviate this problem in the
future.)

  Thanks for your cooperation,

 - Murray (on behalf of The Release Engineering Team)



msg35781/pgp0.pgp
Description: PGP signature

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Jeff Roberson]

Should I postpone my allocator commit then?

Thanks,
Jeff



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Mark Murray]

>   To this end, we would like to request that commits for the next 7
> days to HEAD be made with special care.  -CURRENT is in pretty good
> shape right now, so we're not requiring approval for all commits.

I have a Perl-5.6.1 upgrade. Is that too risky? Apart from the perl
stuff itself, there are some other makefiles and mtree things that
need to be done. Also the ports will be affected (not by very much).

M
-- 
o   Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Andrey A. Chernov]

On Fri, Mar 08, 2002 at 11:16:53 +, Mark Murray wrote:
> >   To this end, we would like to request that commits for the next 7
> > days to HEAD be made with special care.  -CURRENT is in pretty good
> > shape right now, so we're not requiring approval for all commits.
> 
> I have a Perl-5.6.1 upgrade. Is that too risky? Apart from the perl
> stuff itself, there are some other makefiles and mtree things that
> need to be done. Also the ports will be affected (not by very much).

Mark, please, before the date don't forget to commit _trivial_ random()  
-> arc4random() fix for pam_unix() I ugre on for a long time.

-- 
Andrey A. Chernov
http://ache.pp.ru/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Brian Somers]

> >   To this end, we would like to request that commits for the next 7
> > days to HEAD be made with special care.  -CURRENT is in pretty good
> > shape right now, so we're not requiring approval for all commits.
> 
> I have a Perl-5.6.1 upgrade. Is that too risky? Apart from the perl
> stuff itself, there are some other makefiles and mtree things that
> need to be done. Also the ports will be affected (not by very much).

It's probably worth holding off for now and committing it after the 7 
days.  The 2 months between then and the DP2 release can shake out 
any problems it causes.

> M
> -- 
> o   Mark Murray
> \_
> O.\_Warning: this .sig is umop ap!sdn

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David W. Chapman Jr.]

>As discussed at BSDCon, the release engineers are committed to
> releasing a relatively stable snapshot of FreeBSD -CURRENT on or
> around April 1, 2002.  Obviously, a lot of major components are still
> in progress, but a great deal of work has already been accomplished,
> and could benefit from the additional exposure that a polished
> snapshot with full package set and documentation will provide.
> 
I don't know if this is something worth making it the snapshot, but 
currently kde doesn't work due to binuntils update.  It may work now 
after the most recent binutils update, but we have to recompile kde 
to see that I believe, andkdelibs cannot be compiled
which builds kde-config which the rest of the kde meta-ports try to 
run.

I think that last sentence is a huge run on and I by no means am 
trying to complain, just wondering if anyone thinks its important to 
make it on this snapshot.

-- 
David W. Chapman Jr.
[EMAIL PROTECTED]   Raintree Network Services, Inc. 
[EMAIL PROTECTED]   FreeBSD Committer 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[George V. Neville-Neil]

Does this include getting someone to fix picobsd for -CURRENT?

Is this important for the snapshots?

Later,
George

*** Making static libraries
cd /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf;  make depend;  make all;  
make
 install
rm -f .depend
mkdep -f .depend -a   -nostdinc -DSTANDARD_INCLUDE_DIR=/home/gnn/FreeBSD/src.la
t
est../usr/include -I/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common
/
home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crti.S 
/home/gnn/FreeBSD/src.latest
/lib/csu/i386-elf/crtn.S
mkdep -f .depend -a   -nostdinc -DSTANDARD_INCLUDE_DIR=/home/gnn/FreeBSD/src.la
t
est../usr/include -I/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common  
/ho
me/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c
/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:30: stddef.h: No such 
file
or directory
/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:31: stdlib.h: No such 
file
or directory
In file included from /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:32: 

/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common/crtbrand.c:28: 
sys/param
.h: No such file or directory
mkdep: compile failed
*** Error code 1

Stop in /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf.
*** Error code 1

Stop in /home/gnn/FreeBSD/src.latest.
*** Error code 1


-- 
George V. Neville-Neil  [EMAIL PROTECTED]
NIC:GN82 

"Those who would trade liberty for temporary security deserve neither" 
- Benjamin Franklin



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Brian Somers]

> >As discussed at BSDCon, the release engineers are committed to
> > releasing a relatively stable snapshot of FreeBSD -CURRENT on or
> > around April 1, 2002.  Obviously, a lot of major components are still
> > in progress, but a great deal of work has already been accomplished,
> > and could benefit from the additional exposure that a polished
> > snapshot with full package set and documentation will provide.
> > 
> I don't know if this is something worth making it the snapshot, but 
> currently kde doesn't work due to binuntils update.  It may work now 
> after the most recent binutils update, but we have to recompile kde 
> to see that I believe, andkdelibs cannot be compiled
> which builds kde-config which the rest of the kde meta-ports try to 
> run.
> 
> I think that last sentence is a huge run on and I by no means am 
> trying to complain, just wondering if anyone thinks its important to 
> make it on this snapshot.

If you're referring to the problems loading libpng.so (and probably 
other shared libraries), I can confirm that it's been fixed now.

> -- 
> David W. Chapman Jr.
> [EMAIL PROTECTED] Raintree Network Services, Inc. 
> [EMAIL PROTECTED] FreeBSD Committer 

-- 
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
  http://www.freebsd-services.com/
Don't _EVER_ lose your sense of humour !  



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Robert Watson]

On Fri, 8 Mar 2002, David W. Chapman Jr. wrote:

> >As discussed at BSDCon, the release engineers are committed to
> > releasing a relatively stable snapshot of FreeBSD -CURRENT on or
> > around April 1, 2002.  Obviously, a lot of major components are still
> > in progress, but a great deal of work has already been accomplished,
> > and could benefit from the additional exposure that a polished
> > snapshot with full package set and documentation will provide.
> 
> I don't know if this is something worth making it the snapshot, but
> currently kde doesn't work due to binuntils update.  It may work now
> after the most recent binutils update, but we have to recompile kde to
> see that I believe, andkdelibs cannot be compiled which builds
> kde-config which the rest of the kde meta-ports try to run. 
> 
> I think that last sentence is a huge run on and I by no means am trying
> to complain, just wondering if anyone thinks its important to make it on
> this snapshot. 

Hmm.  My impression was that the libpng stuff had been fixed, could you
confirm that KDE still doesn't build on 5.0-CURRENT?

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Joel Wilsson]

On Fri, Mar 08, 2002 at 08:59:53AM -0600, David W. Chapman Jr. wrote:
> >As discussed at BSDCon, the release engineers are committed to
> > releasing a relatively stable snapshot of FreeBSD -CURRENT on or
> > around April 1, 2002.  Obviously, a lot of major components are still
> > in progress, but a great deal of work has already been accomplished,
> > and could benefit from the additional exposure that a polished
> > snapshot with full package set and documentation will provide.
> > 
> I don't know if this is something worth making it the snapshot, but 
> currently kde doesn't work due to binuntils update.  It may work now 
> after the most recent binutils update, but we have to recompile kde 
> to see that I believe, andkdelibs cannot be compiled
> which builds kde-config which the rest of the kde meta-ports try to 
> run.

It works if you don't use objprelink, and then change a bunch of files
to include arpa/inet.h
I spent some time fixing this yesterday...
Here are my notes:

#include  in

kdelibs-2.2.2:
kdecore/kextsock.cpp
kio/ftp/ftp.cc
kio/tcpslavebase.cpp
arts/mcop/tcpconnection.cc

qt2.3.1:
src/kernel/qfont_x11.cpp
src/kernel/qpainter_x11.cpp
src/network/qdns.cpp
src/network/qsocketdevice_unix.cpp
also "uic" gets a weird dependency on "libclms.so_edata", so you need to run
ln -s /usr/local/lib/liblcms.so.1 /usr/local/lib/liblcms.so_edata && ldconfig -R

kdenetwork-2.2.2:
kit/kitsocket.cpp
kmail/kmacctimap.cpp
kmail/kmacctexppop.cpp
kmail/accountdialog.cpp
ktalkd/ktalkd/machines/forwmach.cpp
ktalkd/ktalkd/machines/talkconn.cpp
ktalkd/ktalkd/print.cpp
ktalkd/ktalkd/process.cpp
ktalkd/ktalkd/table.cpp

to make kdemultimedia-2.2.2 compile, don't use the FreeBSD-specific byteswapping
functions defined in kmidi/config.h, instead use the generic ones (which should
have been used in the first place anyway, imo)
remove the "ifdef #FreeBSD"-blah near XCHG_(LONG|SHORT)


I installed all those ports using make NO_DEPENDS=yes install since
I'm too lazy to figure out where the objprelink dep is defined.

> I think that last sentence is a huge run on and I by no means am 
> trying to complain, just wondering if anyone thinks its important to 
> make it on this snapshot.

I agree... -CURRENT was fine until the new binutils came into the tree.
First the libpng, then the KDE problems. I think we should wait a while
and fix ports using ntohl and friends (since someone seem to have decided
that netinet/in.h shouldn't define it or something) and make KDE build
again before making a "developer preview", but that's just my opinion.


// Joel Wilsson

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David W. Chapman Jr.]

> > currently kde doesn't work due to binuntils update.  It may work now
> > after the most recent binutils update, but we have to recompile kde to
> > see that I believe, andkdelibs cannot be compiled which builds
> > kde-config which the rest of the kde meta-ports try to run. 
> > 
> > I think that last sentence is a huge run on and I by no means am trying
> > to complain, just wondering if anyone thinks its important to make it on
> > this snapshot. 
> 
> Hmm.  My impression was that the libpng stuff had been fixed, could you
> confirm that KDE still doesn't build on 5.0-CURRENT?

Its not related to libpng, I believe that has been fixed, but I 
cannot tell for sure because kde cannot be compiled under -current.  
I'm not the only one that is experiencing it either, here is what I 
was told by Alan Eldridge <[EMAIL PROTECTED]>


On Tue, Mar 05, 2002 at 05:26:27PM -0600, David W. Chapman Jr. wrote:
>When I try to build kdelibs2 I get the following under recent
>-current builds
>
>,.deps/kextsock.pp -c kextsock.cpp  -fPIC -DPIC -o .libs/kextsock.o
>kextsock.cpp: In method `struct kde_addrinfo *
>KExtendedSocketLookup::results()'
>:
>kextsock.cpp:294: implicit declaration of function `int __htons(...)'
>kextsock.cpp:353: implicit declaration of function `int __htonl(...)'

Yes. Recent changes to netinet/in.h have made it require the inclusion
of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW, 
each
of these files must #include the other in order to work correctly.

As you  might guess, this is a less than desirable situation. A 
#includes
B and B #includes A is a very bad arrangement. However, unless both 
files
are overhauled, that is what will have to happen.

To say that this sucks is an understatement. I already have an open PR
on the arpa/inet.h problem. Now that the reverse dependency has been
made to occur, I have written portmgr@ requesting a referral to a
mainline developer who can handle this mess in an expedient manner.

In the meantime, you need to find every occurence of either of those
files being included, and make sure the other is included as
well. netinet/in.h needs to come first.

Since the problem is a large one, and any change will not happen
without a reasonable amount of deliberation, I suggest you submit a PR
with a patch for kdelibs source tree.

-- 
David W. Chapman Jr.
[EMAIL PROTECTED]   Raintree Network Services, Inc. 
[EMAIL PROTECTED]   FreeBSD Committer 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Will Andrews]

On Fri, Mar 08, 2002 at 10:17:16AM -0600, David W. Chapman Jr. wrote:
> > > currently kde doesn't work due to binuntils update.  It may work now
> > > after the most recent binutils update, but we have to recompile kde to
> > > see that I believe, andkdelibs cannot be compiled which builds
> > > kde-config which the rest of the kde meta-ports try to run. 
> > > 
> > > I think that last sentence is a huge run on and I by no means am trying
> > > to complain, just wondering if anyone thinks its important to make it on
> > > this snapshot. 
> > 
> > Hmm.  My impression was that the libpng stuff had been fixed, could you
> > confirm that KDE still doesn't build on 5.0-CURRENT?
> 
> Its not related to libpng, I believe that has been fixed, but I 
> cannot tell for sure because kde cannot be compiled under -current.  
> I'm not the only one that is experiencing it either, here is what I 
> was told by Alan Eldridge <[EMAIL PROTECTED]>

You said "binutils upgrade broke KDE" -- the quoted mail has
nothing to do with binutils.

-- 
wca

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David W. Chapman Jr.]

> > currently kde doesn't work due to binuntils update.  It may work now 
> > after the most recent binutils update, but we have to recompile kde 
> > to see that I believe, andkdelibs cannot be compiled
> > which builds kde-config which the rest of the kde meta-ports try to 
> > run.
> > 
> > I think that last sentence is a huge run on and I by no means am 
> > trying to complain, just wondering if anyone thinks its important to 
> > make it on this snapshot.
> 
> If you're referring to the problems loading libpng.so (and probably 
> other shared libraries), I can confirm that it's been fixed now.

I was curious about that, but it wasn't my main concern.  Have you 
been able to run anything that uses OBJPRELINK?

-- 
David W. Chapman Jr.
[EMAIL PROTECTED]   Raintree Network Services, Inc. 
[EMAIL PROTECTED]   FreeBSD Committer 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David W. Chapman Jr.]

On Fri, Mar 08, 2002 at 11:20:35AM -0500, Will Andrews wrote:
> On Fri, Mar 08, 2002 at 10:17:16AM -0600, David W. Chapman Jr. wrote:
> > > > currently kde doesn't work due to binuntils update.  It may work now
> > > > after the most recent binutils update, but we have to recompile kde to
> > > > see that I believe, andkdelibs cannot be compiled which builds
> > > > kde-config which the rest of the kde meta-ports try to run. 
> > > > 
> > > > I think that last sentence is a huge run on and I by no means am trying
> > > > to complain, just wondering if anyone thinks its important to make it on
> > > > this snapshot. 
> > > 
> > > Hmm.  My impression was that the libpng stuff had been fixed, could you
> > > confirm that KDE still doesn't build on 5.0-CURRENT?
> > 
> > Its not related to libpng, I believe that has been fixed, but I 
> > cannot tell for sure because kde cannot be compiled under -current.  
> > I'm not the only one that is experiencing it either, here is what I 
> > was told by Alan Eldridge <[EMAIL PROTECTED]>
> 
> You said "binutils upgrade broke KDE" -- the quoted mail has
> nothing to do with binutils.
> 
I'm sorry for the lack of clarity in my email, if I didn't explain it 
the way I wanted to here is a better attempt.  I cannot recompile kde 
due to the reasons stated in the quoted email so I'm not sure if the 
binutils problem has been fixed, but apparently a few people can 
vouch that it has.

-- 
David W. Chapman Jr.
[EMAIL PROTECTED]   Raintree Network Services, Inc. 
[EMAIL PROTECTED]   FreeBSD Committer 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Peter Pentchev]

On Fri, Mar 08, 2002 at 10:17:16AM -0600, David W. Chapman Jr. wrote:
> > > currently kde doesn't work due to binuntils update.  It may work now
> > > after the most recent binutils update, but we have to recompile kde to
> > > see that I believe, andkdelibs cannot be compiled which builds
> > > kde-config which the rest of the kde meta-ports try to run. 
[snip]
> I'm not the only one that is experiencing it either, here is what I 
> was told by Alan Eldridge <[EMAIL PROTECTED]>
> 
> 
> On Tue, Mar 05, 2002 at 05:26:27PM -0600, David W. Chapman Jr. wrote:
> >When I try to build kdelibs2 I get the following under recent
> >-current builds
> >
> >,.deps/kextsock.pp -c kextsock.cpp  -fPIC -DPIC -o .libs/kextsock.o
> >kextsock.cpp: In method `struct kde_addrinfo *
> >KExtendedSocketLookup::results()'
> >:
> >kextsock.cpp:294: implicit declaration of function `int __htons(...)'
> >kextsock.cpp:353: implicit declaration of function `int __htonl(...)'
> 
> Yes. Recent changes to netinet/in.h have made it require the inclusion
> of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW, 
> each
> of these files must #include the other in order to work correctly.
> 
> As you  might guess, this is a less than desirable situation. A 
> #includes
> B and B #includes A is a very bad arrangement. However, unless both 
> files
> are overhauled, that is what will have to happen.

FWIW, Alan filed a PR about that - bin/35598.

G'luck,
Peter

-- 
Peter Pentchev  [EMAIL PROTECTED][EMAIL PROTECTED]
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
What would this sentence be like if it weren't self-referential?



msg35804/pgp0.pgp
Description: PGP signature

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Robert Watson]

Sounds to me like there are fixes in the pipeline from Mike and Thomas.
Hopefully they'll get that committed in the next day or two so that KDE
can be happy on -CURRENT before the snapshot.

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services

On Fri, 8 Mar 2002, Peter Pentchev wrote:

> On Fri, Mar 08, 2002 at 10:17:16AM -0600, David W. Chapman Jr. wrote:
> > > > currently kde doesn't work due to binuntils update.  It may work now
> > > > after the most recent binutils update, but we have to recompile kde to
> > > > see that I believe, andkdelibs cannot be compiled which builds
> > > > kde-config which the rest of the kde meta-ports try to run. 
> [snip]
> > I'm not the only one that is experiencing it either, here is what I 
> > was told by Alan Eldridge <[EMAIL PROTECTED]>
> > 
> > 
> > On Tue, Mar 05, 2002 at 05:26:27PM -0600, David W. Chapman Jr. wrote:
> > >When I try to build kdelibs2 I get the following under recent
> > >-current builds
> > >
> > >,.deps/kextsock.pp -c kextsock.cpp  -fPIC -DPIC -o .libs/kextsock.o
> > >kextsock.cpp: In method `struct kde_addrinfo *
> > >KExtendedSocketLookup::results()'
> > >:
> > >kextsock.cpp:294: implicit declaration of function `int __htons(...)'
> > >kextsock.cpp:353: implicit declaration of function `int __htonl(...)'
> > 
> > Yes. Recent changes to netinet/in.h have made it require the inclusion
> > of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW, 
> > each
> > of these files must #include the other in order to work correctly.
> > 
> > As you  might guess, this is a less than desirable situation. A 
> > #includes
> > B and B #includes A is a very bad arrangement. However, unless both 
> > files
> > are overhauled, that is what will have to happen.
> 
> FWIW, Alan filed a PR about that - bin/35598.
> 
> G'luck,
> Peter
> 
> -- 
> Peter Pentchev[EMAIL PROTECTED][EMAIL PROTECTED]
> PGP key:  http://people.FreeBSD.org/~roam/roam.key.asc
> Key fingerprint   FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
> What would this sentence be like if it weren't self-referential?
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Michael G. Petry]

There seem to be two distinct problems.  The header one seems to have
resolution,I got around it by the nested include.  The second one may
be OBJPRELINK, but does seem to be nailed down yet. Martin Blapp ran into
what might be related problems in the OpenOffice port.  I've only seen it
on g++ related programs. Good hunting...

> Sounds to me like there are fixes in the pipeline from Mike and Thomas.
> Hopefully they'll get that committed in the next day or two so that KDE
> can be happy on -CURRENT before the snapshot.
> 
> Robert N M Watson FreeBSD Core Team, TrustedBSD Project
> [EMAIL PROTECTED]  NAI Labs, Safeport Network Services
> 




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Bruce Evans]

On Fri, 8 Mar 2002, David W. Chapman Jr. wrote:

> > Hmm.  My impression was that the libpng stuff had been fixed, could you
> > confirm that KDE still doesn't build on 5.0-CURRENT?
>
> Its not related to libpng, I believe that has been fixed, but I
> cannot tell for sure because kde cannot be compiled under -current.
> I'm not the only one that is experiencing it either, here is what I
> was told by Alan Eldridge <[EMAIL PROTECTED]>
>
>
> On Tue, Mar 05, 2002 at 05:26:27PM -0600, David W. Chapman Jr. wrote:
> >When I try to build kdelibs2 I get the following under recent
> >-current builds
> >
> >,.deps/kextsock.pp -c kextsock.cpp  -fPIC -DPIC -o .libs/kextsock.o
> >kextsock.cpp: In method `struct kde_addrinfo *
> >KExtendedSocketLookup::results()'
> >:
> >kextsock.cpp:294: implicit declaration of function `int __htons(...)'
> >kextsock.cpp:353: implicit declaration of function `int __htonl(...)'
>
> Yes. Recent changes to netinet/in.h have made it require the inclusion
> of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW,
> each
> of these files must #include the other in order to work correctly.

This is actually caused by the last round of endianness changes (in
 and ) breaking the previous round of
endianness changes in (, , 
and ).  Another round is planned to fix this.

I'm surprised that everyone hasn't complained about world breakage
from this.  It has been broken for almost 2 weeks now.  Everything
that goes near ntohl and has WARNS >= 2 fails to compile.  Without
WARNS, the bug is reported as above, but a bogus version of __hton*
is found in the library and only optimization of hton* is broken.

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Garance A Drosihn]

At 10:17 AM -0600 3/8/02, David W. Chapman Jr. wrote:
>Yes. Recent changes to netinet/in.h have made it require the
>inclusion of arpa/inet.h. As well, arpa/inet.h must include
>netinet/in.h. IOW, each of these files must #include the
>other in order to work correctly.
>
>As you  might guess, this is a less than desirable situation.
>[A #includes B] and [B #includes A] is a very bad arrangement.
>However, unless both files are overhauled, that is what will
>have to happen.
>
>To say that this sucks is an understatement. [...]

>Since the problem is a large one, and any change will not
>happen without a reasonable amount of deliberation, I suggest
>you submit a PR with a patch for kdelibs source tree.

Mike Barcroft, Bruce Evans, and maybe a few others are working
on an update to about eight different include files which should
clear up many of these issues.  I think it would be very desirable
to get this include-file-cleanup patch committed before the snapshot
is done.  The present version of this patch clears up a lot of the
compile-time warnings that come up when doing a buildworld of
current, but it still isn't quite right.

If this current snapshot means more people will be running current,
then I'd hate to see them chasing after compile-time warnings which
are due to the present state of the system include files...

-- 
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David W. Chapman Jr.]

> I'm surprised that everyone hasn't complained about world breakage
> from this.  It has been broken for almost 2 weeks now.  Everything
> that goes near ntohl and has WARNS >= 2 fails to compile.  Without
> WARNS, the bug is reported as above, but a bogus version of __hton*
> is found in the library and only optimization of hton* is broken.

Very strange, I have been making world over the past few weeks (just 
did one yesterday) with no problems, maybe I have some stuff that it 
stale?
-- 
David W. Chapman Jr.
[EMAIL PROTECTED]   Raintree Network Services, Inc. 
[EMAIL PROTECTED]   FreeBSD Committer 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Murray Stokely]

On Fri, Mar 08, 2002 at 05:28:24AM -0500, Jeff Roberson wrote:
> Should I postpone my allocator commit then?

Hi Jeff,

   Yes, I would prefer to wait a week on this.  After we've created
the RELENG_5_0_DP1 branch, you may commit the new allocator code to
-CURRENT.  That will give us plenty of time to iron out any problems
before shipping a second developer preview this summer.

Thanks,
- Murray

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Chris Hedley]

On Fri, 8 Mar 2002, Murray Stokely wrote:
>As discussed at BSDCon, the release engineers are committed to
> releasing a relatively stable snapshot of FreeBSD -CURRENT on or
> around April 1, 2002.  Obviously, a lot of major components are still
> in progress, but a great deal of work has already been accomplished,
> and could benefit from the additional exposure that a polished
> snapshot with full package set and documentation will provide.

Dunno if this is already known, but I just had a kernel from a cvsup of
the 5th of this month go bang about half an hour ago; I'm afraid I don't
have a lot of info available as it was unattended at the time and auto-
rebooted (and I deleted the core files before I read this because I needed
the disc space... sorry) so the only info I can offer is that it was in
the process of doing a "make -j10 buildworld" and barfed in
pmap_remove_pages (via exec_new_vmspace <- exec_elf_imgact <- execve);
hardware is a dual P3 with SMP enabled, 512MB core, 2GB swap (total of two
partitions)  If this is important/unexpected, I'll try to reproduce it
with more info.

Cheers,

Chris.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Garance A Drosihn]

At 4:57 AM +1100 3/9/02, Bruce Evans wrote:
>I'm surprised that everyone hasn't complained about world breakage
>from this.  It has been broken for almost 2 weeks now.  Everything
>that goes near ntohl and has WARNS >= 2 fails to compile.  Without
>WARNS, the bug is reported as above, but a bogus version of __hton*
>is found in the library and only optimization of hton* is broken.

Well, I get compile-time warning messages when doing a buildworld
of current, but nothing actually breaks.  I do not do much of
anything fancy with resetting WARNS, so my guess is that the
"default buildworld settings" will not run into a show-stopping
error due to these loose ends.

I think part of it is that some things (like 'lpr' for instance)
were changed to use 'BDECFLAGS' instead of some compiler-specific
list of flags (in -stable lpr has '-Wall -Wnested-externs
-Wmissing-prototypes -Wno-unused -Wredundant-decls
-Wstrict-prototypes').

That probably sounds like a step up in warning level, except that
we also removed BDECFLAGS from /etc/defaults/make.conf.  In fact,
there is no /etc/defaults/make.conf in current, it was moved to
/usr/share/examples/etc/make.conf.  So I expect that most people
(including me) have effectively gone to compiling with zero special
CWARNFLAGS parameters for those modules.

I'll make a wild guess and say that it's possible that Bruce might
have some BDECFLAGS set in his /etc/make.conf, so he is probably
seeing more warning messages than the average person...

-- 
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Matthew Jacob]

And FWIW, alpha kernels on some Uniprocessor boxes freeze up.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Wilko Bulte]

On Fri, Mar 08, 2002 at 01:35:47PM -0800, Matthew Jacob wrote:
> 
> And FWIW, alpha kernels on some Uniprocessor boxes freeze up.

Yes. Or panic. See my posts earlier this week. I managed to get 
2 buildworlds without accidents, but all make release attempts either
paniced or froze.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Matthew Jacob]

Sorry- couldn't see your posts. Majordomo bounced my resubscribe request to
the list owner who seems to not to have gotten it.


On Fri, 8 Mar 2002, Wilko Bulte wrote:

> On Fri, Mar 08, 2002 at 01:35:47PM -0800, Matthew Jacob wrote:
> > 
> > And FWIW, alpha kernels on some Uniprocessor boxes freeze up.
> 
> Yes. Or panic. See my posts earlier this week. I managed to get 
> 2 buildworlds without accidents, but all make release attempts either
> paniced or froze.
> 
> -- 
> |   / o / /_  _   [EMAIL PROTECTED]
> |/|/ / / /(  (_)  Bulte   Arnhem, the Netherlands
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Garance A Drosihn]

>On Fri, 8 Mar 2002, Murray Stokely wrote:
>  >As discussed at BSDCon, the release engineers are committed
>  > to releasing a relatively stable snapshot of FreeBSD -CURRENT
>  > on or around April 1, 2002.

Will this release include some kind of bootable-install support
for any new hardware platforms, such as sparc64?  (this snapshot
is meant to be available as some kind of CD-package, right?)

-- 
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Mike Barcroft]

Joel Wilsson <[EMAIL PROTECTED]> writes:
> On Fri, Mar 08, 2002 at 08:59:53AM -0600, David W. Chapman Jr. wrote:
> > >As discussed at BSDCon, the release engineers are committed to
> > > releasing a relatively stable snapshot of FreeBSD -CURRENT on or
> > > around April 1, 2002.  Obviously, a lot of major components are still
> > > in progress, but a great deal of work has already been accomplished,
> > > and could benefit from the additional exposure that a polished
> > > snapshot with full package set and documentation will provide.
> > > 
> > I don't know if this is something worth making it the snapshot, but 
> > currently kde doesn't work due to binuntils update.  It may work now 
> > after the most recent binutils update, but we have to recompile kde 
> > to see that I believe, andkdelibs cannot be compiled
> > which builds kde-config which the rest of the kde meta-ports try to 
> > run.
> 
> It works if you don't use objprelink, and then change a bunch of files
> to include arpa/inet.h

htonl()/htons()/ntohl()/ntohs() can be defined by including
, , or  (the first two are
POSIX-required, the final one is temporary until the base system no
long requires it).  Previously these functions were leaked to all
sorts different headers.  Weak aliases exist for these functions so
even if software depended on, for instance ntohl() being prototyped
, this should not be fatal.

There's a few small issues with the prototypes which can lead to some
compiler diagnostics (this should be fixed by Sunday).

If someone can provide a compiler error and source file, I can
figure out what the problem is.

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Mike Barcroft]

[ Could we CC a few more lists?  I'm not sure everyone that uses
FreeBSD has read this yet. :) ]

David W. Chapman Jr. <[EMAIL PROTECTED]> writes:
> Its not related to libpng, I believe that has been fixed, but I 
> cannot tell for sure because kde cannot be compiled under -current.  
> I'm not the only one that is experiencing it either, here is what I 
> was told by Alan Eldridge <[EMAIL PROTECTED]>
> 
> On Tue, Mar 05, 2002 at 05:26:27PM -0600, David W. Chapman Jr. wrote:
> >When I try to build kdelibs2 I get the following under recent
> >-current builds
> >
> >,.deps/kextsock.pp -c kextsock.cpp  -fPIC -DPIC -o .libs/kextsock.o
> >kextsock.cpp: In method `struct kde_addrinfo *
> >KExtendedSocketLookup::results()'
> >:
> >kextsock.cpp:294: implicit declaration of function `int __htons(...)'
> >kextsock.cpp:353: implicit declaration of function `int __htonl(...)'

Hmm.  This should be non-fatal in any event, but which header does it
include to get it's htons() and htonl() prototypes?  ,
, or ?

> Yes. Recent changes to netinet/in.h have made it require the inclusion
> of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW, 
> each
> of these files must #include the other in order to work correctly.

This is almost completely bogus.  I recently saw a PR of similar
bogusness.

> As you  might guess, this is a less than desirable situation. A 
> #includes
> B and B #includes A is a very bad arrangement. However, unless both 
> files
> are overhauled, that is what will have to happen.

Hello?  I've been overhauling  (and ) for
over six months.  The new kernel endian functions complicated things
much more.

> In the meantime, you need to find every occurence of either of those
> files being included, and make sure the other is included as
> well. netinet/in.h needs to come first.

This is untrue.   can appear before  or
vice versa (remember to include  before ,
since  isn't a POSIX-2001 header yet).

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David W. Chapman Jr.]

> Hmm.  This should be non-fatal in any event, but which header does it
> include to get it's htons() and htonl() prototypes?  ,
> , or ?
>
> > Yes. Recent changes to netinet/in.h have made it require the inclusion
> > of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW,
> > each
> > of these files must #include the other in order to work correctly.

>From reading all the posts, I believe the solution has been to manually
modify the kde port to do this.

>
> This is almost completely bogus.  I recently saw a PR of similar
> bogusness.
>
This was most likely quoted from the same person who submitted the pr you
read.  I'm not sure how I can help you because I'm not a programmer, but I'd
be happy to boot into -current and give you any information you need if
there is actually a problem(I don't totally understand what it is at the
moment).


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Terry Lambert]

Garance A Drosihn wrote:
> >On Fri, 8 Mar 2002, Murray Stokely wrote:
> >  >As discussed at BSDCon, the release engineers are committed
> >  > to releasing a relatively stable snapshot of FreeBSD -CURRENT
> >  > on or around April 1, 2002.
> 
> Will this release include some kind of bootable-install support
> for any new hardware platforms, such as sparc64?  (this snapshot
> is meant to be available as some kind of CD-package, right?)

That was not planned until the second developer snapshot before
release, according to the discussion at the developer's summit
at BSDCon.

I thought someone was going to accumulate and post minutes for
that meeting?!?

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Robert Watson]

On Fri, 8 Mar 2002, Terry Lambert wrote:

> Garance A Drosihn wrote:
> > >On Fri, 8 Mar 2002, Murray Stokely wrote:
> > >  >As discussed at BSDCon, the release engineers are committed
> > >  > to releasing a relatively stable snapshot of FreeBSD -CURRENT
> > >  > on or around April 1, 2002.
> > 
> > Will this release include some kind of bootable-install support
> > for any new hardware platforms, such as sparc64?  (this snapshot
> > is meant to be available as some kind of CD-package, right?)
> 
> That was not planned until the second developer snapshot before release,
> according to the discussion at the developer's summit at BSDCon. 
> 
> I thought someone was going to accumulate and post minutes for that
> meeting?!? 

Yeah, we have extensive notes and a complete recording, I've just been
stalled on getting them out the door due to other priorities and lack of a
docs person wanting to docify them.  I'll post the text version sometime
in the next day or two, and we can let the docified version come later. 
Look for a post on sometime this weekend. 

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Andrew Gallatin]

Matthew Jacob writes:
 > 
 > And FWIW, alpha kernels on some Uniprocessor boxes freeze up.
 > 

I suggest reverting rev 1.61 of alpha/alpha/interrupt.c (eg, disable 
interrupt thread preemption).  I'm on the west coast right now, away
from my alphas, but I had several buildworlds complete last week with
ithread preemption disabled.

Drew

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Jake Burkholder]

Apparently, On Fri, Mar 08, 2002 at 05:33:28PM -0500,
Garance A Drosihn said words to the effect of;

> >On Fri, 8 Mar 2002, Murray Stokely wrote:
> >  >As discussed at BSDCon, the release engineers are committed
> >  > to releasing a relatively stable snapshot of FreeBSD -CURRENT
> >  > on or around April 1, 2002.
> 
> Will this release include some kind of bootable-install support
> for any new hardware platforms, such as sparc64?  (this snapshot
> is meant to be available as some kind of CD-package, right?)

Yes, absolutely.  I'm really excited that the sparc64 port is ready to be
part of this.  It will probably not be a regaular freebsd release, there
will be (already is) a bootable iso that has all the tools needed to install
a distribution from a tarball quickly and easily (the cd boots multi user).
There will be a self hosted toolchain which can be used to build a custom
kernel.  This can also be used to build userland and ports natively, but
make buildworld may not work.

I will be cutting another iso this weekend which fixes a couple problems
with the first one.  Anyone who has a sparc64 machine is invited to subscribe
to the freebsd-sparc mailing list and be testers for the first semi-official
fresbsd/sparc64 release.  .

Jake

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Matthew Jacob]

Yes, Peter also suggested this.

Alas, at some point over the last couple of days, something also broke so that
polled mailbox commands for ISP are now broken. Dunno why. *shrug*


On Fri, 8 Mar 2002, Andrew Gallatin wrote:

> 
> Matthew Jacob writes:
>  > 
>  > And FWIW, alpha kernels on some Uniprocessor boxes freeze up.
>  > 
> 
> I suggest reverting rev 1.61 of alpha/alpha/interrupt.c (eg, disable 
> interrupt thread preemption).  I'm on the west coast right now, away
> from my alphas, but I had several buildworlds complete last week with
> ithread preemption disabled.
> 
> Drew
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Terry Lambert]

Jake Burkholder wrote:
> > Will this release include some kind of bootable-install support
> > for any new hardware platforms, such as sparc64?  (this snapshot
> > is meant to be available as some kind of CD-package, right?)
> 
> Yes, absolutely.

Wow.

This is really impressive.

I thought it wasn't going to be available until the preview
just before the final release!

Good work!  Make Robert update his notes...

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Jake Burkholder]

Apparently, On Fri, Mar 08, 2002 at 04:12:47PM -0800,
Terry Lambert said words to the effect of;

> Jake Burkholder wrote:
> > > Will this release include some kind of bootable-install support
> > > for any new hardware platforms, such as sparc64?  (this snapshot
> > > is meant to be available as some kind of CD-package, right?)
> > 
> > Yes, absolutely.
> 
> Wow.
> 
> This is really impressive.
> 
> I thought it wasn't going to be available until the preview
> just before the final release!
> 
> Good work!  Make Robert update his notes...

Thanks.  Alot of this actually happened since the meeting  ;)

Jake

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Kris Kennaway]

On Fri, Mar 08, 2002 at 02:17:24AM -0800, Murray Stokely wrote:

>   To this end, we would like to request that commits for the next 7
> days to HEAD be made with special care.  -CURRENT is in pretty good
> shape right now, so we're not requiring approval for all commits.

Some of the 5.x package builds on bento are dying with SIGBUS in the
port compilation process, for example gnomelibs which is dying in the
configure script.  Apparently this is a widely experienced problem (a
workaround is to compile without optimization, but I don't want to do
that for the package builds unless I have to).

Is anyone looking into this?

Kris



msg35862/pgp0.pgp
Description: PGP signature

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Mike Barcroft]

David W. Chapman Jr. <[EMAIL PROTECTED]> writes:
> > Hmm.  This should be non-fatal in any event, but which header does it
> > include to get it's htons() and htonl() prototypes?  ,
> > , or ?
> >
> > > Yes. Recent changes to netinet/in.h have made it require the inclusion
> > > of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW,
> > > each
> > > of these files must #include the other in order to work correctly.
> 
> From reading all the posts, I believe the solution has been to manually
> modify the kde port to do this.

Maybe not.  I think missing prototypes might be fatal in C++.  If this
is the case, my new endian patch will fix this.  Try compiling KDE
after installing a world with the following patch applied:
http://people.FreeBSD.org/~mike/patches/endian-ng3.diff

I plan on committing this on Sunday.

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Dag-Erling Smorgrav]

Mike Barcroft <[EMAIL PROTECTED]> writes:
> Maybe not.  I think missing prototypes might be fatal in C++.

Yes.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David W. Chapman Jr.]

> Maybe not.  I think missing prototypes might be fatal in C++.  If this
> is the case, my new endian patch will fix this.  Try compiling KDE
> after installing a world with the following patch applied:
> http://people.FreeBSD.org/~mike/patches/endian-ng3.diff
> 
> I plan on committing this on Sunday.
> 
I don't know if its related to this patch, but I get this when I 
buildworld now

cc -O -pipe -march=k6 -DDES -Wall -Wformat   -Werror -Wall 
-Wno-uninitialized -W
non-const-format -Wno-format-extra-args -Werror  -c 
/usr/src/bin/ed/sub.c
cc -O -pipe -march=k6 -DDES -Wall -Wformat   -Werror -Wall 
-Wno-uninitialized -W
non-const-format -Wno-format-extra-args -Werror  -c 
/usr/src/bin/ed/undo.c
gzip -cn /usr/src/bin/ed/ed.1 > ed.1.gz
cc -O -pipe -march=k6 -DDES -Wall -Wformat   -Werror -Wall 
-Wno-uninitialized -W
non-const-format -Wno-format-extra-args -Werror   -static -o ed buf.o 
cbc.o glbl
.o io.o main.o re.o sub.o undo.o  -lcipher
cbc.o: In function `get_keyword':
cbc.o(.text+0x17d): undefined reference to `getpass'
*** Error code 1
1 error
*** Error code 2

-- 
David W. Chapman Jr.
[EMAIL PROTECTED]   Raintree Network Services, Inc. 
[EMAIL PROTECTED]   FreeBSD Committer 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Garance A Drosihn]

At 6:32 PM -0600 3/8/02, David W. Chapman Jr. wrote:
>  > Try compiling KDE after installing a world with the
>  > following patch applied:
>  > http://people.FreeBSD.org/~mike/patches/endian-ng3.diff
>>
>  > I plan on committing this on Sunday.
>
>I don't know if its related to this patch, but I get this
>when I buildworld now

I just did a complete buildworld + installworld with no
trouble, and I then added the above patch and did another
complete buildworld + installworld.  I had no problems with
either build.

Applying the above patch got rid of about 81 warning messages
in the buildworld process, and another 9 from buildkernel.
Applying the patch causes no new warning messages (for me,
with my kernel options, make options, on i386, etc etc).

-- 
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David W. Chapman Jr.]

> >I don't know if its related to this patch, but I get this
> >when I buildworld now
>
> I just did a complete buildworld + installworld with no
> trouble, and I then added the above patch and did another
> complete buildworld + installworld.  I had no problems with
> either build.
>
> Applying the above patch got rid of about 81 warning messages
> in the buildworld process, and another 9 from buildkernel.
> Applying the patch causes no new warning messages (for me,
> with my kernel options, make options, on i386, etc etc).
>
I wonder what's broken, I did a buildworld twice with the same result, I'll
try to cvsup tomorrow and see if its fixed, maybe I caught it between
commits.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Doug Rabson]

On Fri, 8 Mar 2002, Matthew Jacob wrote:

>
> And FWIW, alpha kernels on some Uniprocessor boxes freeze up.

I managed to panic my 4-cpu 4100 yesterday with a 'make -j8 buildworld'
I'm going to look at that today.

-- 
Doug Rabson Mail:  [EMAIL PROTECTED]
Phone: +44 20 8348 6160



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Chris Hedley]

On Fri, 8 Mar 2002, Chris Hedley wrote:
... about a crash ...

Just in case anyone needs to know, I had another couple of panics today
when trying to newfs_msdos /dev/fd0, seems something in readdisklabel
isn't too happy.

Chris.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David W. Chapman Jr.]

I'm able to compile kdelibs now, no problem as well as QT, but when I run
configure on kdebase it locks my system up.  I can switch terminals but
that's it.  It locks up on configure when detecting QT(I believe line 5612).
The first time it did this I decided that was because I need to rebuild QT,
so I did that, but it still locks up.  Is anyone else seeing this with a
very recent -current?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[John Baldwin]

On 08-Mar-02 Wilko Bulte wrote:
> On Fri, Mar 08, 2002 at 01:35:47PM -0800, Matthew Jacob wrote:
>> 
>> And FWIW, alpha kernels on some Uniprocessor boxes freeze up.
> 
> Yes. Or panic. See my posts earlier this week. I managed to get 
> 2 buildworlds without accidents, but all make release attempts either
> paniced or froze.

We should turn preemption back off again. :-/

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Peter Wemm]

Murray Stokely wrote:

>   On March 15, a RELENG_5_0_DP1 branch will be created in CVS for
> final release polishing.  This will allow us to provide translated
> release notes, sync up sysinstall and the package set, bump version
> numbers, and tweak default diagnostic settings without further
> impacting -CURRENT developers.  Commits to this branch will require
> re@ approval.

Actually, with my CVS hat on, I have a *huge* problem with this.

We have a large number of "temporary" repo copies in place that are to
be deleted (ie: rm -rf) soon.  This was with the plan that there would
be *NO* persistant branches and that it would be rm'ed long before the
RELENG_5 branch began.

I had a quick look and I immediately found 55MB of duplicated repo files.
That's over 5% of the repo right now.

I want to know what expectations people have by calling this a
"RELENG_5_XX" branch..  Given that this stuff is going to be rm'ed within a
month, that will break RELENG_5_DP1 when that happens.  People will no
longer be able to cvsup or check out -r RELENG_5_DP1 and have it build.
Specifically, gcc and gdb will not build.

If this is going to be a "static" release (calling it RELENG_5_anything is
a mistake IMHO) then this isn't a big deal.  But if people are expecting
it to have ongoing secirity fixes etc like we do with RELENG_4_5 etc then
we have a problem, because it cannot last very long at all.

Accordingly, I would much prefer that the branch (if we have to have it)
would be called SNAPSHOT_5_DP1 or soemthing, so that the "RELENG_" prefix
doesn't unduely raise expectations that it will keep working, or move the
DP1 release elsewhere if we want it to remain cvsup'able long term.

The other option is to do some hackery after the branch is set down so that
the *.291 and *.295 temporary copies do not exist in the branch, and
accordingly wont get broken when they are cvs rm -rf'ed.  (Hmm, this might
be the best option from a cvs perspective, if people dont mind the fact that
-current and DP1 will have some files in different places..)

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Bruce A. Mah]

[Trimming Cc list a little bit]

If memory serves me right, Peter Wemm wrote:

> Actually, with my CVS hat on, I have a *huge* problem with this.

In the future, if you see such huge problems come up, a little more
advance notice might be nice.  :-(

> We have a large number of "temporary" repo copies in place that are to
> be deleted (ie: rm -rf) soon.  This was with the plan that there would
> be *NO* persistant branches and that it would be rm'ed long before the
> RELENG_5 branch began.

Is there more to this plan?  This is news to me and I would like to get 
up to speed.

> I had a quick look and I immediately found 55MB of duplicated repo files.
> That's over 5% of the repo right now.
> 
> I want to know what expectations people have by calling this a
> "RELENG_5_XX" branch..  Given that this stuff is going to be rm'ed within a
> month, that will break RELENG_5_DP1 when that happens.  People will no
> longer be able to cvsup or check out -r RELENG_5_DP1 and have it build.
> Specifically, gcc and gdb will not build.
> 
> If this is going to be a "static" release (calling it RELENG_5_anything is
> a mistake IMHO) then this isn't a big deal.  But if people are expecting
> it to have ongoing secirity fixes etc like we do with RELENG_4_5 etc then
> we have a problem, because it cannot last very long at all.

Differences of opinion on naming aside...the branch isn't supposed to
last long at all.  The point is to provide a slightly polished snapshot
to the wider developer community.  We can't do the QA/releng work on
HEAD without calling for a code freeze (which we early on decided that
we would *not* do).  Since it's not a formal release, we won't be doing 
security fixes, etc.

I can't imagine why anyone would expect to cvsup this thing at some
point in the distant future, especially after 5.0-DP2 and 5.0-RELEASE.
Just thinking off the top of my head, having it break soon after 5.0-DP1
might not be fatal, as long as we have the CDROM and FTP areas still 
intact.

Did you have a definite date for the rm-ing in mind?

Thanks,

Bruce.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Dag-Erling Smorgrav]

"Bruce A. Mah" <[EMAIL PROTECTED]> writes:
> Differences of opinion on naming aside...the branch isn't supposed to
> last long at all.  The point is to provide a slightly polished snapshot
> to the wider developer community.  We can't do the QA/releng work on
> HEAD without calling for a code freeze (which we early on decided that
> we would *not* do).

Then you don't need a branch, you just need a simple tag, and you can
slide it forward if something needs fixing, and remove it after
rolling and shipping the snapshot.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT( "1 week Feature Slush" )

[Doug Barton]

On Thu, 14 Mar 2002, Bruce A. Mah wrote:

> I can't imagine why anyone would expect to cvsup this thing at some
> point in the distant future

Rule number one of release engineering... user's will do all kinds
of wacky stuff that you would never expect them to do, and complain
bitterly when it doesn't work. :)

-- 
   "We have known freedom's price. We have shown freedom's power.
  And in this great conflict, ...  we will see freedom's victory."
- George W. Bush, President of the United States
  State of the Union, January 28, 2002

 Do YOU Yahoo!?



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Robert Watson]

On 15 Mar 2002, Dag-Erling Smorgrav wrote:

> "Bruce A. Mah" <[EMAIL PROTECTED]> writes:
> > Differences of opinion on naming aside...the branch isn't supposed to
> > last long at all.  The point is to provide a slightly polished snapshot
> > to the wider developer community.  We can't do the QA/releng work on
> > HEAD without calling for a code freeze (which we early on decided that
> > we would *not* do).
> 
> Then you don't need a branch, you just need a simple tag, and you can
> slide it forward if something needs fixing, and remove it after rolling
> and shipping the snapshot. 

No, in this case that doesn't help.  What we want is to grab a stable
moment, then to allow development to continue.  However, we may then want
to tweak that stable moment without impinging on development, which
requires a branch.  The QA/releng work requires us to modify the stuff
being released following the branchpoint.

It's worth noting, BTW, that originally the release engineering team
planned to use Perforce for this to avoid the branch issue entirely,
minimize impact on the main tree, etc, but decided not to due to the high
volume of complaints on the topic.

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Dag-Erling Smorgrav]

Robert Watson <[EMAIL PROTECTED]> writes:
> It's worth noting, BTW, that originally the release engineering team
> planned to use Perforce for this to avoid the branch issue entirely,
> minimize impact on the main tree, etc, but decided not to due to the high
> volume of complaints on the topic.

If it allows you to do your job better and quicker, use it.  I was
actually going to suggest it myself, but I didn't think anybody would
take me seriously...

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[David O'Brien]

On Thu, Mar 14, 2002 at 09:36:30PM -0500, Robert Watson wrote:
> It's worth noting, BTW, that originally the release engineering team
> planned to use Perforce for this to avoid the branch issue entirely,
> minimize impact on the main tree, etc, but decided not to due to the high
> volume of complaints on the topic.

You would get no complaints from me.  I think this would be a very good
use of Perforce.  In the past the WC -CURRENT snapshots were not tagged
or branched w/in CVS.  I don't see that the requirement to do so has been
demanded.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Nate Williams]

> > "Bruce A. Mah" <[EMAIL PROTECTED]> writes:
> > > Differences of opinion on naming aside...the branch isn't supposed to
> > > last long at all.  The point is to provide a slightly polished snapshot
> > > to the wider developer community.  We can't do the QA/releng work on
> > > HEAD without calling for a code freeze (which we early on decided that
> > > we would *not* do).
> > 
> > Then you don't need a branch, you just need a simple tag, and you can
> > slide it forward if something needs fixing, and remove it after rolling
> > and shipping the snapshot. 
> 
> No, in this case that doesn't help.  What we want is to grab a stable
> moment, then to allow development to continue.  However, we may then want
> to tweak that stable moment without impinging on development, which
> requires a branch.

Not necessarily.  What we've done at work is *NOT* create a branch
unless absolutely necessary.  The only time a branch is requires is *if*
a file changes out from underneath the developer *AND* it that files
needs modifying but *must not* contain that same change.

We play it by ear, since in almost all cases, the change can be made to
any necessary file(s) and the file(s) updated by hand.  Otherwise, often
the change that happens are necessary to merge into the build, so we do
an update.

Only in very rare cases do we run into a problem where we have to create
a branch.  In that case, the developer responsible for the release
creates a branch from his checked out tree (there's no law against
creating a branch from sources that are older than the HEAD), and then
makes any necessary changes.

It's *not* that hard to do.  Otherwise, once the release is made using
the files, a point-tag is laid down and we've saved the hassle of the
branch.

> The QA/releng work requires us to modify the stuff being released
> following the branchpoint.

See above.



Nate

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Murray Stokely]

On Fri, Mar 15, 2002 at 03:32:00AM +0100, Dag-Erling Smorgrav wrote:
> "Bruce A. Mah" <[EMAIL PROTECTED]> writes:
> > Differences of opinion on naming aside...the branch isn't supposed to
> > last long at all.  The point is to provide a slightly polished snapshot
> > to the wider developer community.  We can't do the QA/releng work on
> > HEAD without calling for a code freeze (which we early on decided that
> > we would *not* do).
> 
> Then you don't need a branch, you just need a simple tag, and you can
> slide it forward if something needs fixing, and remove it after
> rolling and shipping the snapshot.

  Sliding tags around at the request of hundreds of different
developers making thousands of changes to -CURRENT over that time
period is not very appealing.  However, all of our other options are
rapidly being shot down as well.  Peter raises some valid concerns
about the pains that branching CVS will cause.  They would have been
much more helpful if voiced to re@ a week ago, but that's another
issue.

  At the very least a tag is going down in approximately 24 hours.

- Murray



msg36135/pgp0.pgp
Description: PGP signature

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Murray Stokely]

On Thu, Mar 14, 2002 at 04:40:08PM -0800, Peter Wemm wrote:
> If this is going to be a "static" release (calling it RELENG_5_anything is
> a mistake IMHO) then this isn't a big deal.  But if people are expecting
> it to have ongoing secirity fixes etc like we do with RELENG_4_5 etc then
> we have a problem, because it cannot last very long at all.

   Ongoing security fixes for a SNAPSHOT ???  No, that is definitely
not the case.

> Accordingly, I would much prefer that the branch (if we have to have it)
> would be called SNAPSHOT_5_DP1 or soemthing, so that the "RELENG_" prefix
> doesn't unduely raise expectations that it will keep working, or move the
> DP1 release elsewhere if we want it to remain cvsup'able long term.

  I think that the huge warning signs all over the release
documentation will do a lot more to set the expectations that the name
of a CVS tag, but just to be sure I suppose we can keep the RELENG
namespace for official releases.  Your proposed name change works for
me.

- Murray



msg36136/pgp0.pgp
Description: PGP signature

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

[Robert Watson]

On Thu, 14 Mar 2002, Nate Williams wrote:

> Only in very rare cases do we run into a problem where we have to create
> a branch.  In that case, the developer responsible for the release
> creates a branch from his checked out tree (there's no law against
> creating a branch from sources that are older than the HEAD), and then
> makes any necessary changes. 

It's worth noting that the rationale for the branch was that we *want*
-CURRENT development to continue at a wild and merry pace, and *expect*
that it will.  Once the branch occurs, Jeff is free to replace the kernel
memory allocator, etc.  Local tweaks on the branch may include backing out
some of the more recent changes to locking (the VM changes, for example --
there have been some reports of stability problems from Alfred).  I.e.,
there is a specific development process goal to be accomplished using the
branch.

My feeling is that at this point, we probably should just use Perforce due
to limitations in CVS.

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to-CURRENT ( "1 week Feature Slush" )

[Garance A Drosihn]

At 2:17 PM -0500 3/15/02, Robert Watson wrote:
>My feeling is that at this point, we probably should just use
>Perforce due to limitations in CVS.

This seems fine to me.  I am uneasy about perforce in cases
where someone is developing something which is *meant* to be
merged back into the main branch, and anyone interested in
that change is told "just check the P4 repository".  That is
not what is happening here.

I would not *push* to have this done in P4, but I certainly
do not mind if the RE team wants to handle it that way.

-- 
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message