Re: stat(1) (was Re: mergemaster(8) broken -- uses Perl
Bakul Shah wrote: the trick nicely (but is too ``complicated'', and I'd still like having a tool that allows userland to call stat/fstat(2): I'm currently testing a buildworld prior to importing NetBSD's stat(1) into the tree. Once that's done, if you have suggestions for improvements I'm sure that they would be interested. I'll be happy to work with you on adding useful bits to it in our tree as well. You can see what I'm importing at http://cvsweb.netbsd.org/bsdweb.cgi/basesrc/usr.bin/stat/ My reasons for choosing to import this version are the obvious benefits of working closely with the NetBSD folks, as well as the fact that it has a large number of features, compiles cleanly on our system (even with WARNS=2), etc. Doug -- 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: Safe to go to -CURRENT?
On 05 Jun 2002 08:46:59 GMT, Christopher Nehren wrote: I've been monitoring the -CURRENT mailing list for about a day or two, and haven't seen anything that's really broken (except for GCC 3.x, which I don't use anyway). So, is it safe to upgrade to -CURRENT yet? TIA for the info, Chris There are still issues with the C++ compiler in the base system that make building X and some other C++ ports tricky. If you use a lot of X applications, you might want to hold back if you're looking for a smooth ride. The base system itself seems pretty stable, though. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: stat(1) (was Re: mergemaster(8) broken -- uses Perl
On Wed, 05 Jun 2002 23:58:14 MST, Doug Barton wrote: I'm currently testing a buildworld prior to importing NetBSD's stat(1) into the tree. Once that's done, if you have suggestions for improvements I'm sure that they would be interested. I'll be happy to work with you on adding useful bits to it in our tree as well. You can see what I'm importing at http://cvsweb.netbsd.org/bsdweb.cgi/basesrc/usr.bin/stat/ I really like the fact that you're trying to maintain NetBSD compatibility with tools imported from NetBSD. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld error in gnu/lib/libstdc++
On Wed, 05 Jun 2002 15:36:04 +0200, Andrea Campi wrote: I've been seeing a compile error in gnu/lib/libstdc++ for days now. Since no one else reported it (not even tinderbox) I can only wonder what's up, and expecially how to get out of this. Show the compile error. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld error in gnu/lib/libstdc++
On Thu, Jun 06, 2002 at 11:05:54AM +0200, Sheldon Hearn wrote: On Wed, 05 Jun 2002 15:36:04 +0200, Andrea Campi wrote: I've been seeing a compile error in gnu/lib/libstdc++ for days now. Since no one else reported it (not even tinderbox) I can only wonder what's up, and expecially how to get out of this. Show the compile error. Grrr... of course I meant to attach the error, as I wrote, but I didn't OK, it's in the attachment! Bye, Andrea -- Actually, Microsoft is sort of a mixture between the Borg and the Ferengi. [...] === gnu/lib/libreadline/readline === gnu/lib/libreadline/readline/doc === gnu/lib/libstdc++ c++ -O -pipe -march=pentiumpro -DIN_GLIBCPP_V3 -DHAVE_CONFIG_H -I/usr/src/gnu/lib/libstdc++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc -fno-implicit-templates -ffunction-sections -fdata-sections -Wno-deprecated -c /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/globals.cc -o globals.o In file included from /usr/obj/usr/src/i386/usr/include/g++/iosfwd:46, from /usr/obj/usr/src/i386/usr/include/g++/ios:44, from /usr/obj/usr/src/i386/usr/include/g++/istream:44, from /usr/obj/usr/src/i386/usr/include/g++/fstream:45, from /usr/src/contrib/libstdc++/src/globals.cc:30: /usr/obj/usr/src/i386/usr/include/g++/bits/fpos.h:40:50: bits/std_cwchar.h: No such file or directory In file included from /usr/obj/usr/src/i386/usr/include/g++/iosfwd:46, from /usr/obj/usr/src/i386/usr/include/g++/ios:44, from /usr/obj/usr/src/i386/usr/include/g++/istream:44, from /usr/obj/usr/src/i386/usr/include/g++/fstream:45, from /usr/src/contrib/libstdc++/src/globals.cc:30: /usr/obj/usr/src/i386/usr/include/g++/bits/fpos.h:112: `mbstate_t' was not declared in this scope /usr/obj/usr/src/i386/usr/include/g++/bits/fpos.h:112: template argument 1 is invalid In file included from /usr/obj/usr/src/i386/usr/include/g++/ios:46, from /usr/obj/usr/src/i386/usr/include/g++/istream:44, from /usr/obj/usr/src/i386/usr/include/g++/fstream:45, from /usr/src/contrib/libstdc++/src/globals.cc:30: /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:39:63: bits/std_cstring.h: No such file or directory In file included from /usr/obj/usr/src/i386/usr/include/g++/ios:46, from /usr/obj/usr/src/i386/usr/include/g++/istream:44, from /usr/obj/usr/src/i386/usr/include/g++/fstream:45, from /usr/src/contrib/libstdc++/src/globals.cc:30: /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:55: syntax error before `;' token /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:138: syntax error before `;' token /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h: In static member function `static int std::char_traitschar::compare(const char*, const char*, unsigned int)': /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:154: `memcmp' undeclared (first use this function) /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:154: (Each undeclared identifier is reported only once for each function it appears in.) /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h: In static member function `static size_t std::char_traitschar::length(const char*)': /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:158: `strlen' undeclared (first use this function) /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h: In static member function `static const char* std::char_traitschar::find(const char*, unsigned int, const char)': /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:162: `memchr' undeclared (first use this function) /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h: In static member function `static char* std::char_traitschar::move(char*, const char*, unsigned int)': /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:166: `memmove' undeclared (first use this function) /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h: In static member function `static char* std::char_traitschar::copy(char*, const char*, unsigned int)': /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:170: `memcpy' undeclared (first use this function) /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h: In static member function `static char* std::char_traitschar::assign(char*, unsigned int, char)': /usr/obj/usr/src/i386/usr/include/g++/bits/char_traits.h:174: `memset' undeclared (first use this function) In file included from /usr/obj/usr/src/i386/usr/include/g++/ios:48, from /usr/obj/usr/src/i386/usr/include/g++/istream:44, from /usr/obj/usr/src/i386/usr/include/g++/fstream:45, from /usr/src/contrib/libstdc++/src/globals.cc:30:
Re: Perl script rewrite (/usr/bin/mmroff)
is someone currently converting /usr/bin/mmroff from perl to C ? Nope. If no one is working on it, i'm willing to do it. You have it! Thanks! :-) 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: buildworld failure in libfetch
On Wed, 05 Jun 2002 16:44:55 CST, Scott Long wrote: Ok, I finally feel the need to speak up here. DES, FREEFALL CVS IS NOT THE PLACE TO PUT EXPERIMENTAL CODE THAT BREAKS WORLD! PERIOD! Don't give me any crap about It's -current, you should expect breakage. You are abusing this disclaimer far more than it was ever meant for. Breaking world used to be a very humiliating event for committers. You, however, break it on a consistent basis. What the F*CK? Yes, others have broken world before you, and others will break it after you, but you are abusing the standards of the project. I think you went a little over the top with this message. If you'd taken a moment to calm down and limited yourself to presenting an emotion-free complaint, you'd be in a much better position to expect a positive result. Yes, DES broke the world build. Yes, more / better testing on his part could have avoided the breakage. Still, it's seldom useful to come on so strong. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
rc.d boot scripts are ready
Ok folks, I have our current rc.* scripts ported to the NetBSD framework. Preliminary testing says it's good to go, so consider this an official call for testers. Gordon has indicated he is ready to start committing it soon. I ask that people start testing it out before he does so. That will enable me to get any remaining bugs fixed before it hits the tree. Once you download and follow the directions at: http://home.pacbell.net/makonnen/rcng.html you can enable it by including rc_ng=YES in your /etc/rc.conf. If you experience any breakage please let me know so I can fix it. I'd appreciate it if people with the appropriate setups especially test the following: ATM ipfilter amd Any comments, constructive criticism welcome. Cheers, Mike Makonnen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rc.d boot scripts are ready
[ forgive this breach of net-ettiquette, but this should probably be given a wider audience] On Thu, 06 Jun 2002 05:01:18 -0600 Mike Makonnen [EMAIL PROTECTED] wrote: Ok folks, I have our current rc.* scripts ported to the NetBSD framework. Preliminary testing says it's good to go, so consider this an official call for testers. Gordon has indicated he is ready to start committing it soon. I ask that people start testing it out before he does so. That will enable me to get any remaining bugs fixed before it hits the tree. Once you download and follow the directions at: http://home.pacbell.net/makonnen/rcng.html you can enable it by including rc_ng=YES in your /etc/rc.conf. If you experience any breakage please let me know so I can fix it. I'd appreciate it if people with the appropriate setups especially test the following: ATM ipfilter amd Any comments, constructive criticism welcome. Cheers, Mike Makonnen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Panic in softdep_fsync() while running VMWare in background
Hi,
I get this panic sometimes when VMWare is executing in the background
(iconified). It can take a while (a couple of hours) until it happens.
The panic string says buffer not busy, but that seems to be fallout of a
second panic during the panic. The first one seems to be caused by a
trap in softdep_fsync().
Unfortunately it looks like my line numbers are wrong. This is a GCC
3.1 kernel, -current CVSupped on May 17 22:24 GMT+2. I boot kernel and
use kernel.debug only for looking at the dump. These two should be
identical except for the symbol table, right? Or did GCC 3.1 break this
assumption?
Any clue what is causing the panic? Anything else I could provide from
the dump?
--
Regards,
Georg.
(kgdb) where
#0 0xc01fa1a4 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353
#1 0xc01fa7d1 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:353
#2 0xc01fa9dd in panic (fmt=0xc03aab0b bwrite: buffer is not busy???)
at /usr/src/sys/kern/kern_shutdown.c:353
#3 0xc0240eac in bwrite (bp=0xd287585c) at /usr/src/sys/kern/vfs_bio.c:1367
#4 0xc0242635 in vfs_bio_awrite (bp=0xd287585c)
at /usr/src/sys/kern/vfs_bio.c:1367
#5 0xc01c8a67 in spec_fsync (ap=0xe3d88a24)
at /usr/src/sys/fs/specfs/spec_vnops.c:849
#6 0xc01c844e in spec_vnoperate (ap=0xe3d88a24)
at /usr/src/sys/fs/specfs/spec_vnops.c:849
#7 0xc030b72a in VOP_FSYNC (vp=0xe0e03000, cred=0xd277ff00, waitfor=2,
td=0xc03ea5a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:810
#8 0xc030abc1 in ffs_sync (mp=0xe0c25600, waitfor=2, cred=0xd277ff00,
td=0xc03ea5a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:810
#9 0xc025424b in sync (td=0xc03ea5a0, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:640
#10 0xc01fa2ab in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:353
#11 0xc01fa9dd in panic (fmt=0xc03c70de %s)
at /usr/src/sys/kern/kern_shutdown.c:353
#12 0xc036d714 in trap_fatal (frame=0xe3d88c0c, eva=1845524107)
at /usr/src/sys/i386/i386/trap.c:652
#13 0xc036d34b in trap_pfault (frame=0xe3d88c0c, usermode=0, eva=1845524107)
at /usr/src/sys/i386/i386/trap.c:652
#14 0xc036cd34 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16,
tf_edi = 165662208, tf_esi = 0, tf_ebp = -472347472,
tf_isp = -472347592, tf_ebx = 24, tf_edx = 1845524079, tf_ecx = 4,
tf_eax = -472347496, tf_trapno = 12, tf_err = 0, tf_eip = -1070570113,
tf_cs = 8, tf_eflags = 66182, tf_esp = -1069904279, tf_ss = 843472})
at /usr/src/sys/i386/i386/trap.c:652
#15 0xc030657f in softdep_fsync (vp=0xe42f9c30)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:4603
#16 0xc0258185 in fsync (td=0xe3d7a414, uap=0xe3d88cf8)
at /usr/src/sys/kern/vfs_syscalls.c:640
#17 0xc036da82 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 1342242863,
tf_edi = 165662208, tf_esi = 0, tf_ebp = -1077944332,
tf_isp = -472347276, tf_ebx = 24, tf_edx = 24, tf_ecx = 3, tf_eax = 118,
tf_trapno = 22, tf_err = 2, tf_eip = 685504173, tf_cs = 31,
tf_eflags = 514, tf_esp = -1077944352, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:652
#18 0xc035c67d in syscall_with_err_pushed () at /var/tmp//ccqhs5l0.s:128
#19 0x83cccfc in ?? ()
#20 0x83e44d2 in ?? ()
#21 0x83dd07e in ?? ()
#22 0x82cdedb in ?? ()
#23 0x28b9b8ef in ?? ()
#24 0x82bd3bc in ?? ()
#25 0x82bfdc5 in ?? ()
#26 0x28d2c1eb in ?? ()
(kgdb) frame 15
#15 0xc030657f in softdep_fsync (vp=0xe42f9c30)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:4603
4603}
(kgdb) l
4598vp-v_rdev-si_mountpoint !VOP_ISLOCKED(vp, NULL)
4599(error = VFS_SYNC(vp-v_rdev-si_mountpoint, MNT_WAIT, ap-a_cred,
4600 ap-a_td)) != 0)
4601return (error);
4602return (0);
4603}
4604
4605/*
4606 * Flush the dependencies associated with an inodedep.
4607 * Called with splbio blocked.
(kgdb)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Safe to go to -CURRENT?
÷ Thu, 06.06.2002, × 12:54, Sheldon Hearn ÎÁÐÉÓÁÌ: I've been monitoring the -CURRENT mailing list for about a day or two, and haven't seen anything that's really broken (except for GCC 3.x, which I don't use anyway). So, is it safe to upgrade to -CURRENT yet? TIA for the info, Chris There are still issues with the C++ compiler in the base system that make building X and some other C++ ports tricky. If you use a lot of X applications, you might want to hold back if you're looking for a smooth ride. The base system itself seems pretty stable, though. Not sure, yesterdays kernel give me panic somewhere about ufsdir. Week-old kernel work very good. Turning off softupdates and doing fsck not in background not helps. I will fill PR just after connecting serial console. Ciao, Sheldon. -- Vladimir B. Grebenschikov [EMAIL PROTECTED], SWsoft, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Perl script rewrite (/usr/bin/mmroff)
On Thu, Jun 06, 2002 at 10:14:29AM +0100, Mark Murray wrote: is someone currently converting /usr/bin/mmroff from perl to C ? IMO, if something is best written in Perl, there is nothing wrong with leaving it in Perl. Our current setup handles this cleanly: bash$ mmroff perl: Perl is not installed, try 'pkg_add -r perl' mmroff isn't needed in building the system, nor is it a common command (as I never knew it existed until this email). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump on current broken -- master/slave protocol botched
On Wed, Jun 05, 2002 at 08:01:54PM -0700, Manfred Antar wrote: I have been using the following command to dump for months with no problem: dump 0fua /dev/nsa0 /dev/da0s1a for the past few weeks I get this: (bin)504}dump 0fua /dev/nsa0 /dev/da0s1a DUMP: Date of this level 0 dump: Wed Jun 5 19:54:04 2002 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da0s1a (/) to /dev/nsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 67590 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: master/slave protocol botched. DUMP: The ENTIRE dump is aborted. I am seeing this also. :-( Is your world kernel in sync. I must admit my kernel is May 17 (been avoiding some suspicious problems in SMP kernels); but world is Jun 3rd. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
The great perl rewrite - progress report
/usr/sbin/sysinstall* - fix - * /usr/bin/afmtodit Kyle Martin [EMAIL PROTECTED] - redo - * /usr/bin/mmroff Lester A Mesa [EMAIL PROTECTED] - redo - * /usr/bin/sockstat des - redo - * /usr/bin/whereissheldonh - redo - * /usr/sbin/adduser Mike Makonnen [EMAIL PROTECTED] - redo - * /usr/sbin/rmuserMike Makonnen [EMAIL PROTECTED] - redo - * /usr/sbin/kbdmapJonathan Belson [EMAIL PROTECTED] - redo - * /usr/sbin/vidfont Jonathan Belson [EMAIL PROTECTED] - redo - * /usr/sbin/mergemaster dougb(?) - fix - * /usr/sbin/pkg_version reg - redo - ready(?) /usr/bin/catman John Rochester [EMAIL PROTECTED] - redo - done /usr/bin/makewhatis John Rochester [EMAIL PROTECTED] - redo - done /usr/sbin/pkg_updatepaul - del - done /usr/sbin/scriptdumpume - del - done /usr/sbin/spkrtest Riccardo Torrini [EMAIL PROTECTED] - redo - done release/scripts/*.plru - redo - done etc/periodic/* keramida - fix - done Key - redo == to be rewritten fix == to have perl usage removed/redone del == to be deleted ready == work done, just waiting for commit. done == completed -- 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
cvsup failure -current/src/contrib/gcc/#cvs.cvsup-NNN.M: Cannot create
John, folks, I've been off of -current for a few days (two ISP failures) so I don't have -really-current-list-clue for this. cvsup for -stable completed OK, cvsup for -current failed in gcc, with a Cannot create: Permission denied error for its own logging files. Clue on the back of a matchbook please. Eric To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing perl usage from mergemaster
On Wed, Jun 05, 2002 at 03:27:47PM -0700, Doug Barton wrote: On Thu, 6 Jun 2002, Giorgos Keramidas wrote: Hello dougb all, Here's a patch that removes all trails of Perl usage from mergemaster. Your work looks good, but I wish you'd asked before embarking on it. My current plan is actually to import netbsd's stat(1), which will solve this Doug, mergemaster has been broken for almost a month now due to its use of perl. This is tool long for such an important tool. I would like to commit this patch now as a band-aid solution -- with full expectation you will back it out once stat(1) is ready. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Safe to go to -CURRENT?
On Thu, Jun 06, 2002 at 10:54:15AM +0200, Sheldon Hearn wrote: I've been monitoring the -CURRENT mailing list for about a day or two, and haven't seen anything that's really broken (except for GCC 3.x, which I don't use anyway). So, is it safe to upgrade to -CURRENT yet? TIA for the info, Chris There are still issues with the C++ compiler in the base system that make building X and some other C++ ports tricky. There is no issue with the C++ compiler. There is issue with the X source that uses depreciated features. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Safe to go to -CURRENT?
On Wed, Jun 05, 2002 at 08:46:59AM +, Christopher Nehren wrote: I've been monitoring the -CURRENT mailing list for about a day or two, and haven't seen anything that's really broken (except for GCC 3.x, which I don't use anyway). So, is it safe to upgrade to -CURRENT yet? TIA for the info, You use C to rebuild your system -- so I would say you _do_ use(will) use GCC 3.x. The C compiler has been fine since day 1. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Buildworld errors caused by libfetch.so
[CC'ed to des@] Hi all. I am experiencing buildworld errors caused by the latest libfetch.so. The CVSUP source is just a couple of minutes old. Thanks. -- Hiten Pandya http://storm.uk.FreeBSD.org/~hiten Finger [EMAIL PROTECTED] for PGP public key -- 4FB9 C4A9 4925 CF97 9BF3 ADDA 861D 5DBD E4E3 03C3 cc -O -save-temps -march=pentiumpro -I/data/dev/src/usr.sbin/pkg_install/add/../lib -Werror -Wall -Wno-uninitialized -o pkg_add main.o perform.o futil.o extract.o /c1/obj/data/dev/src/usr.sbin/pkg_install/add/../lib/libinstall.a -lfetch -lmd /usr/lib/libfetch.so: undefined reference to `SSL_set_fd' /usr/lib/libfetch.so: undefined reference to `X509_NAME_oneline' /usr/lib/libfetch.so: undefined reference to `SSL_read' /usr/lib/libfetch.so: undefined reference to `SSL_new' /usr/lib/libfetch.so: undefined reference to `SSL_CTX_new' /usr/lib/libfetch.so: undefined reference to `SSL_library_init' /usr/lib/libfetch.so: undefined reference to `ERR_print_errors_fp' /usr/lib/libfetch.so: undefined reference to `SSL_load_error_strings' /usr/lib/libfetch.so: undefined reference to `SSL_CIPHER_get_name' /usr/lib/libfetch.so: undefined reference to `SSLv23_client_method' /usr/lib/libfetch.so: undefined reference to `X509_get_subject_name' /usr/lib/libfetch.so: undefined reference to `SSL_get_current_cipher' /usr/lib/libfetch.so: undefined reference to `SSL_connect' /usr/lib/libfetch.so: undefined reference to `X509_get_issuer_name' /usr/lib/libfetch.so: undefined reference to `SSL_get_peer_certificate' /usr/lib/libfetch.so: undefined reference to `SSL_write' *** Error code 1 Stop in /data/dev/src/usr.sbin/pkg_install/add. msg39262/pgp0.pgp Description: PGP signature
Re: The great perl rewrite - progress report
Mark Murray [EMAIL PROTECTED] writes: /usr/bin/sockstat des - redo - * Done, but depends on other changes that aren't ready to be committed yet. I expect to commit the whole shebang this weekend or early next week. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Please test the UFS2 patch!
Right you are sir, seems I had another patch which got mixed up there. I've updated the version of the patch on: http://phk.freebsd.dk/patch/ufs2.patch Poul-Henning In message [EMAIL PROTECTED], Christopher Sharp writes: Hello, The kernel build with the patch applied fails with this message: make: don't know how to make /usr/src/sys/fs/devfs/devfs_rule.c. Stop It seems like this file was forgotten in the patch ... - Christopher Sharp -- Any time things appear to be going better, you have overlooked something. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The great perl rewrite - progress report
On Thu, Jun 06, 2002 at 05:31:12PM +0100, Mark Murray wrote: /usr/sbin/sysinstall * - fix - * What part of this uses perl?? Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: My postgresql7 not working for new gcc
I do beleive the OpenSSL library has moved to a new default location. I could be wrong. - aarong -- ___ Download the free Opera browser at http://www.opera.com/ Powered by Outblaze To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Buildworld errors caused by libfetch.so
Hiten Pandya [EMAIL PROTECTED] writes: I am experiencing buildworld errors caused by the latest libfetch.so. The CVSUP source is just a couple of minutes old. re-cvsup and rebuild. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing perl usage from mergemaster
Ok, I've imported stat(1) and modified mergemaster to use it instead. For now, I have simply disabled use of the user's umask for mode setting so that I could get the non-perl version in the tree asap. I will look at Giorgos' excellent patch and steal bits from it so that I can add that feature back. Once again, sorry for the delay. -- 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
Add a Makefile.user on /usr/src and /usr/ports
To support fancy user and they own targets would be nice an
infrastructure that check and (if it exist) include a file
(named Makefile.user or .local or similar) with personal
targets either under /usr/src than /usr/ports.
This can save a lot of typing building various things (for
example timing build phase or saving logs) only migrating
this file from a machine to another.
I was able to patch /usr/src/Makefile and /usr/ports/Makefile
myself, any comment will be appreciated (even negative ones).
TIA,
Riccardo.
-[ /usr/src ]-
# diff -u Makefile.orig Makefile
--- Makefile.orig Mon Jun 3 21:33:16 2002
+++ MakefileFri Jun 7 00:21:16 2002
@@ -108,6 +108,10 @@
PATH= /sbin:/bin:/usr/sbin:/usr/bin
MAKE= PATH=${PATH} make -m ${.CURDIR}/share/mk -f Makefile.inc1
+.if exists(${.CURDIR}/Makefile.user)
+.include ${.CURDIR}/Makefile.user
+.endif
+
#
# Handle the user-driven targets, using the source relative mk files.
#
-[ /usr/ports ]-
# diff -u Makefile.orig Makefile
--- Makefile.orig Mon Dec 31 02:29:06 2001
+++ MakefileFri Jun 7 00:12:14 2002
@@ -55,6 +55,9 @@
PORTSTOP= yes
.include bsd.port.subdir.mk
+.if exists(${.CURDIR}/Makefile.user)
+.include ${.CURDIR}/Makefile.user
+.endif
index:
@rm -f ${.CURDIR}/INDEX
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: The great perl rewrite - progress report
On 2002-06-06 17:31 +0100, Mark Murray wrote: etc/periodic/*keramida - fix - done I'll probably need to change this to incorporate the suggestions of [EMAIL PROTECTED] (Crist J. Clark), but yes, this is mostly done. The latest form of this diff is now at: http://people.freebsd.org/~keramida/diff/2002-05-29.periodic,aa - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
stlport with gcc3 broken in CURRENT
Hi all, Just to let you know. ports/devel/stlport is broken with gcc3 on CURRENT: And on STABLE, with gcc31 this works like a charm ... ././eh_test -s 100 ././eh_test : Exception handling testsuite. Setting 100 as base for random sizes. iteration #0 EH test : algobase [algobase] :testing uninitialized_copy() (weak) ... Abort trap - core dumped gmake: *** [eh_test.out] Error 134 (gdb) bt #0 0x2821892f in ?? () #1 0x2818093e in ?? () #2 0x28180983 in ?? () #3 0x281808eb in ?? () #4 0x0804aade in TestController::maybe_fail(long) () at nc_alloc.cpp:63 #5 0x0804abd3 in OperatorNew (s=4) at nc_alloc.h:120 #6 0x0804acc4 in operator new(unsigned) (s=4) at nc_alloc.cpp:230 #7 0x0804eb43 in void WeakCheckTestClass*, test_uninitialized_copy(TestClass* const, test_uninitialized_copy const, long) (v=@0xbfbff9ac, op=@0xbfbff9b0, max_iters=200) at TestClass.h:87 #8 0x0804e867 in test_algobase() () at test_algobase.cpp:38 #9 0x08049f74 in main (argc=3, argv=0xbfbffbec) at main.cpp:270 #10 0x08049579 in _start () GDB52 from ports seems stll be broken ... # gdb52 eh_test eh_test.core GNU gdb 5.2 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-portbld-freebsd5.0... Core was generated by `eh_test'. Program terminated with signal 6, Aborted. regcache.c:96: gdb-internal-error: register_buffer: Assertion `regnum = 0 regnum (NUM_REGS + NUM_PSEUDO_REGS)' failed. An internal GDB error was detected. This may make further debugging unreliable. Quit this debugging session? (y or n) n Create a core file containing the current state of GDB? (y or n) n Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
WARNING! New GNU Tar in 5-CURRENT could erroneously create world writeable dirs
Hi, I've just noticed that something wrong with the new tar in the base system (1.13.25) - when extracting some archives it creates 777 dirs, while permissions in the archive itself are OK (for example GNU make make-3.79.1.tar.gz - top level dir gets 777 as well as several other lowel level dirs). The issue is under investigation. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Buildworld errors caused by libfetch.so
--- Doug Barton [EMAIL PROTECTED] wrote: On Thu, 6 Jun 2002, Hiten Pandya wrote: [CC'ed to des@] Hi all. I am experiencing buildworld errors caused by the latest libfetch.so. The CVSUP source is just a couple of minutes old. Make sure that your next cvsup catches the update to the Makefile: $ ident /usr/src/usr.bin/fetch/Makefile /usr/src/usr.bin/fetch/Makefile: $FreeBSD: src/usr.bin/fetch/Makefile,v 1.9 2002/06/06 13:45:46 ru Exp Done. GCC3 environment ready!. Thanks everyone. The buildworld succeeded. -- Hiten __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump on current broken -- master/slave protocol botched
At 09:30 AM 6/6/2002 -0700, David O'Brien wrote: On Wed, Jun 05, 2002 at 08:01:54PM -0700, Manfred Antar wrote: I have been using the following command to dump for months with no problem: dump 0fua /dev/nsa0 /dev/da0s1a for the past few weeks I get this: (bin)504}dump 0fua /dev/nsa0 /dev/da0s1a DUMP: Date of this level 0 dump: Wed Jun 5 19:54:04 2002 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da0s1a (/) to /dev/nsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 67590 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: master/slave protocol botched. DUMP: The ENTIRE dump is aborted. I am seeing this also. :-( Is your world kernel in sync. I must admit my kernel is May 17 (been avoiding some suspicious problems in SMP kernels); but world is Jun 3rd. Everything in sync and current. Dump from May 3rd works == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: stlport with gcc3 broken in CURRENT
Martin, I seem to have a working gdb52 port installed that I built approximately a week ago... femme:/usr/ports/devel/stlport/work/STLport-4.5.3/test/eh29 gdb52 eh_test eh_test.core GNU gdb 5.2 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-portbld-freebsd5.0... Core was generated by `eh_test'. Program terminated with signal 6, Aborted. Reading symbols from ../../lib/libstlport_gcc.so...done. Loaded symbols for ../../lib/libstlport_gcc.so Reading symbols from /usr/lib/libstdc++.so.4...done. Loaded symbols for /usr/lib/libstdc++.so.4 Reading symbols from /usr/lib/libm.so.2...done. Loaded symbols for /usr/lib/libm.so.2 Reading symbols from /usr/lib/libc_r.so.5...done. Loaded symbols for /usr/lib/libc_r.so.5 Reading symbols from /usr/lib/libc.so.5...done. Loaded symbols for /usr/lib/libc.so.5 Reading symbols from /usr/libexec/ld-elf.so.1...done. Loaded symbols for /usr/libexec/ld-elf.so.1 #0 0x281f592f in kill () from /usr/lib/libc.so.5 (gdb) bt #0 0x281f592f in kill () from /usr/lib/libc.so.5 #1 0x282460aa in abort () from /usr/lib/libc.so.5 #2 0x2815d942 in __cxxabiv1::__terminate(void (*)()) () from /usr/lib/libstdc++.so.4 #3 0x2815d987 in std::terminate() () from /usr/lib/libstdc++.so.4 #4 0x2815d8ef in __cxa_throw () from /usr/lib/libstdc++.so.4 #5 0x0804acf7 in TestController::maybe_fail(long) () at nc_alloc.cpp:63 #6 0x0804c9dc in simulate_possible_failure () at nc_alloc.h:120 #7 0x0804ad73 in OperatorNew (s=4) at nc_alloc.cpp:206 #8 0x0804adf1 in operator new(unsigned) (s=4) at nc_alloc.cpp:230 #9 0x0804e7d0 in TestClass::Init(int) (this=0xbfbfe920, value=691697443) at TestClass.h:87 #10 0x080510ea in TestClass (this=0xbfbfe920, rhs=@0x80c0c04) at TestClass.h:106 #11 0x080510a3 in _ConstructTestClass, TestClass (__p=0xbfbfe920, __val=@0x80c0c04) at _construct.h:85 #12 0x08050f01 in __uninitialized_copyTestClass*, TestClass* (__first=0x80c0c04, __last=0x80c0d94, __result=0xbfbfe920) at _uninitialized.h:67 #13 0x08050e78 in uninitialized_copyTestClass*, TestClass* (__first=0x80c0c04, __last=0x80c0d94, __result=0xbfbfe920) at _uninitialized.h:79 #14 0x08050ca0 in test_uninitialized_copy::operator()(TestClass*) const (this=0xbfbfe900, buffer=0xbfbfe920) at test_algobase.cpp:45 #15 0x08050920 in void WeakCheckTestClass*, test_uninitialized_copy(TestClass* const, test_uninitialized_copy const, long) (v=@0xbfbfe91c, op=@0xbfbfe900, max_iters=200) at LeakCheck.h:90 #16 0x080506bf in test_algobase() () at test_algobase.cpp:95 #17 0x0804a548 in main (argc=3, argv=0xbfbff63c) at main.cpp:270 #18 0x08049d69 in _start () (gdb) -Trish -- Trish Lynch [EMAIL PROTECTED] FreeBSD The Power to Serve Ecartis Core Team [EMAIL PROTECTED] http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create world writeable dirs
Hi, I've just noticed that something wrong with the new tar in the base system (1.13.25) - when extracting some archives it creates 777 dirs, while permissions in the archive itself are OK (for example GNU make make-3.79.1.tar.gz - top level dir gets 777 as well as several other lowel level dirs). The issue is under investigation. Should be solved now. Stupid GNU folks for some reason decided that when tar is executed as uid 0 then by default umask(2) should not be applied to files and dirs being extracted. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Can anyone else confirm the x11amp port will not make?
I tried compiling x11amp just a few minutes ago and got this: cc -DHAVE_CONFIG_H -I. -I. -I../.. -O -pipe -I../.. -fomit-frame-pointer -funroll-all-loops -finline-functions -ffast-math -D_REENTRANT -I/usr/X11R6/include/gtk12 -I/usr/local/include/glib12 -I/usr/local/include -I/usr/X11R6/include -c mplayer.c -fPIC -DPIC -o mplayer.lo cc1: warning: changing search order for system directory /usr/local/include cc1: warning: as it has already been specified as a non-system directory mplayer.c: In function `DoITPanbrello': mplayer.c:3129: unrecognizable insn: (insn 225 34 226 (set (reg:CC 17 flags) (compare:CC (reg/v:QI 58) (const_int 128 [0x80]))) -1 (nil) (expr_list:REG_DEAD (reg/v:QI 58) (nil))) mplayer.c:3129: Internal compiler error in extract_insn, at recog.c:2132 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: nl_langinfo is MFCed, but what about compat/libc.so.4?
Hi, What is the status here ? In my CURRENT system, these compat libs are still the old ones :-( I've now updated the libs manually to be able to run OO on CURRENT. And yes - it works. Yes :-)) -r--r--r-- 1 root wheel 725012 Jun 7 02:36 libc.so.4 -r--r--r-- 1 root wheel 675600 Jun 7 02:38 libc_r.so.4 Can we please add now new uuencoded versions to the build ? That would make the openofice package working on CURRENT ! Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha can't map interrupt
A kernel built from last night's sources fails to allocate an interrupt to the NIC in my Miata: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #6: Fri Jun 7 01:55:10 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/alpha/compile/DSA Preloaded elf kernel /boot/kernel/kernel at 0xfc68. Digital Personal Workstation (Miata) Digital Personal WorkStation 600au, 598MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=0 extensions=0x1BWX OSF PAL rev: 0x100020116 real memory = 266493952 (260248K bytes) avail memory = 254672896 (248704K bytes) cia0: 2117x Core Logic chipset cia0: Pyxis, pass 1 cia0: extended capabilities: 1BWEN pcib0: 2117x PCI host bus adapter on cia0 pci0: PCI bus on pcib0 dc0: Intel 21143 10/100BaseTX port 0x9000-0x907f mem 0x80151000-0x8015107f at device 3.0 on pci0 dc0: couldn't map interrupt device_probe_and_attach: dc0 attach returned 6 [...] May 26 kernel boots fine: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #5: Sun May 26 13:22:40 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/alpha/compile/DSA Preloaded elf kernel /boot/kernel.old/kernel at 0xfc682000. Digital Personal Workstation (Miata) Digital Personal WorkStation 600au, 598MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=0 extensions=0x1BWX OSF PAL rev: 0x100020116 real memory = 266493952 (260248K bytes) avail memory = 254664704 (248696K bytes) cia0: 2117x Core Logic chipset cia0: Pyxis, pass 1 cia0: extended capabilities: 1BWEN pcib0: 2117x PCI host bus adapter on cia0 pci0: PCI bus on pcib0 dc0: Intel 21143 10/100BaseTX port 0x9000-0x907f mem 0x80151000-0x8015107f irq 0 at device 3.0 on pci0 dc0: interrupting at CIA irq 0 dc0: Ethernet address: 08:00:2b:86:88:55 miibus0: MII bus on dc0 nsphy0: DP83840 10/100 media interface on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto [...] DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: nl_langinfo is MFCed, but what about compat/libc.so.4?
Hi, Why is it linked against a hacked 4.x libc, instead of an unhacked 5.x libc? Because gcc31 and libstd++ and stlport are unusable for OpenOffice to build. Exceptions are broken. Optimazations are broken. Why is the compat stuff necessary for -current at all? Because some users like to try OpenOffice even if they use CURRENT ? If you like to help me you can fix: ports/devel/stlport so it doesn't coredump anymore doing the tests. Which means fixing gcc31 in CURRENT, since the package was build on STABLE with gcc31 from ports. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: alpha can't map interrupt
Warner -- a pci interupt line of 0 is valid. Please back out your PCI_INTERRUPT_VALID changes in pci.c, or change that macro to allow a value of 0. Thanks, Drew Dag-Erling Smorgrav writes: A kernel built from last night's sources fails to allocate an interrupt to the NIC in my Miata: ... dc0: Intel 21143 10/100BaseTX port 0x9000-0x907f mem 0x80151000-0x8015107f at device 3.0 on pci0 dc0: couldn't map interrupt device_probe_and_attach: dc0 attach returned 6 [...] May 26 kernel boots fine: ... dc0: Intel 21143 10/100BaseTX port 0x9000-0x907f mem 0x80151000-0x8015107f irq 0 at device 3.0 on pci0 .. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
could sleep with process lock from kern_prot.c:867
Just FYI. I got this with debug.witness_ddb=1 kernel. ../../../vm/uma_core.c:1327: could sleep with process lock locked from ../../../kern/kern_prot.c:867 Debugger(witness_sleep) Stopped at breakpoint+0x4: popl%ebp db trace breakpoint(e86f0bfc,c01f84ac,c036b060,c036b06e,e86f0bdc) at breakpoint+0x4 Debugger(c036b060) at Debugger+0x49 witness_sleep(1,0,c037e2b1,52f) at witness_sleep+0x178 uma_zalloc_arg(c081d600,0,4) at uma_zalloc_arg+0x46 uma_zalloc(c081d600,4) at uma_zalloc+0x10 malloc(20,c03bfee0,4) at malloc+0xa5 uifind(1) at uifind+0x5f change_euid(e86bd800,1) at change_euid+0x26 setreuid(e86e1d60,e86f0cf8) at setreuid+0x13b syscall(2f,2f,2f,bfbff550,1) at syscall+0x299 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (126, FreeBSD ELF, setreuid), eip = 0x280e8cbf, esp = 0xbfbff3f0, ebp = 0xbfbff40c --- -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create worldwriteable dirs
I've just noticed that something wrong with the new tar in the base system (1.13.25) - when extracting some archives it creates 777 dirs, while permissions in the archive itself are OK (for example GNU make make-3.79.1.tar.gz - top level dir gets 777 as well as several other lowel level dirs). The issue is under investigation. The latest version on ftp://ftp.gnu.org/gnu/tar/ is 1.13. The ones on ftp://alpha.gnu.org/gnu/tar/ (and everything else on that site) are considered unstable. I suppose it's too late to suggest tar 1.13 as a starting point, but maybe this could be kept in mind when importing other GNU products. -- Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can anyone else confirm the x11amp port will not make?
On Thu, Jun 06, 2002 at 07:30:09PM -0500, drogoh wrote: I tried compiling x11amp just a few minutes ago and got this: Yes, this kind of thing should be expected after a compiler upgrade. Follow the directions and report the bug to the gcc developers. Kris msg39285/pgp0.pgp Description: PGP signature
Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create world writeable dirs
In the last episode (Jun 06), Trevor Johnson said: I've just noticed that something wrong with the new tar in the base system (1.13.25) - when extracting some archives it creates 777 dirs, while permissions in the archive itself are OK (for example GNU make make-3.79.1.tar.gz - top level dir gets 777 as well as several other lowel level dirs). The issue is under investigation. The latest version on ftp://ftp.gnu.org/gnu/tar/ is 1.13. The ones on ftp://alpha.gnu.org/gnu/tar/ (and everything else on that site) are considered unstable. I suppose it's too late to suggest tar 1.13 as a starting point, but maybe this could be kept in mind when importing other GNU products. Tar 1.13 is 3 years old, and has many bugs (incremental backups are unusable, for example). -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: alpha can't map interrupt
In message: [EMAIL PROTECTED] Andrew Gallatin [EMAIL PROTECTED] writes: : : : Warner -- a pci interupt line of 0 is valid. Please back out your : PCI_INTERRUPT_VALID changes in pci.c, or change that macro : to allow a value of 0. An interrupt line of 0 is *NOT* valid. However, the check for zero should only be on the i386 port. Where did I have it? Oh, I see now. I didn't change the PCI_INTERRUPT_VALID to include zero, I just changed some code to use it. It was used in pcib. But I'll make sure that it works on alpha. Is that something that you can test for me if I come up with a fix for? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: alpha can't map interrupt
Please accept my appologies for this, it does look like I messed up the MI code. The following change may mess up the pcib code a little, but I think that the MD code now does the right thing. Does this fix things for you? Warner Index: pcivar.h === RCS file: /cache/ncvs/src/sys/dev/pci/pcivar.h,v retrieving revision 1.56 diff -u -r1.56 pcivar.h --- pcivar.h1 Jun 2002 05:40:33 - 1.56 +++ pcivar.h7 Jun 2002 02:35:52 - @@ -246,10 +246,12 @@ #undef PCIB_ACCESSOR /* - * PCI interrupt validation. + * PCI interrupt validation. Invalid interrupt values such as 0 or 128 + * on i386 or other platforms should be mapped out in the MD pcireadconf + * code and not here, since the only MI invalid IRQ is 255. */ #define PCI_INVALID_IRQ255 -#define PCI_INTERRUPT_VALID(x) (((x) != 0) ((x) != PCI_INVALID_IRQ)) +#define PCI_INTERRUPT_VALID(x) ((x) != PCI_INVALID_IRQ) /* * Convenience functions. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create world writeable dirs
Dan Nelson wrote: Tar 1.13 is 3 years old, and has many bugs (incremental backups are unusable, for example). On the flip side, I hear it respects the umask when running as root... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: nl_langinfo is MFCed, but what about compat/libc.so.4?
Martin Blapp wrote: Why is it linked against a hacked 4.x libc, instead of an unhacked 5.x libc? Because gcc31 and libstd++ and stlport are unusable for OpenOffice to build. Exceptions are broken. Optimazations are broken. I think that if this is going to result in MFC's of things that change the libraries for 4.6, that the update of the libc image in 5.x for -compat is going to have to wait for 4.6-RELEASE. I also think that it may mean another major version number change, since there's aren't real minor version numbers any more. 8-(. If you like to help me you can fix: ports/devel/stlport so it doesn't coredump anymore doing the tests. Which means fixing gcc31 in CURRENT, since the package was build on STABLE with gcc31 from ports. That last sentence is hard to parse unambiguously. Are you saying that it breaks because of -current, or are you saying it breaks because of the compiler change, or are you saying that the compiler in ports is different than the compiler that's now in 5.x? Basically, you need to pin the problem down a little more than Somewhere in these 60G of download you'd have to do to repeat the build. As a note, I would ask if DESTDIR was being set or not? It may be that the reason it's working is that you are getting the old compiler headers instead of the new ones, when you compile it with the new compiler on -stable (I've noted this problem before; the first time was in 1998). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Tue, Jun 04, 2002 at 09:43:59PM +0900, Motoyuki Konno wrote: Please try the following patch. Thanks, this fixed the XFree86-4-libraries build. I've committed the patch. Kris msg39291/pgp0.pgp Description: PGP signature
someone broke sendmail or install
It appears someone either broke sendmail or install. From an make installworld of sources from 02/06/06 1851 PDT. I'm getting install -C -o root -g wheel -m 755 -d /usr/share/sendmail/cf usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 (continuing) `install' not remade because of errors. It seems [EMAIL PROTECTED] forgot to place an entry in src/UPDATING that he purposely broke world. Revision 1.55 / (download) - annotate - [select for diffs], Wed Jun 5 17:37:48 2002 UTC (35 hours, 7 minutes ago) by ru Branch: MAIN CVS Tags: HEAD Changes since 1.54: +1 -8 lines Diff to previous 1.54 (colored) Start the (overdue) de-orbit sequence for the -d -C combo, as was promised in revision 1.43. MFC after: 1 month -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
i386 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /tmp/des/obj/i386/d/home/des/tinderbox/src/i386/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- === gnu/usr.bin/texinfo/infokey === gnu/usr.bin/texinfo/install-info === gnu/usr.bin/texinfo/texindex texindex.o: In function `main': texindex.o(.text+0xbb): warning: mktemp() possibly used unsafely; consider using mkstemp() === gnu/usr.bin/texinfo/doc === gnu/usr.bin/cvs === gnu/usr.bin/cvs/lib === gnu/usr.bin/cvs/libdiff make: don't know how to make all. Stop *** Error code 2 Stop in /d/home/des/tinderbox/src/gnu/usr.bin/cvs. *** Error code 1 Stop in /d/home/des/tinderbox/src/gnu/usr.bin. *** Error code 1 Stop in /d/home/des/tinderbox/src/gnu. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: someone broke sendmail or install
sgk install -C -o root -g wheel -m 755 -d /usr/share/sendmail/cf
Did you override $INSTALL in /etc/make.conf?
sgk It seems [EMAIL PROTECTED] forgot to place an entry
sgk in src/UPDATING that he purposely broke world.
I'm curious what Makefile's are supposed to use if not ${INSTALL}.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
back out rev. 1.55 of xinstall.c
Can someone back out revision 1.55 of xinstall.c? It breaks make installworld with the following: === share/sendmail install -C -o root -g wheel -m 755 -d /usr/share/sendmail/cf usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 (continuing) `install' not remade because of errors. Note, I have INSTALL set to install -C as documented in make.conf(5) and share/examples/etc/defaults/make.conf. If revision 1.55 is to stay, then the documentation should be updated. Also, PR bin/37795 shoudl be closed, and a note added to src/UPDATING for all of us who set INSTALL in make.conf a long time ago. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: someone broke sendmail or install
On Thu, Jun 06, 2002 at 10:39:33PM -0700, Gregory Neil Shapiro wrote:
sgk install -C -o root -g wheel -m 755 -d /usr/share/sendmail/cf
Did you override $INSTALL in /etc/make.conf?
INSTALL is set to install -C in /etc/make.conf as
documented in make.conf(5) and share/examples/etc/defaults/make.conf.
sgk It seems [EMAIL PROTECTED] forgot to place an entry
sgk in src/UPDATING that he purposely broke world.
I'm curious what Makefile's are supposed to use if not ${INSTALL}.
Well, I personally believe that if install's -d option is
mutually exclusive of -bCcpSs, then install should reset
things instead of issue an error.
--- xinstall.c.orig Thu Jun 6 22:45:29 2002
+++ xinstall.c Thu Jun 6 22:46:39 2002
@@ -173,8 +173,11 @@
argv += optind;
/* some options make no sense when creating directories */
- if ((safecopy || docompare || dostrip) dodir)
- usage();
+ if (dodir) {
+ safecopy = 0;
+ docompare = 0;
+ dostrip = 0;
+ }
/* must have at least two arguments, except when creating directories */
if (argc 2 !dodir)
--
Steve
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create world writeable dirs
Hi, I've just noticed that something wrong with the new tar in the base system (1.13.25) - when extracting some archives it creates 777 dirs, while permissions in the archive itself are OK (for example GNU make make-3.79.1.tar.gz - top level dir gets 777 as well as several other lowel level dirs). The issue is under investigation. Should be solved now. Stupid GNU folks for some reason decided that when tar is executed as uid 0 then by default umask(2) should not be applied to files and dirs being extracted. That said, anybody who runs 5.0-CURRENT with the new tar is advised to clean up all ports' WRKDIRs she might have, to avoid being trojaned by a local user. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create worldwriteable dirs
Dan Nelson wrote: The latest version on ftp://ftp.gnu.org/gnu/tar/ is 1.13. The ones on ftp://alpha.gnu.org/gnu/tar/ (and everything else on that site) are considered unstable. I suppose it's too late to suggest tar 1.13 as a starting point, but maybe this could be kept in mind when importing other GNU products. The point I was trying to make is perhaps better conveyed by ftp://alpha.gnu.org/README . Tar 1.13 is 3 years old, and has many bugs (incremental backups are unusable, for example). I don't know why the GNU tar programmers decide that certain versions are stable and others are unstable. I do know that the former are found on ftp.gnu.org, and the latter on alpha.gnu.org. Now you know too, in case you didn't already. :-) I just discovered Jorg Schilling's star (http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/star.html) . He says that it supports POSIX.1-2001, which I assume dates from last year. It's available in the ports collection and it's under the GNU GPL. The documentation for GNU tar 1.13.25 says that it complies with POSIX 1003.1b, which was drafted in 1987 and completed in 1990. The GNU tar in FreeBSD-STABLE is from 1993 and it still works most of the time! According to Mr. Schilling's testing, GNU tar 1.13.25 has a bug: ftp://ftp.fokus.gmd.de/pub/unix/star/testscripts/README.gtarfail . I guess it qualifies as a non-trivial program. :-) On my friend's BSD/OS system, there is no tar--or rather, it's just a hard link to pax: % ls -li `which tar` `which pax` 1819 -r-xr-xr-x 2 bin bin 58288 Jun 12 1998 /bin/pax 1819 -r-xr-xr-x 2 bin bin 58288 Jun 12 1998 /bin/tar Their tar/pax hybrid must check its argv[0]. Isn't that evil? -- Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
