X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7D879.F0D00E2C@onstor-exch02.onstor.net>; Mon, 6 Aug 2007 14:34:24 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: what am i doing wrong? (having trouble building in R3_0_1_rel branch)
Date: Mon, 6 Aug 2007 14:34:24 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02215951@onstor-exch02.onstor.net>
In-Reply-To: <20070806152919.496b8039@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: what am i doing wrong? (having trouble building in R3_0_1_rel branch)
Thread-Index: AcfYeTvElcW7wSTnQLCOGcAAf7OMUQAADS2A
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

No that looks correct. If your bsd tree was checked out with those
options you *should* not have problems with opensource packages wanting
to do the configure again. Unless the Makefile time-stamps and
configure/config.status time-stamps are now all the same due to a branch
creation.

-----Original Message-----
From: Andy Sharp=20
Sent: Monday, August 06, 2007 3:29 PM
To: Larry Scheer
Cc: Ken Renshaw
Subject: Re: what am i doing wrong? (having trouble building in
R3_0_1_rel branch)

Now that we have your attention Larry ~:^)

My perforce client has

Options:        noallwrite noclobber nocompress unlocked modtime normdir

Is that just sick and wrong?

This is on linux-compile, no NFS involved.  Mostly.  ~:^)

a

On Mon, 6 Aug 2007 15:22:14 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> No. A make release requires root access so it will bomb badly if the
> Build directory is on mightydog. Of course if the NFS directory is
> exported with no_root_squash then a make release will succeed.
>=20
> -----Original Message-----
> From: Ken Renshaw=20
> Sent: Monday, August 06, 2007 2:50 PM
> To: Andy Sharp; Larry Scheer
> Cc: Ed Kwan
> Subject: RE: what am i doing wrong? (having trouble building in
> R3_0_1_rel branch)
>=20
> I'm in the middle of building the same tree in prep for checking in
> some patch merges, and will verify I do not hit the error
> ( hopefully ).
>=20
> Does make release work on an NFS partition now ( assuming ~andys is
> remote )? last I knew it did not. Larry can you confirm?
>=20
> -----Original Message-----
> From: Andy Sharp
> Sent: Mon 8/6/2007 2:36 PM
> To: Larry Scheer
> Cc: Ken Renshaw; Ed Kwan
> Subject: what am i doing wrong? (having trouble building in R3_0_1_rel
> branch)
> =20
> Some build breakage, for me at least, on linux-compile building in the
> R3_0_1_rel branch.
>=20
> I'm able to build bsd, and in nfx-tree, a simple 'make' appears to
> work, but 'make release' bombs with this:
>=20
> .
> .
> .
>   Entering subdirectory libldap_r
> make[4]: Entering directory
>
`/home/andys/src/R3_0_1_rel/openbsd/src/openldap-2.2.26/build-cross/libr
> aries/libldap_r'
> ../../../build/shtool mkdir -p
> /home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib
> /bin/sh
>
/home/andys/src/R3_0_1_rel/openbsd.new/src/openldap-2.2.26/build-cross/l
> ibtool --mode=3Dinstall /usr/bin/install -c   -m 644 libldap_r.la
> /home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib
> libtool: install: warning: relinking `libldap_r.la'
> (cd
>
/home/andys/src/R3_0_1_rel/openbsd/src/openldap-2.2.26/build-cross/libra
> ries/libldap_r; /bin/sh
>
/home/andys/src/R3_0_1_rel/openbsd.new/src/openldap-2.2.26/build-cross/l
> ibtool --mode=3Drelink
> /home/andys/src/R3_0_1_rel/openbsd.new/usr/cross/pmonmips/usr/bin/gcc
> -g -O2 -release 2.2 -version-info 7:19:0 -rpath
> /home/andys/src/R3_0_1_rel/openbsd.new/usr/cross/pmonmips/usr/lib -o
> libldap_r.la threads.lo rdwr.lo tpool.lo rq.lo thr_posix.lo
> thr_cthreads.lo thr_thr.lo thr_lwp.lo thr_nt.lo thr_pth.lo thr_stub.lo
> bind.lo open.lo result.lo error.lo compare.lo search.lo controls.lo
> messages.lo references.lo extended.lo cyrus.lo modify.lo add.lo
> modrdn.lo delete.lo abandon.lo sasl.lo sbind.lo kbind.lo unbind.lo
> cancel.lo filter.lo free.lo sort.lo passwd.lo whoami.lo getdn.lo
> getentry.lo getattr.lo getvalues.lo addentry.lo request.lo os-ip.lo
> url.lo sortctrl.lo vlvctrl.lo init.lo options.lo print.lo string.lo
> util-int.lo schema.lo charray.lo tls.lo os-local.lo dnssrv.lo utf-8.lo
> utf-8-conv.lo version.lo ../../libraries/liblber/liblber.la -lkrb5
> -lc_r -lssl -lcrypto)
>=20
> *** Warning: linker path does not have real file for library -lkrb5.
> *** I have the capability to make that library automatically link in
> when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have
> *** because I did check the linker path looking for a file starting
> *** with libkrb5 and none of the candidates passed a file format test
> *** using a file magic. Last file checked: /usr/lib/libkrb5.so.3.2
>=20
> *** Warning: linker path does not have real file for library -lc_r.
> *** I have the capability to make that library automatically link in
> when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have
> *** because I did check the linker path looking for a file starting
> *** with libc_r and none of the candidates passed a file format test
> *** using a file magic. Last file checked: /usr/lib/libkrb5.so.3.2
>=20
> *** Warning: linker path does not have real file for library -lssl.
> *** I have the capability to make that library automatically link in
> when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have
> *** because I did check the linker path looking for a file starting
> *** with libssl and none of the candidates passed a file format test
> *** using a file magic. Last file checked:
> /usr/lib/../../lib/libssl.so.0.9.7a
>=20
> *** Warning: linker path does not have real file for library -lcrypto.
> *** I have the capability to make that library automatically link in
> when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have
> *** because I did check the linker path looking for a file starting
> *** with libcrypto and none of the candidates passed a file format
> test *** using a file magic. Last file checked:
> /usr/lib/../../lib/libcrypto.so.0.9.7a
> *** The inter-library dependencies that have been dropped here will be
> *** automatically added whenever a program is linked with this library
> *** or is declared to -dlopen it.
> /home/andys/src/R3_0_1_rel/openbsd.new/usr/cross/pmonmips/usr/bin/gcc
> -shared  -fPIC -o .libs/libldap_r-2.2.so.7.19  threads.lo rdwr.lo
> tpool.lo rq.lo thr_posix.lo thr_cthreads.lo thr_thr.lo thr_lwp.lo
> thr_nt.lo thr_pth.lo thr_stub.lo bind.lo open.lo result.lo error.lo
> compare.lo search.lo controls.lo messages.lo references.lo extended.lo
> cyrus.lo modify.lo add.lo modrdn.lo delete.lo abandon.lo sasl.lo
> sbind.lo kbind.lo unbind.lo cancel.lo filter.lo free.lo sort.lo
> passwd.lo whoami.lo getdn.lo getentry.lo getattr.lo getvalues.lo
> addentry.lo request.lo os-ip.lo url.lo sortctrl.lo vlvctrl.lo init.lo
> options.lo print.lo string.lo util-int.lo schema.lo charray.lo tls.lo
> os-local.lo dnssrv.lo utf-8.lo utf-8-conv.lo version.lo
>
/home/andys/src/R3_0_1_rel/openbsd.new/usr/cross/pmonmips/usr/lib/liblbe
> r.so.7.19  -Wl,-soname,libldap_r-2.2.so.7.19 -Wl,-R/usr/lib
> /usr/bin/install -c -m 644 .libs/libldap_r-2.2.so.7.19T
>
/home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib/libldap
> _r-2.2.so.7.19
> (cd /home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib
> && rm -f libldap_r.so.7.19 && ln -s libldap_r-2.2.so.7.19
> libldap_r.so.7.19)
> /usr/bin/install -c -m 644 .libs/libldap_r.lai
>
/home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib/libldap
> _r.la
> /usr/bin/install -c -m 644 .libs/libldap_r.a
>
/home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib/libldap
> _r.a
>
/home/andys/src/R3_0_1_rel/openbsd.new/usr/cross/pmonmips/usr/bin/ranlib
> -t
>
/home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib/libldap
> _r.a
> chmod 644
>
/home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib/libldap
> _r.a
> libtool: install: warning: remember to run `libtool --finish
> /home/andys/src/R3_0_1_rel/openbsd.new/usr/cross/pmonmips/usr/lib'
> /bin/sh
>
/home/andys/src/R3_0_1_rel/openbsd.new/src/openldap-2.2.26/build-cross/l
> ibtool --mode=3Dfinish
> /home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib
> PATH=3D"$PATH:/sbin" ldconfig -m
> /home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib
> ldconfig: invalid option -- m
> Try `ldconfig --help' or `ldconfig --usage' for more information.
> ----------------------------------------------------------------------
> Libraries have been installed in:
>    /home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib
>=20
> If you ever happen to want to link against installed libraries
> in a given directory, LIBDIR, you must either use libtool, and
> specify the full pathname of the library, or use the `-LLIBDIR'
> flag during linking and do at least one of the following:
>    - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
>      during execution
>    - use the `-Wl,-rpath,LIBDIR' linker flag
>    - have your system administrator run these commands:
>        PATH=3D"$PATH:/sbin" ldconfig -m
> /home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release/usr/lib
>    - have your system administrator add LIBDIR to `/etc/ld.so.conf'
>=20
> See any operating system documentation about shared libraries for
> more information, such as the ld(1) and ld.so(8) manual pages.
> ----------------------------------------------------------------------
> make[4]: Leaving directory
>
`/home/andys/src/R3_0_1_rel/openbsd/src/openldap-2.2.26/build-cross/libr
> aries/libldap_r'
> =20
>   Entering subdirectory librewrite
> make[4]: Entering directory
>
`/home/andys/src/R3_0_1_rel/openbsd/src/openldap-2.2.26/build-cross/libr
> aries/librewrite'
> make[4]: Nothing to be done for `install'.
> make[4]: Leaving directory
>
`/home/andys/src/R3_0_1_rel/openbsd/src/openldap-2.2.26/build-cross/libr
> aries/librewrite'
> =20
> make[3]: Leaving directory
>
`/home/andys/src/R3_0_1_rel/openbsd/src/openldap-2.2.26/build-cross/libr
> aries'
> =20
> make[2]: Leaving directory
> `/home/andys/src/R3_0_1_rel/openbsd/src/openldap-2.2.26/build-cross'
> cd openbsd.new/src/libxml2-2.6.20/build-cross && \
> sudo make install
> DESTDIR=3D/home/andys/src/R3_0_1_rel/nfx-tree/Build/bc/dbg/Release
> CROSSDIR=3D""
> make[2]: Entering directory
> `/home/andys/src/R3_0_1_rel/openbsd/src/libxml2-2.6.20/build-cross'
>  cd .. && /bin/sh /mnt/bsd-mipsel/libxml2-2.6.20/missing --run
> automake-1.9 --gnu=20
> Makefile.am: required file `./COPYING' not found
> make[2]: *** [../Makefile.in] Error 1
> make[2]: Leaving directory
> `/home/andys/src/R3_0_1_rel/openbsd/src/libxml2-2.6.20/build-cross'
> make[1]: *** [bsd-distr-xml2] Error 2
> make[1]: Leaving directory `/home/andys/src/R3_0_1_rel'
> make: *** [bsd-release] Error 2
> linux-compile:/home/andys/src/R3_0_1_rel/nfx-tree$=20
>=20
