Subject: Re: Strange build.sh problem
To: Tom Spindler <dogcow@babymeat.com>
From: Paul Goyette <paul@whooppee.com>
List: current-users
Date: 01/25/2007 20:40:08
On Thu, 25 Jan 2007, Tom Spindler wrote:

> Do you really wish to have the same objdir for both arches?

Everything is supposed to end up in separate sub-directories anyway 
since I have OBJMACHINE=yes in my /etc/mk.conf file!  :)  From the 
mk.conf(5) man page:

 	OBJMACHINE  If defined, creates objdirs of the form obj.MACHINE,
 	            where MACHINE is the current architecture (as per
 	            `uname -m').

However, that certainly does seem to be a problem.  Even though the
build has apparently created separate obj directories, for example

quicky:cp {313} cd /usr/src/bin/cp; ls -ld obj*
lrwxrwxr-x  1 root  wheel  21 Dec 26 04:51 obj.amd64 -> /usr/obj/bin/cp.amd64
lrwxrwxr-x  1 root  wheel  20 Dec 26 06:24 obj.i386 -> /usr/obj/bin/cp.i386
quicky:cp {314}

It appears that those sym-links don't point to anywhere useful

quicky:cp {314} cd /usr/obj/bin; ls -ld cp*
drwxrwxr-x  2 root  wheel  512 Jan 25 17:51 cp
quicky:bin {315}

And in fact that single directory contains object files from the most 
recent non-update build:

quicky:bin {316} cd /usr/obj/bin ; ls cp* ; file cp/cp.o
.depend   .gdbinit  cp        cp.cat1   cp.d      cp.o      utils.d   utils.o
cp/cp.o: ELF 64-bit LSB relocatable, AMD x86-64, version 1 (SYSV), not stripped
quicky:bin {317}


So it would appear that OBJMACHINE isn't really doing much good after 
all!  Time to update my build scripts.

Thanks for the clue-by-four and making me actually look at it instead of
assuming it was working correctly.


----------------------------------------------------------------------
|   Paul Goyette   | PGP DSS Key fingerprint: |  E-mail addresses:   |
| Network Engineer | FA29 0E3B 35AF E8AE 6651 |  paul@whooppee.com   |
|                  | 0786 F758 55DE 53BA 7731 | pgoyette@juniper.net |
----------------------------------------------------------------------