Re: mysql-server build errors
In the last episode (Aug 08), Beech Rintoul said: Anyone have a pointer to get this to build? cc -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME=\/usr/local\ -fno-exceptions -fno-rtti -DMYSQLD_NET_RETRY_COUNT=100 -c mysqld.cc /usr/include/tcpd.h: In function `void* handle_connections_sockets(void*)': /usr/include/tcpd.h:137: too many arguments to function `void sock_host()' mysqld.cc:2428: at this point in file It's a bug in the tcpwrappers headers; they declare functions with no parameters, and gcc rightfully complains about using them in c++ code. Remove the --with-libwrap line from the port Makefile as a workaround. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Comments on Release Building for -current
Bruce Evans wrote: On Sat, 3 Aug 2002, Mike Barcroft wrote: Andrew Kolchoogin [EMAIL PROTECTED] writes: ... sorry, but some time ago I read here that gcc -O2 breaks our printf() in libc. I haven't find any assembler code in /usr/src/lib/libc/stdio/vfprintf.c, as such, if some C compiler can't handle VALID and STANDARDS-COMPLIANT C code, this compiler is broken. Isn't it? Indeed, all of FreeBSD users could help to catch such a bug in gcc optimizer code. :) If someone could find the small segment of code where the optimizer screws up, and write a small program to demonstrate the problem, we would have a good chance of it getting fixed. Er, someone (Dan Lukes) has already done this. See PR 40209. I'm sorry I haven't found time to look at it in detail. O2-compiling -CURRENT (and -march=athlon ...) still manages to break DCCs in xchat, like: Program received signal SIGBUS, Bus error. 0x286b3220 in __vfprintf () from /usr/lib/libc.so.5 (gdb) bt #0 0x286b3220 in __vfprintf () from /usr/lib/libc.so.5 #1 0x286b20ca in __vfprintf () from /usr/lib/libc.so.5 #2 0x286ad622 in snprintf () from /usr/lib/libc.so.5 #3 0x08066036 in fe_dcc_update_recv () #4 0x08086ee0 in dcc_check_timeouts () #5 0x0809dd83 in lag_check () #6 0x2825c496 in g_timeout_dispatch () from /usr/local/lib/libglib12.so.3 #7 0x2825b658 in g_main_dispatch () from /usr/local/lib/libglib12.so.3 #8 0x2825bbf9 in g_main_iterate () from /usr/local/lib/libglib12.so.3 #9 0x2825bd86 in g_main_run () from /usr/local/lib/libglib12.so.3 #10 0x2844fa38 in gtk_main () from /usr/X11R6/lib/libgtk12.so.2 #11 0x08069311 in fe_main () #12 0x0809e950 in main () #13 0x080638c1 in _start () Regards, -- Michael Nottebrock And the reasons? There are no reasons. msg41682/pgp0.pgp Description: PGP signature
Re: mysql-server build errors
Edit line 92 of sql/mysqld.cc: --#ifdef __linux__ ++ #ifdef __FreeBSD__ However that'll only get you past this set of errors. And then it gets tricky and has something to do with the new C++ compiler that I haven't quite wrapped my mind around yet. -Steve - Original Message - From: Beech Rintoul [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, August 08, 2002 2:01 PM Subject: mysql-server build errors Anyone have a pointer to get this to build? -DDEFAULT_MYSQL_HOME=\/usr/local\ -DDATADIR=\/var/db/mysql\ -DSHAREDIR=\/usr/local/share/mysql\ -DHAVE_CONFIG_H -I../bdb/build_unix -I../innobase/include -I./../include -I./../regex -I. -I../include -I.. -I.-DDBUG_OFF -O -pipe -mcpu=pentiumpro -felide-constructors -fno-rtti -fno-exceptions -fno-implicit-templates -fno-exceptions -fno-rtti -DMYSQLD_NET_RETRY_COUNT=100 -c mysqld.cc /usr/include/tcpd.h: In function `void* handle_connections_sockets(void*)': /usr/include/tcpd.h:137: too many arguments to function `void sock_host()' mysqld.cc:2428: at this point in file /usr/include/tcpd.h:75: too many arguments to function `int hosts_access()' mysqld.cc:2429: at this point in file /usr/include/tcpd.h:130: too many arguments to function `char* eval_client()' mysqld.cc:2437: at this point in file *** Error code 1 Beech -- --- Beech Rintoul - IT Manager - Instructor - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission \ / - NO HTML/RTF in e-mail | P.O. Box 230510 X - NO Word docs in e-mail | Anchorage, AK 99523-0510 / \ - 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
Re: mysql-server build errors
On Thursday 08 August 2002 11:50 am, Dan Nelson wrote: In the last episode (Aug 08), Beech Rintoul said: Anyone have a pointer to get this to build? cc -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME=\/usr/local\ -fno-exceptions -fno-rtti -DMYSQLD_NET_RETRY_COUNT=100 -c mysqld.cc /usr/include/tcpd.h: In function `void* handle_connections_sockets(void*)': /usr/include/tcpd.h:137: too many arguments to function `void sock_host()' mysqld.cc:2428: at this point in file It's a bug in the tcpwrappers headers; they declare functions with no parameters, and gcc rightfully complains about using them in c++ code. Remove the --with-libwrap line from the port Makefile as a workaround. Thanks...That worked. Beech -- --- Beech Rintoul - IT Manager - Instructor - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission \ / - NO HTML/RTF in e-mail | P.O. Box 230510 X - NO Word docs in e-mail | Anchorage, AK 99523-0510 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
Ruslan,
Here is my latest version. It has all the changes you requested and
a fix for the case where there isn't a third floppy.
John
--
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
Index: usr.sbin/sysinstall/system.c
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/system.c,v
retrieving revision 1.119
diff -u -r1.119 system.c
--- usr.sbin/sysinstall/system.c1 Nov 2001 23:32:46 - 1.119
+++ usr.sbin/sysinstall/system.c8 Aug 2002 09:17:01 -
@@ -348,7 +348,13 @@
snprintf(buf, FILENAME_MAX, /stand/help/%s.hlp.gz, file);
if (file_readable(buf))
return expand(buf);
+snprintf(buf, FILENAME_MAX, /stand/help/%s.hlp, file);
+if (file_readable(buf))
+ return expand(buf);
snprintf(buf, FILENAME_MAX, /stand/help/%s.TXT.gz, file);
+if (file_readable(buf))
+ return expand(buf);
+snprintf(buf, FILENAME_MAX, /stand/help/%s.TXT, file);
if (file_readable(buf))
return expand(buf);
snprintf(buf, FILENAME_MAX, /usr/src/usr.sbin/sysinstall/help/%s.hlp, file);
Index: release/Makefile
===
RCS file: /home/ncvs/src/release/Makefile,v
retrieving revision 1.698
diff -u -r1.698 Makefile
--- release/Makefile5 Aug 2002 16:57:43 - 1.698
+++ release/Makefile8 Aug 2002 20:04:08 -
@@ -518,7 +518,8 @@
.endif
cd ${j}_crunch; ${WMAKE} -f ${j}_crunch.mk subclean
cd ${.CURDIR}/..; ${TMAKE} build-tools
- cd ${j}_crunch; ${WMAKE} -f ${j}_crunch.mk all
+ cd ${j}_crunch; ${WMAKE} -f ${j}_crunch.mk \
+ CFLAGS=-Os -pipe -DNO_CPU_CFLAGS all
mv ${j}_crunch/${j}_crunch ${RD}/crunch/${j}
.endfor
touch release.5
@@ -654,15 +655,15 @@
${RD}/mfsfd/stand/etc/services
ln ${RD}/mfsfd/stand/etc/services ${RD}/mfsfd/etc/services
ln ${RD}/mfsfd/stand/etc/netconfig ${RD}/mfsfd/etc/netconfig
- gzip -9c ${RD}/trees/base/COPYRIGHT ${RD}/mfsfd/stand/help/COPYRIGHT.hlp.gz
+ cp ${RD}/trees/base/COPYRIGHT ${RD}/mfsfd/stand/help/COPYRIGHT.hlp
.if !defined(NODOC)
@for i in ${DIST_DOCS_ARCH_INDEP}; do \
- gzip -9c ${RND}/${RELNOTES_LANG}/$$i/article.txt
${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT.gz; \
+ cp ${RND}/${RELNOTES_LANG}/$$i/article.txt ${RD}/mfsfd/stand/help/`echo
+$${i} | tr 'a-z' 'A-Z'`.TXT; \
done
@for i in ${DIST_DOCS_ARCH_DEP}; do \
- gzip -9c ${RND}/${RELNOTES_LANG}/$$i/${TARGET}/article.txt
${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT.gz; \
+ cp ${RND}/${RELNOTES_LANG}/$$i/${TARGET}/article.txt
+${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \
done
- @mv ${RD}/mfsfd/stand/help/INSTALLATION.TXT.gz
${RD}/mfsfd/stand/help/INSTALL.TXT.gz
+ @mv ${RD}/mfsfd/stand/help/INSTALLATION.TXT ${RD}/mfsfd/stand/help/INSTALL.TXT
.endif
-test -f ${.CURDIR}/install.cfg cp ${.CURDIR}/install.cfg ${RD}/mfsfd
@mkdir -p ${RD}/mfsfd/boot
@@ -674,16 +675,23 @@
@echo Making the regular boot floppy.
@tar --exclude CVS -cf - -C ${.CURDIR}/../usr.sbin/sysinstall help | \
tar xf - -C ${RD}/mfsfd/stand
- @echo Compressing doc files...
- @gzip -9 ${RD}/mfsfd/stand/help/*.hlp
.if ${TARGET_ARCH} == alpha
rm -rf ${RD}/mfsfd/stand/help/*
.endif
.if exists(${.CURDIR}/${TARGET}/drivers.conf)
@mkdir -p ${RD}/mfsfd/stand/modules
- @awk -f ${.CURDIR}/scripts/driver-copy2.awk \
+ @awk -f ${.CURDIR}/scripts/driver-copy2.awk 2 \
${.CURDIR}/${TARGET}/drivers.conf \
${RD}/trees/base/boot/kernel ${RD}/mfsfd/stand/modules
+ -@rm -rf ${RD}/driversfd
+ @mkdir ${RD}/driversfd
+ @awk -f ${.CURDIR}/scripts/driver-copy2.awk 3 \
+ ${.CURDIR}/${TARGET}/drivers.conf \
+ ${RD}/trees/base/boot/kernel ${RD}/driversfd
+ -@rmdir ${RD}/driversfd
+ [ -d ${RD}/driversfd ] sh -e ${.CURDIR}/scripts/doFS.sh \
+ ${RD}/floppies/drivers.flp ${RD} ${MNT} ${BOOTSIZE} \
+ ${RD}/driversfd ${BOOTINODE} ${BOOTLABEL}
.endif
sh -e ${.CURDIR}/scripts/doFS.sh -s mfsroot ${RD} ${MNT} \
${MFSSIZE} ${RD}/mfsfd ${MFSINODE} ${MFSLABEL}
@@ -963,7 +971,8 @@
cd ${.CURDIR}/..; \
KERNEL_KO=BOOTMFS KODIR= \
${CROSSMAKE} ${KERNEL_FLAGS} -DNO_MODULES -DNO_KERNELCLEAN \
- KERNCONF=BOOTMFS buildkernel reinstallkernel \
+ KERNCONF=BOOTMFS COPTFLAGS=-Os -pipe -DNO_CPU_COPTFLAGS \
+ buildkernel reinstallkernel \
DESTDIR=${RD}/kernels
[ -r ${.CURDIR}/../sys/${TARGET}/conf/BOOTMFS.hints ] \
cp ${.CURDIR}/../sys/${TARGET}/conf/BOOTMFS.hints ${RD}/kernels
@@ -995,6 +1004,7 @@
.endif
@echo load -t mfs_root /mfsroot ${RD}/image.${FSIMAGE}/boot/loader.rc
@echo set
Re: mysql-server build errors
On Thu, Aug 08, 2002 at 12:05:44PM -0800, Beech Rintoul wrote: On Thursday 08 August 2002 11:50 am, Dan Nelson wrote: In the last episode (Aug 08), Beech Rintoul said: Anyone have a pointer to get this to build? cc -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME=\/usr/local\ -fno-exceptions -fno-rtti -DMYSQLD_NET_RETRY_COUNT=100 -c mysqld.cc /usr/include/tcpd.h: In function `void* handle_connections_sockets(void*)': /usr/include/tcpd.h:137: too many arguments to function `void sock_host()' mysqld.cc:2428: at this point in file It's a bug in the tcpwrappers headers; they declare functions with no parameters, and gcc rightfully complains about using them in c++ code. Remove the --with-libwrap line from the port Makefile as a workaround. Thanks...That worked. Worked=mysql actually compiled? Or it got past that section? Removing --with-libwrap certainly gets past that section but on my system it still spews a lot of errors during the final link: item.o(.gnu.linkonce.d._ZTV9Item_buff+0x8): undefined reference to `__cxa_pure_v irtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x28): undefined reference to `__ cxa_pure_virtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x2c): undefined reference to `__ cxa_pure_virtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x30): undefined reference to `__ cxa_pure_virtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x34): undefined reference to `__ cxa_pure_virtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x38): more undefined references to `__cxa_pure_virtual' follow item_sum.o: In function `Item_sum_count_distinct::~Item_sum_count_distinct()': item_sum.o(.text+0x19c7): undefined reference to `operator delete[](void*)' item_sum.o(.text+0x19dc): undefined reference to `operator delete(void*)' item_sum.o: In function `Item_sum_count_distinct::~Item_sum_count_distinct()': item_sum.o(.text+0x1aa7): undefined reference to `operator delete[](void*)' item_sum.o(.text+0x1abc): undefined reference to `operator delete(void*)' item_sum.o: In function `Item_sum_count_distinct::~Item_sum_count_distinct()': item_sum.o(.text+0x1b87): undefined reference to `operator delete[](void*)' [list goes on for a while] This is with -CURRENT from today (8/8). -Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mysql-server build errors
On Thursday 08 August 2002 12:05 pm, Beech Rintoul wrote: On Thursday 08 August 2002 11:50 am, Dan Nelson wrote: In the last episode (Aug 08), Beech Rintoul said: Anyone have a pointer to get this to build? cc -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME=\/usr/local\ -fno-exceptions -fno-rtti -DMYSQLD_NET_RETRY_COUNT=100 -c mysqld.cc /usr/include/tcpd.h: In function `void* handle_connections_sockets(void*)': /usr/include/tcpd.h:137: too many arguments to function `void sock_host()' mysqld.cc:2428: at this point in file It's a bug in the tcpwrappers headers; they declare functions with no parameters, and gcc rightfully complains about using them in c++ code. Remove the --with-libwrap line from the port Makefile as a workaround. Thanks...That worked. I spoke too soon :-( Now it errors at: sql_analyse.o: In function `proc_analyse_init(THD*, st_order*, select_result*, ListItem)': sql_analyse.o(.text+0x1f): undefined reference to `operator new(unsigned)' sql_analyse.o(.gnu.linkonce.d._ZTV10field_info+0x10): undefined reference to `__cxa_pure_virtual' sql_analyse.o(.gnu.linkonce.d._ZTV10field_info+0x14): undefined reference to `__cxa_pure_virtual' sql_analyse.o(.gnu.linkonce.d._ZTV10field_info+0x18): undefined reference to `__cxa_pure_virtual' sql_analyse.o(.gnu.linkonce.d._ZTV10field_info+0x1c): undefined reference to `__cxa_pure_virtual' sql_analyse.o(.gnu.linkonce.d._ZTV10field_info+0x20): undefined reference to `__cxa_pure_virtual' sql_analyse.o(.gnu.linkonce.d._ZTV10field_info+0x24): more undefined references to `__cxa_pure_virtual' followsql_analyse.o: In function `analyse::~analyse()': sql_analyse.o(.gnu.linkonce.t._ZN7analyseD0Ev+0x56): undefined reference to `operator delete(void*)' collect2: ld returned 1 exit status *** Error code 1 Beech -- --- Beech Rintoul - IT Manager - Instructor - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission \ / - NO HTML/RTF in e-mail | P.O. Box 230510 X - NO Word docs in e-mail | Anchorage, AK 99523-0510 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire support
Julian Elischer wrote: On Thu, 8 Aug 2002, Katsushi Kobayashi wrote: Did you suggest the same API should be used on both Darwin and FreeBSD ? Or, should we share the same code on the device driver level ? Although I have not read the terms and condition carefully, I am afraid if once read the source code, I cannot write any firewire kernel code. There is no problem with that.. The courts have said that what you know in your head can not be withheld from your use. You may not be able to DIRECTLY COPY it but you can use it as a source of information. (depending on the coppyright you may even be able to copy it of course :-) He is in Japan. Japan is one of the few places, besides the U.S., which permits software patents. In additioan, they have a number of draconian laws about reverse engineering, and so on, similar to the laws that have been recently passed or are in the process of being passed in the U.S.. You can not sell or rent a game cartridge for a console game there, for example. He may need someone else to agree to the license for him, and then document the API without coping the information directly. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
Maxim Sobolev wrote: But then everyone needs to boot with 3 floppies. With my way, we can hopefully select the optimum so that most people will only need 2 floppies, ie the most popular drivers should go on mfsroot.flp. Both approaches have its own advantages and disadvantages. IMO, big disadvantage of your method is that user needs to know which drivers he really wants, which makes installation less fool-prof for novice users. Give feedback on hardware without drivers. Keep inserting floppies until there isn't any. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mysql-server build errors
In the last episode (Aug 08), Beech Rintoul said:
On Thursday 08 August 2002 12:05 pm, Beech Rintoul wrote:
I spoke too soon :-(
Now it errors at:
sql_analyse.o: In function `proc_analyse_init(THD*, st_order*, select_result*,
ListItem)':
sql_analyse.o(.text+0x1f): undefined reference to `operator new(unsigned)'
sql_analyse.o(.gnu.linkonce.d._ZTV10field_info+0x10): undefined reference to
`__cxa_pure_virtual'
Ok, that's a bug in the port Makefile :) Remove line 67 ( CXX=${CC} ).
That tells mysql to compile and link as though the sources were C, not
C++. I'm amazed it ever built with that flag.
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: mysql-server build errors
On Thursday 08 August 2002 02:06 pm, Dan Nelson wrote:
In the last episode (Aug 08), Beech Rintoul said:
On Thursday 08 August 2002 12:05 pm, Beech Rintoul wrote:
I spoke too soon :-(
Now it errors at:
sql_analyse.o: In function `proc_analyse_init(THD*, st_order*,
select_result*, ListItem)': sql_analyse.o(.text+0x1f): undefined
reference to `operator new(unsigned)'
sql_analyse.o(.gnu.linkonce.d._ZTV10field_info+0x10): undefined reference
to `__cxa_pure_virtual'
Ok, that's a bug in the port Makefile :) Remove line 67 ( CXX=${CC} ).
That tells mysql to compile and link as though the sources were C, not
C++. I'm amazed it ever built with that flag.
OK - That finally built and installed...thanks for your help. Someone might
want to commit those changes.
Beech
--
---
Beech Rintoul - IT Manager - Instructor - [EMAIL PROTECTED]
/\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission
\ / - NO HTML/RTF in e-mail | P.O. Box 230510
X - NO Word docs in e-mail | Anchorage, AK 99523-0510
/ \ -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Firewire support
On Thu, 2002-08-08 at 16:45, Terry Lambert wrote: Julian Elischer wrote: On Thu, 8 Aug 2002, Katsushi Kobayashi wrote: Did you suggest the same API should be used on both Darwin and FreeBSD ? Or, should we share the same code on the device driver level ? Although I have not read the terms and condition carefully, I am afraid if once read the source code, I cannot write any firewire kernel code. There is no problem with that.. The courts have said that what you know in your head can not be withheld from your use. You may not be able to DIRECTLY COPY it but you can use it as a source of information. (depending on the coppyright you may even be able to copy it of course :-) He is in Japan. Japan is one of the few places, besides the U.S., which permits software patents. In additioan, they have a number of draconian laws about reverse engineering, and so on, similar to the laws that have been recently passed or are in the process of being passed in the U.S.. You can not sell or rent a game cartridge for a console game there, for example. He may need someone else to agree to the license for him, and then document the API without coping the information directly. I'm not sure why Apple would bite the hand that feeds it. BSD is not powerless against them, I see no reason to be afraid. My argument is that Apple has made claims that they will be contributing back to BSD. So, if Katsushi can't go check out their code and make FreeBSD's compatible, then they will be going against their word, and that will not look good to very many of us. Apple is in plenty of hot water already, they don't need a bunch of pissed off BSD users too. In light of the recent and long overdue questioning of business ethics, I think it's our duty to challenge Apple. Apple could have taken the code and walked away, but since they want to be a part of the process they're going to have to deal with us. Of course, it's not my neck on the line, so I totally respect Katsushi's hesitance. If the decision is made to go ahead and Apple follows up with legal action, I can guarantee you that the very next day I will be on the phone with as many senators as I can. Not only that but I would not stop until all parties names are clear and they are free to go ahead with writing the code. I don't think my opinion is out of line, and I have confidence that many of you support this attitude. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: src/usr.sbin/crunch/crunchgen/crunched_main.c
pmedwards The last commit to this appears to have broken it. main() was pmedwards updated to include envp, but crunched_main() calls main() pmedwards without the extra argument. pmedwards This causes make release of -current on -stable to barf for me, pmedwards so I can't truly test the patch without waiting about 8 hours, pmedwards other than to say making the modifications to the generated file pmedwards does at least allow it to compile. I'll take a look at it immediately. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire support
On Thu, Aug 08, 2002 at 20:20:24 -0500, Peter Schultz wrote: On Thu, 2002-08-08 at 16:45, Terry Lambert wrote: Julian Elischer wrote: On Thu, 8 Aug 2002, Katsushi Kobayashi wrote: Did you suggest the same API should be used on both Darwin and FreeBSD ? Or, should we share the same code on the device driver level ? Although I have not read the terms and condition carefully, I am afraid if once read the source code, I cannot write any firewire kernel code. There is no problem with that.. The courts have said that what you know in your head can not be withheld from your use. You may not be able to DIRECTLY COPY it but you can use it as a source of information. (depending on the coppyright you may even be able to copy it of course :-) He is in Japan. Japan is one of the few places, besides the U.S., which permits software patents. In additioan, they have a number of draconian laws about reverse engineering, and so on, similar to the laws that have been recently passed or are in the process of being passed in the U.S.. You can not sell or rent a game cartridge for a console game there, for example. He may need someone else to agree to the license for him, and then document the API without coping the information directly. I'm not sure why Apple would bite the hand that feeds it. BSD is not powerless against them, I see no reason to be afraid. My argument is that Apple has made claims that they will be contributing back to BSD. So, if Katsushi can't go check out their code and make FreeBSD's compatible, then they will be going against their word, and that will not look good to very many of us. Apple is in plenty of hot water already, they don't need a bunch of pissed off BSD users too. In light of the recent and long overdue questioning of business ethics, I think it's our duty to challenge Apple. Apple could have taken the code and walked away, but since they want to be a part of the process they're going to have to deal with us. Of course, it's not my neck on the line, so I totally respect Katsushi's hesitance. If the decision is made to go ahead and Apple follows up with legal action, I can guarantee you that the very next day I will be on the phone with as many senators as I can. Not only that but I would not stop until all parties names are clear and they are free to go ahead with writing the code. I don't think my opinion is out of line, and I have confidence that many of you support this attitude. What's the point of all this, anyway? Why is it so important to use this firewire code from Apple? If we're so concerned about the API, how many applications that will run under FreeBSD actually know something about that API? i.e., what's the gain here? There's already a bunch of Firewire code written for FreeBSD: http://people.freebsd.org/~simokawa/ I'd much rather see our home-grown code go into the tree than make a huge effort to gripe at Apple about their code, which has a rather restricive license anyway. They're looking to make money by licensing their source to people doing appliances and similar things that want quick and easy firewire code. We've already got a bunch of firewire code, and very little reason, I think, to even bother with the Apple code. Kobayashi-san is right, he shouldn't even risk tainting himself by looking at their intellectual property. If someone else, who isn't considering doing the work, wants to take a look at it and come up with some concrete reasons why we should pester Apple to release it under a less restrictive license, then that's fine. Given what they're evidently trying to do with the code (make it available on an evaluation basis, and then sell licenses to use it in products), it makes no sense that they would want to release it for use in FreeBSD. To release it for use in FreeBSD would require a BSD-style license, which would allow people to use it in appliances, which would eliminate Apple's revenue stream for anybody smart enough to use FreeBSD to get their code. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: src/usr.sbin/crunch/crunchgen/crunched_main.c
pmedwards The last commit to this appears to have broken it. main() was pmedwards updated to include envp, but crunched_main() calls main() pmedwards without the extra argument. pmedwards This causes make release of -current on -stable to barf for me, pmedwards so I can't truly test the patch without waiting about 8 hours, pmedwards other than to say making the modifications to the generated file pmedwards does at least allow it to compile. Thanks. Your patch does fix it and has been applied. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
On Thu, Aug 08, 2002 at 06:32:40PM +0200, John Hay scribbled: | Here is a try at a 3 floppy system. Most people should be able to | install with the first 2 floppies (kern.flp and mfsroot.flp). Just | those that need a driver on the third floppy (drivers.flp) will | need it. | | If this idea is acceptable, we should probably tweak what should | go on the second floppy and what is used the least and put that | on the last one. | | To load drivers from the drivers floppy, go to Configure and then | the last option there is Load KLD. | | The last 2 files in the diff (bld-ko.sh and driver-list.awk) are not | really needed. That is part of my attempt to create a single .ko to | save space on mfsroot.flp. But I can't get internal dependancies to | work yet. Most drivers depend on miibus and that don't get loaded | first. I just want to remind you that there are other drivers which depend on another device to work. At this time, I can think of: cardbus friends, SCSI/CAM, USB, ongoing work on IEEE1394 ACPI, and PCM(not that installing requires PCM) Cheers, Michael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
On Thu, Aug 08, 2002 at 08:27:15PM +0300, Ruslan Ermilov wrote: +CD9660 cd9660 3 options ISO 9660 Filesystem +MSDOSFSmsdosfs 3 options MSDOS filsystem +NFSCLIENT nfsclient 3 options Network Filesystem Client SYSVSHMsysvshm 2 options SYSV-style shared memory SYSVMSGsysvmsg 2 options SYSV-style message queues SYSVSEMsysvsem 2 options SYSV-style semaphores Hrm, I can probably agree on moving nfsclient.ko and msdosfs.ko to the 3rd floppy, but certainly not the cd9660 support. Why?? I disagree. CD9600 can go to the 3rd floppy -- if I am installing from floppy's I am 99.9% chance doing a network install. NFSCLIENT definitely should be on the 1st or 2nd, not 3rd floppy -- again because I am most likely doing a network install and that is the 2nd most popular network access protocol (FTP being 1st). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire support
On Thu, Aug 08, 2002 at 08:15:18PM -0600, Kenneth D. Merry wrote: Given what they're evidently trying to do with the code (make it available on an evaluation basis, and then sell licenses to use it in products), it makes no sense that they would want to release it for use in FreeBSD. To release it for use in FreeBSD would require a BSD-style license, which would allow people to use it in appliances, which would eliminate Apple's revenue stream for anybody smart enough to use FreeBSD to get their code. Me wonders why someone does email Jordan [EMAIL PROTECTED] directly to ask about this... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Compiler error XFree86-Server
On Wed, Aug 07, 2002 at 03:59:47PM +0200, Michael Nottebrock wrote: 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 Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/PEX5/ddpex/mi/level2. Anyone have a suggestion? 1.) Submit that bugreport. Why? We have a useless compiler code base for submitting bug reports from. GCC 3.1 and 3.1.1 have been released since we imported our compiler sources. GCC 3.2 should be released next week. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
On Fri, 2002-08-09 at 13:59, David O'Brien wrote: Why?? I disagree. CD9600 can go to the 3rd floppy -- if I am installing from floppy's I am 99.9% chance doing a network install. NFSCLIENT definitely should be on the 1st or 2nd, not 3rd floppy -- again because I am most likely doing a network install and that is the 2nd most popular network access protocol (FTP being 1st). Can't say that's true for me. I have to use floppies for a lot of systems because they have SCSI CD-R's in them with crappy non-BIOS patching SCSI cards. I think MSDOS installs are pretty rare and NFS ones even rarer (FTP is easier to setup) Survey time! :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Comments on Release Building for -current
On Sun, Aug 04, 2002 at 08:01:10PM +1000, Bruce Evans wrote: sorry, but some time ago I read here that gcc -O2 breaks our printf() in libc. I haven't find any assembler code in /usr/src/lib/libc/stdio/vfprintf.c, ... If someone could find the small segment of code where the optimizer screws up, and write a small program to demonstrate the problem, we would have a good chance of it getting fixed. Er, someone (Dan Lukes) has already done this. See PR 40209. It looks like this PR is against the system GCC 3.1. As such it isn't a very interesting bug report. Someone needs to test to see if this bug exists when using the gcc31 (gcc 3.1.1 release) port. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
David O'Brien wrote: Why?? I disagree. CD9600 can go to the 3rd floppy -- if I am installing from floppy's I am 99.9% chance doing a network install. I have an idea... If you only support installing via whatever option wins a vote as The One True Way, then there'll be a 100% chance that that's the way that people will install because that will be the only way that works. ... Is there a particularly good reason people should rip code out, and thereby limit FreeBSD's potential market? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
On Fri, Aug 09, 2002 at 02:12:33PM +0930 I heard the voice of Daniel O'Connor, and lo! it spake thus: I think MSDOS installs are pretty rare and NFS ones even rarer (FTP is easier to setup) I've had one recent example here where FTP wouldn't work, but NFS flew. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
On Fri, 2002-08-09 at 14:25, Matthew D. Fuller wrote: I think MSDOS installs are pretty rare and NFS ones even rarer (FTP is easier to setup) I've had one recent example here where FTP wouldn't work, but NFS flew. Weird but I can appreciate it's possible. I wasn't suggesting removing NFS install support, but giving it a lower priority as I suggest that numerically more people do FTP installs. I have no evidence to back my claim though. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
On Fri, 2002-08-09 at 14:15, Terry Lambert wrote: David O'Brien wrote: Why?? I disagree. CD9600 can go to the 3rd floppy -- if I am installing from floppy's I am 99.9% chance doing a network install. I have an idea... If you only support installing via whatever option wins a vote as The One True Way, then there'll be a 100% chance that that's the way that people will install because that will be the only way that works. ... Is there a particularly good reason people should rip code out, and thereby limit FreeBSD's potential market? Moving it to a third floppy == removing support? I don't _think_ so Tim. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Compiler error XFree86-Server
David O'Brien wrote: On Wed, Aug 07, 2002 at 03:59:47PM +0200, Michael Nottebrock wrote: 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 Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/PEX5/ddpex/mi/level2. Anyone have a suggestion? 1.) Submit that bugreport. Why? We have a useless compiler code base for submitting bug reports from. GCC 3.1 and 3.1.1 have been released since we imported our compiler sources. GCC 3.2 should be released next week. Because chances are good that the bugs still aren't fixed. I reported a bug related to optimization with -march=athlon recently and the reply I've got suggests that it's still present in all branches. I get the impression that not too many people really use gcc3 with heavy optimization on big stuff like XFree86 yet ... Of course, updating the system compiler would make bug reports from -CURRENT users even more useful. Regards, -- Michael Nottebrock And the reasons? There are no reasons. msg41707/pgp0.pgp Description: PGP signature
Re: 3 floppy system for -current releases
I think MSDOS installs are pretty rare and NFS ones even rarer (FTP is easier to setup) I've had one recent example here where FTP wouldn't work, but NFS flew. Weird but I can appreciate it's possible. I'm wondering if that was because something in our stack was bust or because of some firewall or other network thing? I wasn't suggesting removing NFS install support, but giving it a lower priority as I suggest that numerically more people do FTP installs. I have no evidence to back my claim though. I have only my own experience nad can say that I have never done a nfs install, but have done lots of ftp installs and occasionally a cd install. So should I commit the code and let us tune what go on which floppy later or should I just sit back and enjoy the ride? I'm not worried too much because the snaps on ftp.za.freebsd.org is working again. :-) ... Yes they are non-standard (they use my patch) but at least they exist, while without the patch there are no snaps. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
Hi Terry, Why?? I disagree. CD9600 can go to the 3rd floppy -- if I am installing from floppy's I am 99.9% chance doing a network install. I have an idea... If you only support installing via whatever option wins a vote as The One True Way, then there'll be a 100% chance that that's the way that people will install because that will be the only way that works. ... Is there a particularly good reason people should rip code out, and thereby limit FreeBSD's potential market? Calm down and relax. Which part of my patch removed support for anything that might be needed during the install? ... Well thinking about it again, you just might have something there. It is not as if M$ give you many options of how you want to install and still people are buying Windows at a high enough rate that Bill is pretty rich. :-) John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
On Fri, 2002-08-09 at 14:50, John Hay wrote: So should I commit the code and let us tune what go on which floppy later or should I just sit back and enjoy the ride? I'm not worried too much because the snaps on ftp.za.freebsd.org is working again. :-) ... Yes they are non-standard (they use my patch) but at least they exist, while without the patch there are no snaps. Commit it and hang the dissenters :) Since you're writing it do it the way you want. (Buy flame proof undies too) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
On Fri, Aug 09, 2002 at 07:20:53AM +0200 I heard the voice of John Hay, and lo! it spake thus: I'm wondering if that was because something in our stack was bust or because of some firewall or other network thing? I'm not sure. This was 4.6.1-RC2, across a local 100mbps LAN. The FTP server is a few month old -CURRENT; FTP would disconnect itself after fetching the first few files, and then on retry, cpio would start complaining about checksum mismatches (though I could manually ftp the files around, or check them on the server, and the checksums matched). Also after the first disconnect, using another server (such as one of the 'official' mirrors) would get the same thing. Switched to NFS, and everything ran clean through. Interestingly, I tried an experiment of just using one of the official mirrors straight up, and it went just fine (through most of the 'bin' dist, after which I stopped it). I'm presuming it's just something strange on my -CURRENT box, which wouldn't be much surprise. It IS -CURRENT, after all. So should I commit the code and let us tune what go on which floppy later or should I just sit back and enjoy the ride? It wouldn't bother me overly much to have to go to a 3rd floppy. At least, not significantly more than it already does to have to use 2 floppies ; -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Makefile.inc1 warning
Hi Ruslan, During make release I see a lot of these messages: # make: no target to make. /usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m /usr/src/shar e/mk CPUTYPE=i386 -V CPUTYPE returned non-zero status make: no target to make. /usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m /usr/src/shar e/mk CPUTYPE=i386 -V CPUTYPE returned non-zero status ## John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
John Hay wrote: Why?? I disagree. CD9600 can go to the 3rd floppy -- if I am installing from floppy's I am 99.9% chance doing a network install. [ ... ] Calm down and relax. Which part of my patch removed support for anything that might be needed during the install? ... Well thinking about it again, you just might have something there. It is not as if M$ give you many options of how you want to install and still people are buying Windows at a high enough rate that Bill is pretty rich. :-) I was complaining about David O'Brien's implicit suggestion that something was not worth worring about because of the assumption that the install was over a network. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Compiler error XFree86-Server
Because chances are good that the bugs still aren't fixed. I reported a bug related to optimization with -march=athlon recently and the reply If you've got a newer Athlon (XP) then you could compile it with -march=athlon-xp. I've filed a PR with a patch against bsd.cpu.mk (misc/41425) recently. I've got suggests that it's still present in all branches. I get the impression that not too many people really use gcc3 with heavy optimization on big stuff like XFree86 yet ... Of course, updating the XFree86 works like a charm built with -march=athlon-xp . system compiler would make bug reports from -CURRENT users even more useful. Indeed. IMHO going to 3.2 is the best we could do. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
