[-CURRENT tinderbox] failure on amd64/amd64

2003-07-13 Thread Tinderbox
TB --- 2003-07-14 05:33:47 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2003-07-14 05:33:47 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-14 05:35:32 - building world TB --- cd /

Re: Bug filing broken?

2003-07-13 Thread Kris Kennaway
On Sun, Jul 13, 2003 at 03:40:21PM -0700, Andrew P. Lentvorski, Jr. wrote: > I tried to file a bug for one of my -CURRENT machines using send-pr and > got the following result back: > > > - The following addresses had permanent fatal errors - > ><[EMAIL PROTECTED]> > >(reason: 450 :

Overdone rescue cleaning as part of buildworld?

2003-07-13 Thread Nate Lawson
It appears /rescue is cleaning for way too much as part of buildworld. For instance, groff is NOT part of /rescue (or we have other things to discuss. :) This adds a bit of time to buildworld, can it be removed? -Nate ===> rescue/rescue/texinfo/texindex rm -f .depend GPATH GRTAGS GSYMS GTAGS ==

fla.ko

2003-07-13 Thread David Yeske
I'm wondering what needs to be done to make the "fla" device into a kernel module. I made modules/fla/Makefile, but I am not sure what else needs to be done. It looks like you can't kldunload it after you kldload it... .PATH: ${.CURDIR}/../../contrib/dev/fla KMOD= fla SRCS= fla.c \

Re: Bug filing broken?

2003-07-13 Thread Jon Disnard
You might try to investigate the issue first. Try "http://www.dnsreport.com";, and see if any red flags appear in the MX record section, or in another area that might affect mail. Its a common technique to reject mail from domains that do not follow the RFC specs. Also, you might try to send wo

Re: GDB - do we dare?

2003-07-13 Thread David O'Brien
On Sun, Jul 13, 2003 at 02:28:08PM -0500, Mark Linimon wrote: > > FSF GDB releases use a libbfd that's basically a > > snapshot taken at the point where the release branch was cut. > > Hmm, seems like a motivation for a libbfd port that tracks the > snapshot, for this very reason. NO! -- -- Da

Re: GDB - do we dare?

2003-07-13 Thread David O'Brien
On Sun, Jul 13, 2003 at 05:57:34PM +0200, Mark Kettenis wrote: >Date: Sat, 12 Jul 2003 13:39:30 -0700 >From: Marcel Moolenaar <[EMAIL PROTECTED]> > >On Sat, Jul 12, 2003 at 01:05:00PM +0200, Mark Kettenis wrote: >> >>o We still have the Alpha gdb -k bug moved over from th

Re: GDB - do we dare?

2003-07-13 Thread David O'Brien
On Sat, Jul 12, 2003 at 01:05:00PM +0200, Mark Kettenis wrote: >Date: Fri, 11 Jul 2003 15:50:02 -0700 >From: Marcel Moolenaar <[EMAIL PROTECTED]> > >Gang, > >With the gcc(1) dust not even settled yet, I like to get some feedback >on gdb(1). AFAICT, this is the deal: > >o

geteuid hangs in sigsuspend

2003-07-13 Thread Kai Mosebach
Hi, when i update from 5.0-REL to 5.1-REL / 5.1-CURRENT, using a program compiled against linuxthreads, might there be a different behaviour in the geteuid function of libc ? on my sapdb port the database manager called dbmcli starts fine on 5.0-REL, on 5.1-REL/CURRENT it hangs on a sigsuspend.

HEADSUP: acpica 0619 in the tree

2003-07-13 Thread Nate Lawson
I have imported acpica 0619. I will be gone for a few hours but will be checking again tonight in case there are any problems. In particular, I am no longer sure if this patch is needed. If you do have problems, give it a try. Thanks, Nate --- nsalloc.c.old Wed May 28 10:32:31 2003 +++ n

Bug filing broken?

2003-07-13 Thread Andrew P. Lentvorski, Jr.
I tried to file a bug for one of my -CURRENT machines using send-pr and got the following result back: > - The following addresses had permanent fatal errors - ><[EMAIL PROTECTED]> >(reason: 450 : Helo command rejected: Host not found) Presumably this means that the mailer is tryin

Re: PATCH - acpi 0619

2003-07-13 Thread Nate Lawson
On Sun, 13 Jul 2003, Kevin Oberman wrote: > OK. I installed the patches on my T30 and saw no clear regressions, > although I'd like to do more testing. I did get many more errors at > boot time, all early in the operation. messages attached. These are due to lack of ECDT support which newer acpica

DDNS strangeness

2003-07-13 Thread Tom Parquette
Hi. I'm not sure if this belongs somewhere else but I'm starting here since these are 5.x systems. Please CC me on any replies. I subscribe to the digest format (makes replying difficult.) TIA. I have DDNS running between my house server and what will become an X desktop. They are both 5.x a

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread Bruce Evans
On Sun, 13 Jul 2003, Erik Trulsson wrote: > On Sun, Jul 13, 2003 at 01:37:32PM -0500, David Leimbach wrote: > > You keep saying this... where is this "must behave as two's compliment > > stated?" > > > > >(unsigned int) -1 == 0x (assuming 32-bit int). > > > > or with a valid one's com

Broadcom 5705, addendum

2003-07-13 Thread Bill Paul
Almost forgot: The BCM5705 also has a new PHY ID, which means an update to brgphy.c and miidevs is required. So, to test the 5705 driver update, do the following: - Download the files from http://www.freebsd.org/~wpaul/Broadcom/5705 - Put if_bge.c and if_bgereg.h into /sys/dev/bge - Put brgphy.c

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread Bruce Evans
On Sun, 13 Jul 2003, Marcel Moolenaar wrote: > On Sun, Jul 13, 2003 at 08:23:54AM -0500, David Leimbach wrote: > > > > This is a good policy in general, however, one could easily argue that > > what > > is trying to be determined with signedness and such being > > less-than-compared > > to 0 isn'

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread Erik Trulsson
On Sun, Jul 13, 2003 at 01:48:38PM -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > David Leimbach <[EMAIL PROTECTED]> writes: > : So for the one way conversion of signed to unsigned it will behave like > : 2's compliment > : all the time. What about back to signed? >

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread Erik Trulsson
On Sun, Jul 13, 2003 at 02:28:38PM -0500, David Leimbach wrote: > > > >C doesn't require two's compliment, but it encourages it. > > > >If you take a signed value and convert it to the corresponding > >unsigned type , the result must be equal modulo 2^N to the original > >value (where N is the num

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> David Leimbach <[EMAIL PROTECTED]> writes: : So for the one way conversion of signed to unsigned it will behave like : 2's compliment : all the time. What about back to signed? Same way. It will be reduced by the maximum value of the range plus one to

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> David Leimbach <[EMAIL PROTECTED]> writes: : : On Sunday, July 13, 2003, at 1:11PM, M. Warner Losh wrote: : : > In message: <[EMAIL PROTECTED]> : > Jilles Tjoelker <[EMAIL PROTECTED]> writes: : > : The compiler moans about (T)(-1) >= 0 as we

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> David Leimbach <[EMAIL PROTECTED]> writes: : You keep saying this... where is this "must behave as two's compliment : stated?" Read the fine print on the signed to unsigned conversion and you find that it must be done modulo 2^N. Also, I never stated t

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread David Leimbach
C doesn't require two's compliment, but it encourages it. If you take a signed value and convert it to the corresponding unsigned type , the result must be equal modulo 2^N to the original value (where N is the number of bits in the unsigned type. (Ignoring any padding bits.)) (Actually it is mod

Re: PATCH - acpi 0619

2003-07-13 Thread Kevin Oberman
> Date: Fri, 11 Jul 2003 23:07:08 -0700 (PDT) > From: Nate Lawson <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > I've prepared a new diff of the 0619 drop of acpica along with the > appropriate changes to support code: > > * Use ACPI_BUFFER as the type for AcpiGetObjectInfo > * Remove AcpiEn

Re: GDB - do we dare?

2003-07-13 Thread Mark Linimon
> FSF GDB releases use a libbfd that's basically a > snapshot taken at the point where the release branch was cut. Hmm, seems like a motivation for a libbfd port that tracks the snapshot, for this very reason. mcl ___ [EMAIL PROTECTED] mailing list htt

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread Erik Trulsson
On Sun, Jul 13, 2003 at 01:37:32PM -0500, David Leimbach wrote: > > On Sunday, July 13, 2003, at 1:23PM, M. Warner Losh wrote: > > >: > 134 #define __glibcpp_signed(T) ((T)(-1) < 0) > >: #define __glibcpp_signed(T) (!((T)(-1) > 0)) > > > >Why not the simpler: > > > >#define __glibcpp_

Call for testers: Broadcom 5705 gigabit ethernet

2003-07-13 Thread Bill Paul
While I still don't have any documentation for the BCM5705, I recently obtained a Broadcom driver with 5705 support. After scrutinizing it carefully, it looks like the differences between it and its predecessors are: - No jumbo frame support - RX return ring is limited in size to 512 entries - No

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread Stefan Farfeleder
On Sun, Jul 13, 2003 at 01:25:45PM -0500, David Leimbach wrote: > > On Sunday, July 13, 2003, at 1:11PM, M. Warner Losh wrote: > > >In message: <[EMAIL PROTECTED]> > >Jilles Tjoelker <[EMAIL PROTECTED]> writes: > >: The compiler moans about (T)(-1) >= 0 as well. Is the assumption that

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread David Leimbach
On Sunday, July 13, 2003, at 1:23PM, M. Warner Losh wrote: : > 134 #define __glibcpp_signed(T) ((T)(-1) < 0) : #define __glibcpp_signed(T) (!((T)(-1) > 0)) Why not the simpler: #define __glibcpp_signed(T) ((T)(-1) <= 0) that way we have an overlap on the range of the two types, s

Re: [acpi-jp 2415] Re: PATCH - acpi 0619

2003-07-13 Thread Nate Lawson
On Sun, 13 Jul 2003, MATOBA Hirozumi wrote: > On Fri, 11 Jul 2003 23:07:08 -0700, Nate Lawson wrote: > | I've prepared a new diff of the 0619 drop of acpica along with the > | appropriate changes to support code: > | > | * Use ACPI_BUFFER as the type for AcpiGetObjectInfo > | * Remove AcpiEnableEv

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread Marcel Moolenaar
On Sun, Jul 13, 2003 at 08:23:54AM -0500, David Leimbach wrote: > > This is a good policy in general, however, one could easily argue that > what > is trying to be determined with signedness and such being > less-than-compared > to 0 isn't really a big deal and possibly the only way to implemen

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread David Leimbach
On Sunday, July 13, 2003, at 1:11PM, M. Warner Losh wrote: In message: <[EMAIL PROTECTED]> Jilles Tjoelker <[EMAIL PROTECTED]> writes: : The compiler moans about (T)(-1) >= 0 as well. Is the assumption that : (unsigned type)(-1) is never zero valid? yes. There are no known machines wh

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread M. Warner Losh
: > 134 #define __glibcpp_signed(T) ((T)(-1) < 0) : #define __glibcpp_signed(T) (!((T)(-1) > 0)) Why not the simpler: #define __glibcpp_signed(T) ((T)(-1) <= 0) that way we have an overlap on the range of the two types, so we won't get a warning. We know for a fact that -1 != 0

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Jilles Tjoelker <[EMAIL PROTECTED]> writes: : The compiler moans about (T)(-1) >= 0 as well. Is the assumption that : (unsigned type)(-1) is never zero valid? yes. There are no known machines where -1 == 0 for types of different signs. Further, the C s

Re: IPFW and/or rc rule parsing not working since today's cvsup

2003-07-13 Thread Luigi Rizzo
thanks for pointing out -- it turns out that by mistake i have changed the handling of blank lines in ipfw configs. I will restore the old behaviour ASAP (it's a trivial 1-2 line change). cheers luigi On Sun, Jul 13, 2003 at 01:31:07PM +0100, Matt wrote: > > Matt said: >

linuxthreads not compiling

2003-07-13 Thread Kai Mosebach
Hi, - I have a 5.1-CURRENT system from 2003-July-10. - I tried to compile the linuxthreads package, but it failed. - From current.freebsd.org i downloaded the ports.tgz from 2003-July-11 - still linuxthreads isnt compiling error looks like : cc -O -pipe -mcpu=pentiumpro -mcpu=pentiumpro -g -O2

Fw: 4.8 Kernel Compiling Error

2003-07-13 Thread Travis Johnson
the error that I was receiving was due the default directory of config was ../../ and it was incorrect you must specify the FQP of the kernel you are building and then make depend will work fine.. Thanks - Original Message - From: "Travis Johnson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]

Re: Movie

2003-07-13 Thread Auto-reply from [EMAIL PROTECTED]
MY ADDRESS HAS CHANGED. PLEASE RE-SEND YOUR EMAIL AS SET FORTH BELOW: CHANGE OF ADDRESS: Due to the Receipt of a tremendous amount of SPAM, I have changed my email address. My new email address is my first name @ my web site domain name. You should know what my first name and domain name are. M

Re: GDB - do we dare?

2003-07-13 Thread Marcel Moolenaar
On Sun, Jul 13, 2003 at 05:57:34PM +0200, Mark Kettenis wrote: > >> A1 If having support for amd64 is a major reason for doing a new >>import of GDB, importing the upcoming GDB 6.0 would make more sense >>to me. > >No ia64 is the major reason :-) > > Hmm. I think I just

Re: make release of CURRENT on 4.7 box

2003-07-13 Thread Bruce Evans
On Sun, 13 Jul 2003, Tim Kientzle wrote: > Bruce Evans wrote: > > I think splitting it or making it exit after just setting variables > > in the userland case is the right fix. ... [it == newvers.sh] > > I think you're right, but don't see a very simple way to make that > work, especially given t

Re: GDB - do we dare?

2003-07-13 Thread Mark Kettenis
Date: Sat, 12 Jul 2003 13:39:30 -0700 From: Marcel Moolenaar <[EMAIL PROTECTED]> On Sat, Jul 12, 2003 at 01:05:00PM +0200, Mark Kettenis wrote: > >o We still have the Alpha gdb -k bug moved over from the 5.1 todo > list to the 5.2 todo list. I think this is "just" a b

Re: build error building cvs doc?

2003-07-13 Thread Tim Kientzle
John Reynolds wrote: [ On Sunday, July 13, Barney Wolff wrote: ] Me too. I'm about to try re-cvsupping, in case I caught some update in the middle. Somebody else asked if I was doing a "make -jN" buildworld where N > 1 and I was. So, I just now did a buildworld with one process and it finished jus

Re: make release of CURRENT on 4.7 box

2003-07-13 Thread Tim Kientzle
Bruce Evans wrote: On Sat, 12 Jul 2003, Tim Kientzle wrote: In particular, newvers.sh is being run with the current directory being ${.OBJDIR}, and ${.OBJDIR} doesn't contain a Makefile, ... ... `make -V FOO' doesn't require a Makefile in -current. ... A-HA! I don't know the "right" way to fix th

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread Jilles Tjoelker
On Sun, Jul 13, 2003 at 12:43:31AM -0400, Craig Rodrigues wrote: > The warnings seemed to be caused by this code in > /usr/include/c++/3.3/limits: > = > 630 static const int digits = __glibcpp_digits (unsigned int);

4.8 Kernel Compiling Error

2003-07-13 Thread Travis Johnson
mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/ usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/iir/../../dev/iir/iir.c /usr/src/sys/modules/iir/../../dev/iir/iir_ctrl.c /usr/src/sys/modules/iir/../../dev/iir/iir_pci.c /usr/src/sys/modules/iir/../../dev/i

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread David Leimbach
On Sunday, July 13, 2003, at 8:13AM, M. Warner Losh wrote: In message: <[EMAIL PROTECTED]> Craig Rodrigues <[EMAIL PROTECTED]> writes: : I think that this is a FreeBSD issue. I compiled : the same file under Linux, with a GCC 3.3.1 checked out on 7/11 : and did not encounter this warn

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread David Leimbach
On Saturday, July 12, 2003, at 11:05PM, Alexander Kabaev wrote: On Sat, 12 Jul 2003 23:13:12 -0400 Craig Rodrigues <[EMAIL PROTECTED]> wrote: I am guessing that the C preprocessor does not think that it is in a system header, and thus prints out the warning. We specifically disable automatic warni

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Alexander Kabaev <[EMAIL PROTECTED]> writes: : Short of fixing offending files in FSF libstdc++ or turning warning : suppression back on for standard C++ include files selectively, I have : no suggestion. In the past I know that FSF has accepted patches

Re: GCC 3.3.1, new warnings with

2003-07-13 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Craig Rodrigues <[EMAIL PROTECTED]> writes: : I think that this is a FreeBSD issue. I compiled : the same file under Linux, with a GCC 3.3.1 checked out on 7/11 : and did not encounter this warning. keep in mind that on linux the -wno-system-headers is

Re: IPFW and/or rc rule parsing not working since today's cvsup

2003-07-13 Thread MATOBA Hirozumi
ou maybe met the same situation as me. The mail that I posted to [EMAIL PROTECTED] is: <http://docs.freebsd.org/cgi/getmsg.cgi?fetch=65503+0+archive/2003/freebsd-ipfw/20030713.freebsd-ipfw> There are 3 cases for calling show_usage() in ipfw2.c. My case is caught by "if (l == 0)" in

Re: LDT entries and WINE and Threads..

2003-07-13 Thread Gerald Pfeifer
On Tue, 8 Jul 2003, Julian Elischer wrote: > I'm looking at this and I think that my interpretation is that > WINE, under FreeBSD, blindly allocates LDT entries starting at location 17, > without looking to see if they are in use already.. Do you think that's a bug in Wine, or just a Linuxism? In

Re: IPFW and/or rc rule parsing not working since today's cvsup

2003-07-13 Thread Matt
Matt said: > I normally sync to current once a week and have just done it today: > > FreeBSD tao.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Jul 13 > 12:24:40 BST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TAO > i386 > > The problem is though that it looks like IPFW or RC has changed h

IPFW and/or rc rule parsing not working since today's cvsup

2003-07-13 Thread Matt
I normally sync to current once a week and have just done it today: FreeBSD tao.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Jul 13 12:24:40 BST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TAO i386 The problem is though that it looks like IPFW or RC has changed how it works. I'm not su

Re: OpenPAM dynamic module loading not working ?

2003-07-13 Thread Dag-Erling Smorgrav
On Sun, Jul 13, 2003 at 10:11:09AM +0100, Dominic Marks wrote: > Ok, can you explain why it was trying to find the pam_get_pass symbol > which was removed from the module (by a port patch) and not mentioned in > OpenPAM? I assume OpenPAM is looking in the module, catching a stray > reference to it

Re: 5.1 RELEASE bugs?

2003-07-13 Thread Shin-ichi YOSHIMOTO
Subject: 5.1 RELEASE bugs?, On Sun, 13 Jul 2003 12:05:20 +0200 (CEST), Christer Gundersen wrote: > the word 'pentium3' dont exist in make.conf. see /usr/src/share/mk/bsd.cpu.mk -- Shin-ichi YOSHIMOTO <[EMAIL PROTECTED]> http://diary.waishi.jp/~yosimoto/diary/ ___

5.1 RELEASE bugs?

2003-07-13 Thread Christer Gundersen
Hi! I was installing 5.1 yesterday, i and think i discoverd some small bugs. COPTFLAGS is not respected when buling modules, just the kernel. when builings modules it seems to like CFLAGS better. With 'CPUTYPE=p4' and '-march=pentium4' in make.conf, when compiling something it seems to use 'cc -

Re: [acpi-jp 2412] PATCH - acpi 0619

2003-07-13 Thread MATOBA Hirozumi
On Fri, 11 Jul 2003 23:07:08 -0700, Nate Lawson wrote: | I've prepared a new diff of the 0619 drop of acpica along with the | appropriate changes to support code: | | * Use ACPI_BUFFER as the type for AcpiGetObjectInfo | * Remove AcpiEnableEvent/AcpiClearEvent for ACPI_EVENT_FIXED (power/sleep |

Re: OpenPAM dynamic module loading not working ?

2003-07-13 Thread Dominic Marks
On 13/07/2003 10:43, Dag-Erling Smorgrav wrote: > On Thu, Jul 10, 2003 at 09:26:42AM +0100, Dominic Marks wrote: > > On 10/07/2003 08:46, Dag-Erling Sm?rgrav wrote: > > > Dominic Marks <[EMAIL PROTECTED]> writes: > > > > Jul 7 22:10:40 bacon dovecot-auth: in openpam_load_module(): no pam_pgsql.so

Re: NVidia driver stability?

2003-07-13 Thread Munish Chopra
On 2003-07-13 01:47 +, Evan Dower wrote: > That may have done it. Now that I recompiled nvidia-driver only > WITH_NVIDIA_HACKS, doing glxinfo several times no longer wreaks havoc. > Since something seems to be screwy with my network driver (rtl8139) when > the kernel is compiled without opti

Re: NVidia driver stability?

2003-07-13 Thread Evan Dower
That may have done it. Now that I recompiled nvidia-driver only WITH_NVIDIA_HACKS, doing glxinfo several times no longer wreaks havoc. Since something seems to be screwy with my network driver (rtl8139) when the kernel is compiled without optimizations, I recompiled with them and so far all is

Re: OpenPAM dynamic module loading not working ?

2003-07-13 Thread Dag-Erling Smorgrav
On Thu, Jul 10, 2003 at 09:26:42AM +0100, Dominic Marks wrote: > On 10/07/2003 08:46, Dag-Erling Sm?rgrav wrote: > > Dominic Marks <[EMAIL PROTECTED]> writes: > > > Jul 7 22:10:40 bacon dovecot-auth: in openpam_load_module(): no pam_pgsql.so > > > found > > > Jul 7 22:10:40 bacon dovecot-auth:

[-CURRENT tinderbox] failure on i386/pc98

2003-07-13 Thread Tinderbox
TB --- 2003-07-13 07:14:14 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-07-13 07:14:14 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-13 07:19:12 - building world TB --- cd /home