hi doug,

> Greetings Timo,
>
> I have had runs of build.sh work fine for me when run about every
> other day for the past few weeks.

-current does for me (mostly ;). but this is a production machine, so=20
2.0 is the way to go ;)

>  Could you please tell us the line
> which says what the build.sh command is, and what any build related
> environment variables are?  For example, I mine is done entirely
> through the build.sh arguments, and it printed the following:
>
>     =3D=3D=3D> build.sh command: ./build.sh -o -u -D /u1/destdir_200 =
-R=20
> /u1/release_200 release

mine is ./build.sh -x -j 2 -T /usr/notcroos -O /usr/obj release

(notcross because i do cross-building on this machine regularly.)

affected lines in /etc/mk.conf:

.sinclude "/usr/pkg/share/mk/cpuflags.mk"
COPTS+=3D-pipe
CFLAGS+=3D-pipe

first gives back -march=3Dpentium3 as desired.

>
> I am building into a sandbox which is initially empty, and then I use
> the contents of /u1/destdir_200 to produce a second sandbox into which
> I chroot and build my pkgsrc targets.
>
> BTW...with your message, how about we do it over in the port-i386
> list, and let folks follow the discussion over there if they are still
> interested.  Sound good?

yip, done so ;)

>
> - Doug
>
--=20
mit vorz=FCglichster Hochachtung/best regards,

Timo Sch=F6ler
//macfinity -- finest IT services | Triftstrasse 39 | 13353 Berlin |=20
Germany
Fon ++49 30 25 20 30 20 | Fax ++49 30 25 20 30 19
PGP data http://www.macfinity.net/~tis/contact/PGPPKB_timo.schoeler.txt