Project

General

Profile

Bug #1007

env files should define MULTI_PROTO

Added by Yuri Pankov over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Rich Lowe
Category:
tools - gate/build tools
Start date:
2011-05-09
Due date:
% Done:

100%

Estimated time:
Difficulty:
Bite-size
Tags:

Description

using tools/env/illumos.sh:

Build type   is  DEBUG
WARNING: invalid value for MULTI_PROTO (); setting to "no".
[...]

History

#1

Updated by Garrett D'Amore over 8 years ago

I think it would be better to just remove MULTI_PROTO references altogether, don't you? We don't have to build bits for different kinds of delivery any more.

#2

Updated by Rich Lowe over 8 years ago

MULTI_PROTO keeps different proto areas for debug and non-debug builds, it has nothing to do with delivery of any kind. It's also very useful, don't remove it.

#3

Updated by Rich Lowe about 8 years ago

  • Difficulty changed from Medium to Bite-size
#4

Updated by Rich Lowe about 8 years ago

For the record, this only occurs because people are using nightly.sh and bldenv.sh, rather than the built copies which include stdenv.sh, in which MULTI_PROTO is defaulted for the scripts.

#5

Updated by Yuri Pankov about 8 years ago

I wonder how would I get built copy of bldenv.sh without first using the bldenv.sh to do a `dmake setup` :-) sounds like a chicken and egg problem..

#6

Updated by Rich Lowe about 8 years ago

install the onbld package (I'm going to fix the env file anyway, because it's sadly the primary means by which people discover/remember that these settings exist...)

#7

Updated by Rich Lowe about 8 years ago

  • Status changed from New to In Progress
#8

Updated by Rich Lowe about 8 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100
  • Tags deleted (needs-triage)

Resolved in r13462 commit:4d04e1a5e9ff

Also available in: Atom PDF