Project

General

Profile

Actions

Bug #1007

closed

env files should define MULTI_PROTO

Added by Yuri Pankov about 10 years ago. Updated almost 10 years ago.

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

100%

Estimated time:
Difficulty:
Bite-size
Tags:
Gerrit CR:

Description

using tools/env/illumos.sh:

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

Actions #1

Updated by Garrett D'Amore about 10 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.

Actions #2

Updated by Rich Lowe about 10 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.

Actions #3

Updated by Rich Lowe almost 10 years ago

  • Difficulty changed from Medium to Bite-size
Actions #4

Updated by Rich Lowe almost 10 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.

Actions #5

Updated by Yuri Pankov almost 10 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..

Actions #6

Updated by Rich Lowe almost 10 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...)

Actions #7

Updated by Rich Lowe almost 10 years ago

  • Status changed from New to In Progress
Actions #8

Updated by Rich Lowe almost 10 years ago

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

Resolved in r13462 commit:4d04e1a5e9ff

Actions

Also available in: Atom PDF