Blame - README-builds.html - platform/libcore

2007-12-01 00:00:00 +0000

[diff] [blame]

1

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

2

<html>

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

3

<head>

4

<title>OpenJDK Build README</title>

5

</head>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

6

7

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

8

Kelly O'Hair

2008-09-17 13:30:32 -0700

[diff] [blame]

9

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

10

<tr>

11

Kelly O'Hair

634c79b

2008-07-09 15:42:00 -0700

[diff] [blame]

12

<img alt="OpenJDK"

13

src="http://openjdk.java.net/images/openjdk.png"

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

14

width=256>

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

</td>

</tr>

<tr>

<h1>OpenJDK Build README</h1>

20

</td>

21

</tr>

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

22

</table>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

23

24

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

25

<hr>

26

<h2><a name="introduction">Introduction</a></h2>

27

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

28

This README file contains build instructions for the

29

<a href="http://openjdk.java.net" target="_blank">OpenJDK</a>.

30

Building the source code for the

31

OpenJDK

32

requires

33

a certain degree of technical expertise.

34

35

36

<h3>!!!!!!!!!!!!!!! THIS IS A MAJOR RE-WRITE of this document. !!!!!!!!!!!!!</h3>

Some Headlines:

<ul>

<li>

The build is now a "<code>configure && make</code>" style build

42

</li>

43

<li>

44

Any GNU make 3.81 or newer should work

45

</li>

46

<li>

47

The build should scale, i.e. more processors should

48

cause the build to be done in less wall-clock time

49

</li>

50

<li>

51

Nested or recursive make invocations have been significantly

52

reduced, as has the total fork/exec or spawning

53

of sub processes during the build

54

</li>

55

<li>

56

Windows MKS usage is no longer supported

57

</li>

58

<li>

59

Windows Visual Studio <code>vsvars*.bat</code> and

60

<code>vcvars*.bat</code> files are run automatically

61

</li>

62

<li>

63

Ant is no longer used when building the OpenJDK

64

</li>

65

<li>

66

Use of ALT_* environment variables for configuring the

67

build is no longer supported

68

</li>

69

</ul>

70

</blockquote>

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

71

</blockquote>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

72

73

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

74

<hr>

75

<h2><a name="contents">Contents</a></h2>

76

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

77

<ul>

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

78

<li><a href="#introduction">Introduction</a></li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

79

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

80

<li><a href="#hg">Use of Mercurial</a>

81

<ul>

82

<li><a href="#get_source">Getting the Source</a></li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

83

<li><a href="#repositories">Repositories</a></li>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

84

</ul>

85

</li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

86

87

<li><a href="#building">Building</a>

Kelly O'Hair

2008-09-17 13:30:32 -0700

[diff] [blame]

88

<ul>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

89

<li><a href="#setup">System Setup</a>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

90

<ul>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

91

<li><a href="#linux">Linux</a></li>

92

<li><a href="#solaris">Solaris</a></li>

93

94

<li><a href="#windows">Windows</a></li>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

95

</ul>

96

</li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

97

<li><a href="#configure">Configure</a></li>

98

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

99

</ul>

100

</li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

101

<li><a href="#testing">Testing</a></li>

</ul>

<hr>

<ul>

<li><a href="#hints">Appendix A: Hints and Tips</a>

106

<ul>

107

108

<li><a href="#performance">Build Performance Tips</a></li>

109

<li><a href="#troubleshooting">Troubleshooting</a></li>

110

</ul>

111

</li>

112

<li><a href="#gmake">Appendix B: GNU Make Information</a></li>

113

<li><a href="#buildenvironments">Appendix C: Build Environments</a></li>

114

115

<!-- Leave out

116

<li><a href="#mapping">Appendix D: Mapping Old Builds to the New Builds</a></li>

117

-->

118

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

119

</ul>

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

120

</blockquote>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

121

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

122

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

123

<hr>

124

<h2><a name="hg">Use of Mercurial</a></h2>

125

126

The OpenJDK sources are maintained with the revision control system

127

<a href="http://mercurial.selenic.com/wiki/Mercurial">Mercurial</a>.

128

If you are new to Mercurial, please see the

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

129

130

Beginner Guides</a>

131

or refer to the <a href="http://hgbook.red-bean.com/">

132

Mercurial Book</a>.

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

133

The first few chapters of the book provide an excellent overview of

134

Mercurial, what it is and how it works.

135

<br>

136

For using Mercurial with the OpenJDK refer to the

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

137

138

Developer Guide: Installing and Configuring Mercurial</a>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

139

section for more information.

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

140

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

141

<h3><a name="get_source">Getting the Source</a></h3>

142

143

To get the entire set of OpenJDK Mercurial repositories

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

144

use the script <code>get_source.sh</code> located in the

145

root repository:

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

146

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

147

<code>

148

hg clone http://hg.openjdk.java.net/jdk8/jdk8

149

<i>YourOpenJDK</i>

150

<br>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

151

cd <i>YourOpenJDK</i>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

<br>

bash ./get_source.sh

</code>

</blockquote>

Once you have all the repositories, keep in mind that each

Erik Joelsson

2013-08-26 13:43:27 +0200

[diff] [blame^]

157

repository is its own independent repository.

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

158

You can also re-run <code>./get_source.sh</code> anytime to

159

pull over all the latest changesets in all the repositories.

160

This set of nested repositories has been given the term

161

"forest" and there are various ways to apply the same

162

<code>hg</code> command to each of the repositories.

163

For example, the script <code>make/scripts/hgforest.sh</code>

164

can be used to repeat the same <code>hg</code>

165

command on every repository, e.g.

166

167

<code>

168

cd <i>YourOpenJDK</i>

169

<br>

170

bash ./make/scripts/hgforest.sh status

171

</code>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

172

</blockquote>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

173

</blockquote>

174

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

175

<h3><a name="repositories">Repositories</a></h3>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

176

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

177

<p>The set of repositories and what they contain:</p>

<thead>

<tr>

<th>Repository</th>

<th>Contains</th>

</tr>

</thead>

<tbody>

<tr>

<td>

. (root)

</td>

<td>

common configure and makefile logic

</td>

</tr>

<tr>

<td>

hotspot

</td>

<td>

source code and make files for building

200

the OpenJDK Hotspot Virtual Machine

</td>

</tr>

<tr>

<td>

langtools

</td>

<td>

source code for the OpenJDK javac and language tools

</td>

</tr>

<tr>

<td>

jdk

</td>

<td>

source code and make files for building

217

the OpenJDK runtime libraries and misc files

</td>

</tr>

<tr>

<td>

jaxp

</td>

<td>

source code for the OpenJDK JAXP functionality

</td>

</tr>

<tr>

<td>

jaxws

</td>

<td>

source code for the OpenJDK JAX-WS functionality

</td>

</tr>

<tr>

<td>

corba

</td>

<td>

source code for the OpenJDK Corba functionality

242

</td>

243

</tr>

Erik Joelsson

2013-08-26 13:43:27 +0200

[diff] [blame^]

<tr>

<td>

nashorn

</td>

<td>

source code for the OpenJDK JavaScript implementation

250

</td>

251

</tr>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

252

</tbody>

253

</table>

Kelly O'Hair

2008-09-17 13:30:32 -0700

[diff] [blame]

254

</blockquote>

Dalibor Topic

73e9e34

2009-09-23 20:06:01 +0200

[diff] [blame]

255

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

256

<h3><a name="guidelines">Repository Source Guidelines</a></h3>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

257

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

258

There are some very basic guidelines:

Kelly O'Hair

2008-09-17 13:30:32 -0700

[diff] [blame]

259

<ul>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

260

<li>

261

Use of whitespace in source files

262

(.java, .c, .h, .cpp, and .hpp files)

263

is restricted.

264

No TABs, no trailing whitespace on lines, and files

265

should not terminate in more than one blank line.

266

</li>

267

<li>

268

Files with execute permissions should not be added

269

to the source repositories.

270

</li>

271

<li>

272

All generated files need to be kept isolated from

273

the files

274

maintained or managed by the source control system.

275

The standard area for generated files is the top level

276

<code>build/</code> directory.

277

</li>

278

<li>

279

The default build process should be to build the product

280

and nothing else, in one form, e.g. a product (optimized),

281

debug (non-optimized, -g plus assert logic), or

282

fastdebug (optimized, -g plus assert logic).

283

</li>

284

<li>

285

The <tt>.hgignore</tt> file in each repository

286

must exist and should

287

include <tt>^build/</tt>, <tt>^dist/</tt> and

288

optionally any

289

<tt>nbproject/private</tt> directories.

290

<strong>It should NEVER</strong> include

291

anything in the

292

293

or any managed directory area of a repository.

294

</li>

295

<li>

296

Directory names and file names should never contain

297

blanks or

298

non-printing characters.

299

</li>

300

<li>

301

Generated source or binary files should NEVER be added to

302

the repository (that includes <tt>javah</tt> output).

303

There are some exceptions to this rule, in particular

304

with some of the generated configure scripts.

305

</li>

306

<li>

307

Files not needed for typical building

308

or testing of the repository

309

should not be added to the repository.

310

</li>

Kelly O'Hair

2008-09-17 13:30:32 -0700

[diff] [blame]

311

</ul>

312

</blockquote>

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

313

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

314

</blockquote>

315

316

317

<hr>

318

<h2><a name="building">Building</a></h2>

319

320

The very first step in building the OpenJDK is making sure the

321

system itself has everything it needs to do OpenJDK builds.

322

Once a system is setup, it generally doesn't need to be done again.

323

<br>

324

Building the OpenJDK is now done with running a

325

<a href="#configure"><code>configure</code></a>

326

script which will try and find and verify you have everything

327

you need, followed by running

328

<a href="#gmake"><code>make</code></a>, e.g.

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

329

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

<b>

<code>

bash ./configure<br>

make all

</code>

</b>

</blockquote>

Where possible the <code>configure</code> script will attempt to located the

338

various components in the default locations or via component

339

specific variable settings.

340

When the normal defaults fail or components cannot be found,

341

additional <code>configure</code> options may be necessary to help <code>configure</code>

342

find the necessary tools for the build, or you may need to

343

re-visit the setup of your system due to missing software

344

packages.

345

<br>

346

<strong>NOTE:</strong> The <code>configure</code> script

347

file does not have

348

execute permissions and will need to be explicitly run with

349

<code>bash</code>,

350

see the <a href="#guidelines">source guidelines</a>.

351

352

353

<hr>

354

<h3><a name="setup">System Setup</a></h3>

355

356

Before even attempting to use a system to build the OpenJDK

357

there are some very basic system setups needed.

For all systems:

<ul>

<li>

Be sure the GNU make utility is version 3.81 or newer,

362

e.g. run "<code>make -version</code>"

363

</li>

364

<li>

365

Install a

Stuart Marks

e1dd752

2013-06-18 17:18:46 -0700

[diff] [blame]

366

<a name="bootjdk">Bootstrap JDK</a>.

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

367

All OpenJDK builds require access to a previously released

Stuart Marks

e1dd752

2013-06-18 17:18:46 -0700

[diff] [blame]

368

JDK called the <i>bootstrap JDK</i> or <i>boot JDK.</i>

369

The general rule is that the bootstrap JDK

370

must be an instance of the previous major

371

release of the JDK. In addition, there may be

372

a requirement to use a release at or beyond a

373

particular update level.

374

375

376

<b><i>Building JDK 8 requires use of a version

377

of JDK 7 that is at Update 7 or newer. JDK 8

378

developers should not use JDK 8 as the boot

379

JDK, to ensure that JDK 8 dependencies are

380

not introduced into the parts of the system

381

that are built with JDK 7.</i></b>

382

383

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

384

The JDK 7 binaries can be downloaded from Oracle's

385

<a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html"

386

target="_blank">JDK 7 download site</a>.

387

For build performance reasons

388

is very important that this bootstrap JDK be made available

389

on the local disk of the machine doing the build.

390

You should add its <code>bin</code> directory

391

to the <code>PATH</code> environment variable.

392

If <code>configure</code> has any issues finding this JDK, you may

393

need to use the <code>configure</code> option

394

<code>--with-boot-jdk</code>.

395

</li>

396

<li>

Erik Joelsson

2013-08-26 13:43:27 +0200

[diff] [blame^]

397

Ensure that GNU make, the Bootstrap JDK,

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

398

and the compilers are all

399

in your PATH environment variable

400

</li>

401

</ul>

402

And for specific systems:

<thead>

<tr>

<th>Linux</th>

<th>Solaris</th>

<th>Windows</th>

</tr>

</thead>

<tbody>

<tr>

<td>

Install all the software development

416

packages needed including

417

<a href="#alsa">alsa</a>,

418

<a href="#freetype">freetype</a>,

419

<a href="#cups">cups</a>, and

420

<a href="#xrender">xrender</a>.

421

<br>

422

See

423

<a href="#SDBE">specific system packages</a>.

424

</td>

425

<td>

426

Install all the software development

427

packages needed including

428

<a href="#studio">Studio Compilers</a>,

429

<a href="#freetype">freetype</a>,

430

<a href="#cups">cups</a>, and

431

<a href="#xrender">xrender</a>.

432

<br>

433

See

434

<a href="#SDBE">specific system packages</a>.

</td>

<td>

<ul>

<li>

Install one of

<a href="#cygwin">CYGWIN</a> or

441

<a href="#msys">MinGW/MSYS</a>

</li>

<li>

Install

<a href="#vs2010">Visual Studio 2010</a>

</li>

<li>

Install the

<a href="#dxsdk">Microsoft DirectX SDK</a>

</li>

</ul>

</td>

<td>

Install

<a href="https://developer.apple.com/xcode/">XCode 4.5.2</a>

456

and also install the "Command line tools" found under the

457

preferences pane "Downloads"

</td>

</tr>

</tbody>

</table>

<h4><a name="linux">Linux</a></h4>

464

465

With Linux, try and favor the system packages over

466

building your own

467

or getting packages from other areas.

468

Most Linux builds should be possible with the system's

469

available packages.

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

470

<br>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

471

Note that some Linux systems have a habit of pre-populating

472

your environment variables for you, for example <code>JAVA_HOME</code>

473

might get pre-defined for you to refer to the JDK installed on

474

your Linux system.

475

You will need to unset <code>JAVA_HOME</code>.

476

It's a good idea to run <code>env</code> and verify the

477

environment variables you are getting from the default system

478

settings make sense for building the OpenJDK.

</blockquote>

<h4><a name="solaris">Solaris</a></h4>

483

484

<h5><a name="studio">Studio Compilers</a></h5>

At a minimum, the

Studio 12 Update 1 Compilers</a>

489

(containing version 5.10 of the C and C++ compilers) is required,

490

including specific patches.

491

<p>

492

The Solaris SPARC patch list is:

493

<ul>

494

<li>

495

118683-05: SunOS 5.10: Patch for profiling libraries and assembler

496

</li>

497

<li>

498

119963-21: SunOS 5.10: Shared library patch for C++

499

</li>

500

<li>

501

120753-08: SunOS 5.10: Microtasking libraries (libmtsk) patch

502

</li>

503

<li>

504

128228-09: Sun Studio 12 Update 1: Patch for Sun C++ Compiler

505

</li>

506

<li>

507

141860-03: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95

508

</li>

509

<li>

510

141861-05: Sun Studio 12 Update 1: Patch for Sun C Compiler

511

</li>

512

<li>

513

142371-01: Sun Studio 12.1 Update 1: Patch for dbx

514

</li>

515

<li>

516

143384-02: Sun Studio 12 Update 1: Patch for debuginfo handling

517

</li>

518

<li>

519

143385-02: Sun Studio 12 Update 1: Patch for Compiler Common patch for Sun C C++ F77 F95

520

</li>

521

<li>

522

142369-01: Sun Studio 12.1: Patch for Performance Analyzer Tools

</li>

</ul>

<p>

The Solaris X86 patch list is:

527

<ul>

528

<li>

529

119961-07: SunOS 5.10_x86, x64, Patch for profiling libraries and assembler

530

</li>

531

<li>

532

119964-21: SunOS 5.10_x86: Shared library patch for C++_x86

533

</li>

534

<li>

535

120754-08: SunOS 5.10_x86: Microtasking libraries (libmtsk) patch

536

</li>

537

<li>

538

141858-06: Sun Studio 12 Update 1_x86: Sun Compiler Common patch for x86 backend

539

</li>

540

<li>

541

128229-09: Sun Studio 12 Update 1_x86: Patch for C++ Compiler

542

</li>

543

<li>

544

142363-05: Sun Studio 12 Update 1_x86: Patch for C Compiler

545

</li>

546

<li>

547

142368-01: Sun Studio 12.1_x86: Patch for Performance Analyzer Tools

</li>

</ul>

<p>

Place the <code>bin</code> directory in <code>PATH</code>.

552

<p>

553

The Oracle Solaris Studio Express compilers at:

554

555

Oracle Solaris Studio Express Download site</a>

556

are also an option, although these compilers have not

557

been extensively used yet.

558

</blockquote>

559

560

</blockquote>

561

562

<h4><a name="windows">Windows</a></h4>

563

564

565

<h5><a name="toolkit">Windows Unix Toolkit</a></h5>

566

567

Building on Windows requires a Unix-like environment, notably a

568

Unix-like shell.

569

There are several such environments available of which

570

<a href="http://www.cygwin.com/">Cygwin</a> and

571

<a href="http://www.mingw.org/wiki/MSYS">MinGW/MSYS</a> are

572

currently supported for

573

the OpenJDK build. One of the differences of these

574

systems from standard Windows tools is the way

575

they handle Windows path names, particularly path names which contain

576

spaces, backslashes as path separators and possibly drive letters.

577

Depending

578

on the use case and the specifics of each environment these path

579

problems can

580

be solved by a combination of quoting whole paths, translating

581

backslashes to

582

forward slashes, escaping backslashes with additional backslashes and

583

translating the path names to their

"8.3" version</a>.

<h6><a name="cygwin">CYGWIN</a></h6>

588

589

CYGWIN is an open source, Linux-like environment which tries to emulate

590

a complete POSIX layer on Windows. It tries to be smart about path names

591

and can usually handle all kinds of paths if they are correctly quoted

592

or escaped although internally it maps drive letters <code><drive>:</code>

593

to a virtual directory <code>/cygdrive/<drive></code>.

594

<p>

595

You can always use the <code>cygpath</code> utility to map pathnames with spaces

596

or the backslash character into the <code>C:/</code> style of pathname

597

(called 'mixed'), e.g. <code>cygpath -s -m "<i>path</i>"</code>.

598

</p>

599

<p>

600

Note that the use of CYGWIN creates a unique problem with regards to

601

setting <a href="#path"><code>PATH</code></a>. Normally on Windows

602

the <code>PATH</code> variable contains directories

603

separated with the ";" character (Solaris and Linux use ":").

604

With CYGWIN, it uses ":", but that means that paths like "C:/path"

605

cannot be placed in the CYGWIN version of <code>PATH</code> and

606

instead CYGWIN uses something like <code>/cygdrive/c/path</code>

607

which CYGWIN understands, but only CYGWIN understands.

608

</p>

609

<p>

610

The OpenJDK build requires CYGWIN version 1.7.16 or newer.

611

Information about CYGWIN can

612

be obtained from the CYGWIN website at

613

<a href="http://www.cygwin.com" target="_blank">www.cygwin.com</a>.

614

</p>

615

<p>

616

By default CYGWIN doesn't install all the tools required for building

617

the OpenJDK.

618

Along with the default installation, you need to install

the following tools.

<thead>

<tr>

<td>Binary Name</td>

<td>Category</td>

<td>Package</td>

<td>Description</td>

</tr>

</thead>

<tbody>

<tr>

<td>Devel</td>

<td>binutils</td>

<td>

The GNU assembler, linker and binary utilities

</td>

</tr>

<tr>

<td>Devel</td>

<td>

The GNU version of the 'make' utility built for CYGWIN

</td>

</tr>

<tr>

<td>Interpreters</td>

650

651

<td>

652

GNU implementation of the traditional Unix macro

processor

</td>

</tr>

<tr>

<td>Utils</td>

<td>

A program to manage archives of files

</td>

</tr>

<tr>

<td>Utils</td>

<td>

Pattern-directed scanning and processing language

</td>

</tr>

<tr>

<td>Utils</td>

<td>

Determines file type using 'magic' numbers

</td>

</tr>

<tr>

<td>Archive</td>

<td>

Package and compress (archive) files

</td>

</tr>

<tr>

<td>unzip.exe</td>

<td>Archive</td>

<td>unzip</td>

<td>

Extract compressed files in a ZIP archive

</td>

</tr>

<tr>

<td>System</td>

<td>procps</td>

<td>

Display amount of free and used memory in the system

</td>

</tr>

</tbody>

</table>

</blockquote>

Note that the CYGWIN software can conflict with other non-CYGWIN

708

software on your Windows system.

709

CYGWIN provides a

710

<a href="http://cygwin.com/faq/faq.using.html" target="_blank">FAQ</a> for

711

known issues and problems, of particular interest is the

712

section on

713

714

BLODA (applications that interfere with CYGWIN)</a>.

715

</blockquote>

716

717

<h6><a name="msys">MinGW/MSYS</a></h6>

718

719

MinGW ("Minimalist GNU for Windows") is a collection of free Windows

720

specific header files and import libraries combined with GNU toolsets that

721

allow one to produce native Windows programs that do not rely on any

722

3rd-party C runtime DLLs. MSYS is a supplement to MinGW which allows building

723

applications and programs which rely on traditional UNIX tools to

724

be present. Among others this includes tools like <code>bash</code>

725

and <code>make</code>.

726

See <a href="http://www.mingw.org/wiki/MSYS" target="_blank">MinGW/MSYS</a>

727

for more information.

728

<p>

729

Like Cygwin, MinGW/MSYS can handle different types of path formats. They

730

are internally converted to paths with forward slashes and drive letters

731

<code><drive>:</code> replaced by a virtual

732

directory <code>/<drive></code>. Additionally, MSYS automatically

733

detects binaries compiled for the MSYS environment and feeds them with the

734

internal, Unix-style path names. If native Windows applications are called

735

from within MSYS programs their path arguments are automatically converted

736

back to Windows style path names with drive letters and backslashes as

737

path separators. This may cause problems for Windows applications which

738

use forward slashes as parameter separator (e.g. <code>cl /nologo /I</code>)

739

because MSYS may wrongly <a href="http://mingw.org/wiki/Posix_path_conversion">

740

replace such parameters by drive letters</a>.

741

</p>

742

<p>

743

In addition to the tools which will be installed

744

by default, you have

745

to manually install the

746

<code>msys-zip</code> and

747

<code>msys-unzip</code> packages.

748

This can be easily done with the MinGW command line installer:

749

750

<code>mingw-get.exe install msys-zip</code>

751

<br>

752

<code>mingw-get.exe install msys-unzip</code>

</blockquote>

</blockquote>

</blockquote>

<h5><a name="vs2010">Visual Studio 2010 Compilers</a></h5>

759

760

<p>

761

The 32-bit and 64-bit OpenJDK Windows build requires

762

Microsoft Visual Studio C++ 2010 (VS2010) Professional

763

Edition or Express compiler.

764

The compiler and other tools are expected to reside

765

in the location defined by the variable

766

<code>VS100COMNTOOLS</code> which

767

is set by the Microsoft Visual Studio installer.

768

</p>

769

<p>

770

Only the C++ part of VS2010 is needed.

771

Try to let the installation go to the default

772

install directory.

773

Always reboot your system after installing VS2010.

774

The system environment variable VS100COMNTOOLS

775

should be

776

set in your environment.

777

</p>

778

<p>

779

Make sure that TMP and TEMP are also set

780

in the environment

781

and refer to Windows paths that exist,

782

like <code>C:\temp</code>,

783

not <code>/tmp</code>, not <code>/cygdrive/c/temp</code>,

784

and not <code>C:/temp</code>.

785

<code>C:\temp</code> is just an example,

786

it is assumed that this area is

787

private to the user, so by default

788

after installs you should

789

see a unique user path in these variables.

</p>

</blockquote>

</blockquote>

Make sure you get the right XCode version.

799

</blockquote>

</blockquote>

804

<hr>

805

<h3><a name="configure">Configure</a></h3>

806

807

The basic invocation of the <code>configure</code> script

808

looks like:

809

810

<b><code>bash ./configure [<i>options</i>]</code></b>

811

</blockquote>

812

This will create an output directory containing the

813

"configuration" and setup an area for the build result.

814

This directory typically looks like:

815

816

<b><code>build/linux-x64-normal-server-release</code></b>

817

</blockquote>

818

<code>configure</code> will try to figure out what system you are running on

819

and where all necessary build components are.

820

If you have all prerequisites for building installed,

821

it should find everything.

822

If it fails to detect any component automatically,

823

it will exit and inform you about the problem.

824

When this happens, read more below in

825

<a href="#configureoptions">the <code>configure</code> options</a>.

<p>

Some examples:

</p>

<thead>

<tr>

<th>Description</th>

<th>Configure Command Line</th>

</tr>

</thead>

<tbody>

<tr>

<td>Windows 32bit build with freetype specified</td>

839

<td>

840

<code>bash ./configure --with-freetype=/cygdrive/c/freetype-i586 --with-target-bits=32</code>

</td>

</tr>

<tr>

<td>Debug 64bit Build</td>

845

<td>

846

<code>bash ./configure --enable-debug --with-target-bits=64</code>

</td>

</tr>

</tbody>

</table>

853

<h4><a name="configureoptions">Configure Options</a></h4>

854

855

Complete details on all the OpenJDK <code>configure</code> options can

856

be seen with:

857

858

<b><code>bash ./configure --help=short</code></b>

859

</blockquote>

860

Use <code>-help</code> to see all the <code>configure</code> options

861

available.

862

863

You can generate any number of different configurations,

864

e.g. debug, release, 32, 64, etc.

865

866

Some of the more commonly used <code>configure</code> options are:

<thead>

<tr>

<th width="300">OpenJDK Configure Option</th>

<th>Description</th>

</tr>

</thead>

<tbody>

<tr>

<td><b><code>--enable-debug</code></b></td>

878

<td>

879

set the debug level to fastdebug (this is a shorthand for

880

<code>--with-debug-level=fastdebug</code>)

</td>

</tr>

<tr>

<td>

select the location of the

887

<a name="alsa">Advanced Linux Sound Architecture (ALSA)</a>

888

<br>

889

Version 0.9.1 or newer of the ALSA files are

890

required for building the OpenJDK on Linux.

891

These Linux files are usually available from an "alsa"

892

of "libasound"

893

development package,

894

and it's highly recommended that you try and use

895

the package provided by the particular version of Linux that

you are using.

</td>

</tr>

<tr>

<td>

select the <a href="#bootjdk">Bootstrap JDK</a>

</td>

</tr>

<tr>

<td><b><code>--with-boot-jdk-jvmargs=</code></b>"<i>args</i>"</td>

907

<td>

908

provide the JVM options to be used to run the

909

<a href="#bootjdk">Bootstrap JDK</a>

</td>

</tr>

<tr>

<td><b><code>--with-cacerts=</code></b><i>path</i></td>

914

<td>

915

select the path to the cacerts file.

916

<br>

917

See <a href="http://en.wikipedia.org/wiki/Certificate_Authority" target="_blank">

918

http://en.wikipedia.org/wiki/Certificate_Authority</a>

919

for a better understanding of the Certificate Authority (CA).

920

A certificates file named "cacerts"

921

represents a system-wide keystore with CA certificates.

922

In JDK and JRE

923

binary bundles, the "cacerts" file contains root CA certificates from

924

several public CAs (e.g., VeriSign, Thawte, and Baltimore).

925

The source contain a cacerts file

926

without CA root certificates.

927

Formal JDK builders will need to secure

928

permission from each public CA and include the certificates into their

929

own custom cacerts file.

930

Failure to provide a populated cacerts file

931

will result in verification errors of a certificate chain during runtime.

932

By default an empty cacerts file is provided and that should be

933

fine for most JDK developers.

</td>

</tr>

<tr>

<td>

select the CUPS install location

940

<br>

941

The

942

<a name="cups">Common UNIX Printing System (CUPS) Headers</a>

943

are required for building the

944

OpenJDK on Solaris and Linux.

945

The Solaris header files can be obtained by installing

946

the package <strong>SFWcups</strong> from the Solaris Software

947

Companion CD/DVD, these often will be installed into the

948

directory <code>/opt/sfw/cups</code>.

949

<br>

950

The CUPS header files can always be downloaded from

951

<a href="http://www.cups.org" target="_blank">www.cups.org</a>.

</td>

</tr>

<tr>

<td><b><code>--with-cups-include=</code></b><i>path</i></td>

956

<td>

957

select the CUPS include directory location

</td>

</tr>

<tr>

<td><b><code>--with-debug-level=</code></b><i>level</i></td>

962

<td>

963

select the debug information level of release,

964

fastdebug, or slowdebug

</td>

</tr>

<tr>

<td>

select location of the compiler install or

971

developer install location

</td>

</tr>

<tr>

<td><b><code>--with-dxsdk=</code></b><i>path</i></td>

976

<td>

977

select location of the Windows Direct X SDK install

978

<br>

979

The <a name="dxsdk">Microsoft DirectX 9.0 SDK</a>

980

header files and libraries

981

from the Summer 2004 edition

982

are required for building OpenJDK.

983

This SDK can be downloaded from

984

985

Microsoft DirectX 9.0 SDK (Summer 2004)</a>.

986

If the link above becomes obsolete, the SDK can be found from

987

<a href="http://download.microsoft.com" target="_blank">the Microsoft Download Site</a>

988

(search with "DirectX 9.0 SDK Update Summer 2004").

989

Installation usually will set the environment variable

990

<code>DXSDK_DIR</code> to it's install location.

</td>

</tr>

<tr>

<td><b><code>--with-freetype=</code></b><i>path</i></td>

995

<td>

996

select the freetype files to use.

997

<br>

998

Expecting the

999

<a name="freetype">freetype</a> libraries under

1000

<code>lib/</code> and the

1001

headers under <code>include/</code>.

1002

<br>

1003

Version 2.3 or newer of FreeType is required.

1004

On Unix systems required files can be available as part of your

1005

distribution (while you still may need to upgrade them).

1006

Note that you need development version of package that

1007

includes both the FreeType library and header files.

1008

<br>

1009

You can always download latest FreeType version from the

1010

<a href="http://www.freetype.org" target="_blank">FreeType website</a>.

1011

<br>

1012

Building the freetype 2 libraries from scratch is also possible,

1013

however on Windows refer to the

1014

1015

Windows FreeType DLL build instructions</a>.

1016

<br>

1017

Note that by default FreeType is built with byte code hinting

1018

support disabled due to licensing restrictions.

1019

In this case, text appearance and metrics are expected to

1020

differ from Sun's official JDK build.

1021

See

1022

1023

the SourceForge FreeType2 Home Page

1024

</a>

1025

for more information.

</td>

</tr>

<tr>

<td><b><code>--with-import-hotspot=</code></b><i>path</i></td>

1030

<td>

1031

select the location to find hotspot

1032

binaries from a previous build to avoid building

hotspot

</td>

</tr>

<tr>

<td><b><code>--with-target-bits=</code></b><i>arg</i></td>

1038

<td>

1039

select 32 or 64 bit build

</td>

</tr>

<tr>

<td><b><code>--with-jvm-variants=</code></b><i>variants</i></td>

1044

<td>

1045

select the JVM variants to build from, comma

1046

separated list that can include:

1047

server, client, kernel, zero and zeroshark

</td>

</tr>

<tr>

<td><b><code>--with-memory-size=</code></b><i>size</i></td>

1052

<td>

1053

select the RAM size that GNU make will think

this system has

</td>

</tr>

<tr>

<td><a name="msvcrNN"><b><code>--with-msvcr-dll=</code></b><i>path</i></a></td>

1059

<td>

1060

select the <code>msvcr100.dll</code>

1061

file to include in the

1062

Windows builds (C/C++ runtime library for

1063

Visual Studio).

1064

<br>

1065

This is usually picked up automatically

1066

from the redist

1067

directories of Visual Studio 2010.

</td>

</tr>

<tr>

<td><b><code>--with-num-cores=</code></b><i>cores</i></td>

1072

<td>

1073

select the number of cores to use (processor

count or CPU count)

</td>

</tr>

<tr>

<td>

select the location of the X11 and xrender files.

1081

<br>

1082

The

1083

<a name="xrender">XRender Extension Headers</a>

1084

are required for building the

1085

OpenJDK on Solaris and Linux.

1086

<br>

1087

The Linux header files are usually available from a "Xrender"

1088

development package, it's recommended that you try and use

1089

the package provided by the particular distribution of Linux that

1090

you are using.

1091

<br>

1092

The Solaris XRender header files is

1093

included with the other X11 header files

1094

in the package <strong>SFWxwinc</strong>

1095

on new enough versions of

1096

Solaris and will be installed in

1097

<code>/usr/X11/include/X11/extensions/Xrender.h</code> or

1098

<code>/usr/openwin/share/include/X11/extensions/Xrender.h</code>

</td>

</tr>

</tbody>

</table>

</blockquote>

</blockquote>

<hr>

The basic invocation of the <code>make</code> utility

looks like:

</blockquote>

This will start the build to the output directory containing the

1117

"configuration" that was created by the <code>configure</code>

1118

script. Run <code>make help</code> for more information on

1119

the available targets.

1120

<br>

1121

There are some of the make targets that

1122

are of general interest:

<thead>

<tr>

<th>Make Target</th>

<th>Description</th>

</tr>

</thead>

<tbody>

<tr>

<td><i>empty</i></td>

1133

<td>build everything but no images</td>

</tr>

<tr>

<td>build everything including images</td>

</tr>

<tr>

<td>build all configurations</td>

1142

</tr>

1143

<tr>

1144

<td><b><code>images</code></b></td>

1145

<td>create complete j2sdk and j2re images</td>

1146

</tr>

1147

<tr>

1148

<td><b><code>install</code></b></td>

1149

<td>install the generated images locally,

1150

typically in <code>/usr/local</code></td>

1151

</tr>

1152

<tr>

1153

<td><b><code>clean</code></b></td>

1154

<td>remove all files generated by make,

1155

but not those generated by <code>configure</code></td>

1156

</tr>

1157

<tr>

1158

<td><b><code>dist-clean</code></b></td>

1159

<td>remove all files generated by both

1160

and <code>configure</code> (basically killing the configuration)</td>

</tr>

<tr>

<td>give some help on using <code>make</code>,

1165

including some interesting make targets</td>

</tr>

</tbody>

</table>

</blockquote>

</blockquote>

1173

<hr>

1174

<h2><a name="testing">Testing</a></h2>

1175

1176

When the build is completed, you should see the generated

1177

binaries and associated files in the <code>j2sdk-image</code>

1178

directory in the output directory.

1179

In particular, the

1180

<code>build/<i>*</i>/images/j2sdk-image/bin</code>

1181

directory should contain executables for the

1182

OpenJDK tools and utilities for that configuration.

1183

The testing tool <code>jtreg</code> will be needed

and can be found at:

the jtreg site</a>.

The provided regression tests in the repositories

1188

can be run with the command:

1189

1190

<code><b>cd test && make PRODUCT_HOME=`pwd`/../build/*/images/j2sdk-image all</b></code>

</blockquote>

</blockquote>

1195

1196

1197

1198

1199

1200

1201

1202

1203

1204

1205

<hr>

1206

<h2><a name="hints">Appendix A: Hints and Tips</a></h2>

<p>

<b>Q:</b> The <code>configure</code> file looks horrible!

1214

How are you going to edit it?

1215

<br>

1216

<b>A:</b> The <code>configure</code> file is generated (think

1217

"compiled") by the autoconf tools. The source code is

1218

in <code>configure.ac</code> various .m4 files in common/autoconf,

1219

which are

1220

much more readable.

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1221

</p>

1222

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1223

<p>

1224

1225

Why is the <code>configure</code> file checked in,

if it is generated?

<br>

If it was not generated, every user would need to have the autoconf

1230

tools installed, and re-generate the <code>configure</code> file

1231

as the first step.

1232

Our goal is to minimize the work needed to be done by the user

1233

to start building OpenJDK, and to minimize

1234

the number of external dependencies required.

</p>

<p>

Do you require a specific version of autoconf for regenerating

1240

<code>configure</code>?

1241

<br>

1242

1243

Currently, no, but this will likely be the case when things have

1244

settled down a bit more. (The reason for this is to avoid

1245

large spurious changes in <code>configure</code>

1246

in commits that made small changes to <code>configure.ac</code>).

</p>

<p>

What are the files in <code>common/makefiles/support/*</code> for?

1252

They look like gibberish.

1253

<br>

1254

1255

They are a somewhat ugly hack to compensate for command line length

1256

limitations on certain platforms (Windows, Solaris).

1257

Due to a combination of limitations in make and the shell,

1258

command lines containing too many files will not work properly.

1259

These

1260

helper files are part of an elaborate hack that will compress the

1261

command line in the makefile and then uncompress it safely.

1262

We're

1263

not proud of it, but it does fix the problem.

1264

If you have any better suggestions, we're all ears! :-)

</p>

<p>

I want to see the output of the commands that make runs,

1270

like in the old build. How do I do that?

1271

<br>

1272

1273

You specify the <code>LOG</code> variable to make. There are

1274

several log levels:

1275

</p>

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1276

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1277

<ul>

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1278

<li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1279

<b><code>warn</code></b> — Default and very quiet.

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1280

</li>

1281

<li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1282

<b><code>info</code></b> — Shows more progress information

1283

than warn.

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1284

</li>

1285

<li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1286

<b><code>debug</code></b> — Echos all command lines and

1287

prints all macro calls for compilation definitions.

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1288

</li>

1289

<li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1290

<b><code>trace</code></b> — Echos all $(shell) command

1291

lines as well.

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1292

</li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1293

</ul>

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1294

</blockquote>

1295

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1296

<p>

1297

1298

When do I have to re-run <code>configure</code>?

1299

<br>

1300

1301

Normally you will run <code>configure</code> only once for creating a

1302

configuration.

1303

You need to re-run configuration only if you want to change any

1304

configuration options,

1305

or if you pull down changes to the <code>configure</code> script.

</p>

<p>

I have added a new source file. Do I need to modify the makefiles?

1311

<br>

1312

1313

Normally, no. If you want to create e.g. a new native

1314

library,

1315

you will need to modify the makefiles. But for normal file

1316

additions or removals, no changes are needed. There are certan

1317

exceptions for some native libraries where the source files are spread

Erik Joelsson

2013-08-26 13:43:27 +0200

[diff] [blame^]

1318

over many directories which also contain sources for other

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1319

libraries. In these cases it was simply easier to create include lists

Erik Joelsson

2013-08-26 13:43:27 +0200

[diff] [blame^]

1320

rather than excludes.

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

</p>

<p>

When I run <code>configure --help</code>, I see many strange options,

1326

like <code>--dvidir</code>. What is this?

1327

<br>

1328

1329

Configure provides a slew of options by default, to all projects

1330

that use autoconf. Most of them are not used in OpenJDK,

1331

so you can safely ignore them. To list only OpenJDK specific features,

1332

use <code>configure --help=short</code> instead.

</p>

<p>

<code>configure</code> provides OpenJDK-specific features such as

Erik Joelsson

2013-08-26 13:43:27 +0200

[diff] [blame^]

1338

<code>--with-builddeps-server</code> that are not

1339

described in this document. What about those?

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1340

<br>

1341

1342

Try them out if you like! But be aware that most of these are

1343

experimental features.

1344

Many of them don't do anything at all at the moment; the option

Erik Joelsson

2013-08-26 13:43:27 +0200

[diff] [blame^]

1345

is just a placeholder. Others depend on

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1346

pieces of code or infrastructure that is currently

1347

not ready for prime time.

</p>

<p>

How will you make sure you don't break anything?

1353

<br>

1354

1355

We have a script that compares the result of the new build system

1356

with the result of the old. For most part, we aim for (and achieve)

1357

byte-by-byte identical output. There are however technical issues

1358

with e.g. native binaries, which might differ in a byte-by-byte

1359

comparison, even

1360

when building twice with the old build system.

1361

For these, we compare relevant aspects

1362

(e.g. the symbol table and file size).

1363

Note that we still don't have 100%

1364

equivalence, but we're close.

</p>

<p>

I noticed this thing X in the build that looks very broken by design.

1370

Why don't you fix it?

1371

<br>

1372

1373

Our goal is to produce a build output that is as close as

1374

technically possible to the old build output.

1375

If things were weird in the old build,

1376

they will be weird in the new build.

1377

Often, things were weird before due to obscurity,

1378

but in the new build system the weird stuff comes up to the surface.

1379

The plan is to attack these things at a later stage,

1380

after the new build system is established.

</p>

<p>

The code in the new build system is not that well-structured.

Will you fix this?

<br>

Yes! The new build system has grown bit by bit as we converted

1390

the old system. When all of the old build system is converted,

1391

we can take a step back and clean up the structure of the new build

1392

system. Some of this we plan to do before replacing the old build

1393

system and some will need to wait until after.

1394

</p>

1395

1396

<p>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1397

1398

Is anything able to use the results of the new build's default make target?

1399

<br>

1400

1401

Yes, this is the minimal (or roughly minimal)

1402

set of compiled output needed for a developer to actually

1403

execute the newly built JDK. The idea is that in an incremental

1404

development fashion, when doing a normal make,

1405

you should only spend time recompiling what's changed

1406

(making it purely incremental) and only do the work that's

1407

needed to actually run and test your code.

1408

The packaging stuff that is part of the <code>images</code>

1409

target is not needed for a normal developer who wants to

1410

test his new code. Even if it's quite fast, it's still unnecessary.

1411

We're targeting sub-second incremental rebuilds! ;-)

1412

(Or, well, at least single-digit seconds...)

</p>

<p>

I usually set a specific environment variable when building,

1418

but I can't find the equivalent in the new build.

What should I do?

<br>

Erik Joelsson

2013-08-26 13:43:27 +0200

[diff] [blame^]

1422

It might very well be that we have neglected to add support for

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1423

an option that was actually used from outside the build system.

Erik Joelsson

2013-08-26 13:43:27 +0200

[diff] [blame^]

1424

Email us and we will add support for it!

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1425

</p>

1426

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1427

</blockquote>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1428

1429

<h3><a name="performance">Build Performance Tips</a></h3>

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1430

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1431

1432

<p>Building OpenJDK requires a lot of horsepower.

1433

Some of the build tools can be adjusted to utilize more or less

1434

of resources such as

1435

parallel threads and memory.

1436

The <code>configure</code> script analyzes your system and selects reasonable

1437

values for such options based on your hardware.

1438

If you encounter resource problems, such as out of memory conditions,

1439

you can modify the detected values with:</p>

<ul>

<li>

<b><code>--with-num-cores</code></b>

1444

—

1445

number of cores in the build system,

1446

e.g. <code>--with-num-cores=8</code>

1447

</li>

1448

<li>

1449

<b><code>--with-memory-size</code></b>

1450

— memory (in MB) available in the build system,

1451

e.g. <code>--with-memory-size=1024</code>

</li>

</ul>

<p>It might also be necessary to specify the JVM arguments passed

1456

to the Bootstrap JDK, using e.g.

1457

<code>--with-boot-jdk-jvmargs="-Xmx8G -enableassertions"</code>.

1458

Doing this will override the default JVM arguments

1459

passed to the Bootstrap JDK.</p>

1460

1461

1462

<p>One of the top goals of the new build system is to improve the

1463

build performance and decrease the time needed to build. This will

1464

soon also apply to the java compilation when the Smart Javac wrapper

1465

is making its way into jdk8. It can be tried in the build-infra

1466

repository already. You are likely to find that the new build system

1467

is faster than the old one even without this feature.</p>

1468

1469

<p>At the end of a successful execution of <code>configure</code>,

1470

you will get a performance summary,

1471

indicating how well the build will perform. Here you will

1472

also get performance hints.

1473

If you want to build fast, pay attention to those!</p>

1474

1475

<h4>Building with ccache</h4>

1476

1477

<p>A simple way to radically speed up compilation of native code

1478

(typically hotspot and native libraries in JDK) is to install

1479

ccache. This will cache and reuse prior compilation results, if the

1480

source code is unchanged. However, ccache versions prior to 3.1.4

1481

does not work correctly with the precompiled headers used in

1482

OpenJDK. So if your platform supports ccache at 3.1.4 or later, we

1483

highly recommend installing it. This is currently only supported on

1484

linux.</p>

1485

1486

<h4>Building on local disk</h4>

1487

1488

<p>If you are using network shares, e.g. via NFS, for your source code,

1489

make sure the build directory is situated on local disk.

1490

The performance

1491

penalty is extremely high for building on a network share,

1492

close to unusable.</p>

1493

1494

<h4>Building only one JVM</h4>

1495

1496

<p>The old build builds multiple JVMs on 32-bit systems (client and

1497

server; and on Windows kernel as well). In the new build we have

1498

changed this default to only build server when it's available. This

1499

improves build times for those not interested in multiple JVMs. To

1500

mimic the old behavior on platforms that support it,

1501

use <code>--with-jvm-variants=client,server</code>.</p>

1502

1503

<h4>Selecting the number of cores to build on</h4>

1504

1505

<p>By default, <code>configure</code> will analyze your machine and run the make

1506

process in parallel with as many threads as you have cores. This

1507

behavior can be overridden, either "permanently" (on a <code>configure</code>

1508

basis) using <code>--with-num-cores=N</code> or for a single build

1509

only (on a make basis), using <code>make JOBS=N</code>.</p>

1510

1511

<p>If you want to make a slower build just this time, to save some CPU

1512

power for other processes, you can run

1513

e.g. <code>make JOBS=2</code>. This will force the makefiles

1514

to only run 2 parallel processes, or even <code>make JOBS=1</code>

1515

which will disable parallelism.</p>

1516

1517

<p>If you want to have it the other way round, namely having slow

1518

builds default and override with fast if you're

1519

impatient, you should call <code>configure</code> with

1520

<code>--with-num-cores=2</code>, making 2 the default.

1521

If you want to run with more

1522

cores, run <code>make JOBS=8</code></p>

1523

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

1524

</blockquote>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1525

1526

<h3><a name="troubleshooting">Troubleshooting</a></h3>

1527

1528

1529

<h4>Solving build problems</h4>

1530

1531

1532

If the build fails (and it's not due to a compilation error in

1533

a source file you've changed), the first thing you should do

1534

is to re-run the build with more verbosity.

1535

Do this by adding <code>LOG=debug</code> to your make command line.

1536

<br>

1537

The build log (with both stdout and stderr intermingled,

1538

basically the same as you see on your console) can be found as

1539

<code>build.log</code> in your build directory.

1540

<br>

1541

You can ask for help on build problems with the new build system

on either the

build-dev</a>

or the

build-infra-dev</a>

mailing lists. Please include the relevant parts

1549

of the build log.

1550

<br>

1551

A build can fail for any number of reasons.

1552

Most failures

1553

are a result of trying to build in an environment in which all the

1554

pre-build requirements have not been met.

1555

The first step in

1556

troubleshooting a build failure is to recheck that you have satisfied

1557

all the pre-build requirements for your platform.

1558

Scanning the <code>configure</code> log is a good first step, making

1559

sure that what it found makes sense for your system.

1560

Look for strange error messages or any difficulties that

1561

<code>configure</code> had in finding things.

1562

<br>

1563

Some of the more common problems with builds are briefly

1564

described

1565

below, with suggestions for remedies.

1566

<ul>

1567

<li>

1568

<b>Corrupted Bundles on Windows:</b>

1569

1570

Some virus scanning software has been known to

1571

corrupt the

1572

downloading of zip bundles.

1573

It may be necessary to disable the 'on access' or

1574

'real time'

1575

virus scanning features to prevent this corruption.

1576

This type of "real time" virus scanning can also

1577

slow down the

1578

build process significantly.

1579

Temporarily disabling the feature, or excluding the build

1580

output directory may be necessary to get correct and

faster builds.

</blockquote>

</li>

<li>

<b>Slow Builds:</b>

If your build machine seems to be overloaded from too many

1588

simultaneous C++ compiles, try setting the

1589

<code>JOBS=1</code> on the <code>make</code> command line.

1590

Then try increasing the count slowly to an acceptable

1591

level for your system. Also:

1592

1593

Creating the javadocs can be very slow,

1594

if you are running

1595

javadoc, consider skipping that step.

1596

<br>

1597

Faster CPUs, more RAM, and a faster DISK usually helps.

1598

The VM build tends to be CPU intensive

1599

(many C++ compiles),

1600

and the rest of the JDK will often be disk intensive.

1601

<br>

1602

Faster compiles are possible using a tool called

1603

<a href="http://ccache.samba.org/" target="_blank">ccache</a>.

</blockquote>

</blockquote>

</li>

<li>

<b>File time issues:</b>

1609

1610

If you see warnings that refer to file time stamps, e.g.

1611

1612

<i>Warning message:</i><code>

1613

File `xxx' has modification time in

1614

the future.</code>

1615

<br>

1616

<i>Warning message:</i> <code> Clock skew detected.

1617

Your build may

1618

be incomplete.</code>

1619

</blockquote>

1620

These warnings can occur when the clock on the build

1621

machine is out of

1622

sync with the timestamps on the source files.

1623

Other errors, apparently

1624

unrelated but in fact caused by the clock skew,

1625

can occur along with

1626

the clock skew warnings.

1627

These secondary errors may tend to obscure the

1628

fact that the true root cause of the problem

1629

is an out-of-sync clock.

1630

<p>

1631

If you see these warnings, reset the clock on the

1632

build

1633

machine, run "<code><i>gmake</i> clobber</code>"

1634

or delete the directory

1635

containing the build output, and restart the

1636

build from the beginning.

</blockquote>

</li>

<li>

<b>Error message:

<code>Trouble writing out table to disk</code></b>

1642

1643

Increase the amount of swap space on your build machine.

1644

This could be caused by overloading the system and

1645

it may be necessary to use:

</blockquote>

to reduce the load on the system.

</blockquote>

</li>

<li>

<b>Error Message:

<code>libstdc++ not found:</code></b>

1655

1656

This is caused by a missing libstdc++.a library.

1657

This is installed as part of a specific package

1658

(e.g. libstdc++.so.devel.386).

1659

By default some 64-bit Linux versions (e.g. Fedora)

1660

only install the 64-bit version of the libstdc++ package.

1661

Various parts of the JDK build require a static

1662

link of the C++ runtime libraries to allow for maximum

1663

portability of the built images.

</blockquote>

</li>

<li>

<b>Linux Error Message:

1668

<code>cannot restore segment prot after reloc</code></b>

1669

1670

This is probably an issue with SELinux (See

1671

1672

http://en.wikipedia.org/wiki/SELinux</a>).

1673

Parts of the VM is built without the <code>-fPIC</code> for

1674

performance reasons.

1675

<p>

1676

To completely disable SELinux:

1677

<ol>

1678

1679

<li><code># system-config-securitylevel</code></li>

1680

<li><code>In the window that appears, select the SELinux tab</code></li>

1681

<li><code>Disable SELinux</code></li>

1682

</ol>

1683

<p>

1684

Alternatively, instead of completely disabling it you could

1685

disable just this one check.

1686

<ol>

1687

<li>Select System->Administration->SELinux Management</li>

1688

<li>In the SELinux Management Tool which appears,

1689

select "Boolean" from the menu on the left</li>

1690

<li>Expand the "Memory Protection" group</li>

1691

<li>Check the first item, labeled

1692

"Allow all unconfined executables to use

1693

libraries requiring text relocation ..."</li>

</ol>

</blockquote>

</li>

<li>

<b>Windows Error Messages:</b>

1699

<br>

1700

<code>*** fatal error - couldn't allocate heap, ... </code>

1701

<br>

1702

<code>rm fails with "Directory not empty"</code>

1703

<br>

1704

<code>unzip fails with "cannot create ... Permission denied"</code>

1705

<br>

1706

<code>unzip fails with "cannot create ... Error 50"</code>

1707

<br>

1708

1709

The CYGWIN software can conflict with other non-CYGWIN

1710

software. See the CYGWIN FAQ section on

1711

1712

BLODA (applications that interfere with CYGWIN)</a>.

</blockquote>

</li>

<li>

<b>Windows Error Message: <code>spawn failed</code></b>

1717

1718

Try rebooting the system, or there could be some kind of

1719

issue with the disk or disk partition being used.

1720

Sometimes it comes with a "Permission Denied" message.

</blockquote>

</li>

</ul>

</blockquote>

</blockquote>

1727

1728

</blockquote>

1729

1730

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1731

<hr>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1732

<h2><a name="gmake">Appendix B: GNU make</a></h2>

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

1733

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1734

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1735

The Makefiles in the OpenJDK are only valid when used with the

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1736

GNU version of the utility command <code>make</code>

1737

(usually called <code>gmake</code> on Solaris).

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1738

A few notes about using GNU make:

1739

<ul>

1740

<li>

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1741

You need GNU make version 3.81 or newer.

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1742

If the GNU make utility on your systems is not

1743

3.81 or newer,

1744

see <a href="#buildgmake">"Building GNU make"</a>.

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1745

</li>

1746

<li>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1747

Place the location of the GNU make binary in the

1748

<code>PATH</code>.

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1749

</li>

1750

<li>

1751

<strong>Solaris:</strong>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1752

Do NOT use <code>/usr/bin/make</code> on Solaris.

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1753

If your Solaris system has the software

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1754

from the Solaris Developer Companion CD installed,

1755

you should try and use <code>gmake</code>

1756

which will be located in either the

1757

<code>/usr/bin</code>, <code>/opt/sfw/bin</code> or

1758

<code>/usr/sfw/bin</code> directory.

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1759

</li>

1760

<li>

1761

<strong>Windows:</strong>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1762

Make sure you start your build inside a bash shell.

</li>

<li>

The XCode "command line tools" must be installed on your Mac.

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1767

</li>

1768

</ul>

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

1769

<p>

Kelly O'Hair

2010-12-22 12:25:52 -0800

[diff] [blame]

1770

Information on GNU make, and access to ftp download sites, are

available on the

GNU make web site

</a>.

The latest source to GNU make is available at

1776

1777

ftp.gnu.org/pub/gnu/make/</a>.

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1778

</p>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1779

1780

<h3><a name="buildgmake">Building GNU make</a></h3>

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1781

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1782

First step is to get the GNU make 3.81 or newer source from

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1783

1784

ftp.gnu.org/pub/gnu/make/</a>.

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1785

Building is a little different depending on the OS but is

1786

basically done with:

1787

1788

<code>bash ./configure</code>

1789

<br>

1790

1791

</blockquote>

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

1792

</blockquote>

Edvard Wendelin

1f736c8

2012-05-03 14:17:30 +0200

[diff] [blame]

1793

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1794

</blockquote>

1795

1796

Edvard Wendelin

1f736c8

2012-05-03 14:17:30 +0200

[diff] [blame]

1797

<hr>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1798

<h2><a name="buildenvironments">Appendix C: Build Environments</a></h2>

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1799

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1800

1801

<h3><a name="MBE">Minimum Build Environments</a></h3>

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

1802

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1803

This file often describes specific requirements for what we

1804

call the

1805

"minimum build environments" (MBE) for this

1806

specific release of the JDK.

1807

What is listed below is what the Oracle Release

1808

Engineering Team will use to build the Oracle JDK product.

1809

Building with the MBE will hopefully generate the most compatible

1810

bits that install on, and run correctly on, the most variations

1811

of the same base OS and hardware architecture.

1812

In some cases, these represent what is often called the

1813

least common denominator, but each Operating System has different

1814

aspects to it.

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

1815

<p>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1816

In all cases, the Bootstrap JDK version minimum is critical,

1817

we cannot guarantee builds will work with older Bootstrap JDK's.

1818

Also in all cases, more RAM and more processors is better,

1819

the minimums listed below are simply recommendations.

1820

<p>

1821

With Solaris and Mac OS X, the version listed below is the

1822

oldest release we can guarantee builds and works, and the

1823

specific version of the compilers used could be critical.

1824

<p>

1825

With Windows the critical aspect is the Visual Studio compiler

1826

used, which due to it's runtime, generally dictates what Windows

1827

systems can do the builds and where the resulting bits can

1828

be used.<br>

1829

<b>NOTE: We expect a change here off these older Windows OS releases

1830

and to a 'less older' one, probably Windows 2008R2 X64.</b>

1831

<p>

1832

With Linux, it was just a matter of picking a

1833

stable distribution that is a good representative for Linux

1834

in general.<br>

1835

<b>NOTE: We expect a change here from Fedora 9 to something else,

1836

but it has not been completely determined yet, possibly

1837

Ubuntu 12.04 X64, unbiased community feedback would be welcome on

1838

what a good choice would be here.</b>

1839

<p>

1840

It is understood that most developers will NOT be using these

1841

specific versions, and in fact creating these specific versions

1842

may be difficult due to the age of some of this software.

1843

It is expected that developers are more often using the more

1844

recent releases and distributions of these operating systems.

1845

<p>

1846

Compilation problems with newer or different C/C++ compilers is a

1847

common problem.

1848

Similarly, compilation problems related to changes to the

1849

<code>/usr/include</code> or system header files is also a

1850

common problem with older, newer, or unreleased OS versions.

1851

Please report these types of problems as bugs so that they

1852

can be dealt with accordingly.

</p>

<thead>

<tr>

<th>Base OS and Architecture</th>

1858

1859

<th>C/C++ Compiler</th>

1860

<th>Bootstrap JDK</th>

<th>Processors</th>

<th>RAM Minimum</th>

<th>DISK Needs</th>

</tr>

</thead>

<tbody>

<tr>

<td>Linux X86 (32-bit) and X64 (64-bit)</td>

<td>Fedora 9</td>

</tr>

<tr>

<td>Solaris SPARC (32-bit) and SPARCV9 (64-bit)</td>

1878

<td>Solaris 10 Update 6</td>

1879

<td>Studio 12 Update 1 + patches</td>

</tr>

<tr>

<td>Solaris X86 (32-bit) and X64 (64-bit)</td>

1887

<td>Solaris 10 Update 6</td>

1888

<td>Studio 12 Update 1 + patches</td>

</tr>

<tr>

<td>Windows X86 (32-bit)</td>

1896

<td>Windows XP</td>

1897

<td>Microsoft Visual Studio C++ 2010 Professional Edition</td>

</tr>

<tr>

<td>Windows X64 (64-bit)</td>

1905

<td>Windows Server 2003 - Enterprise x64 Edition</td>

1906

<td>Microsoft Visual Studio C++ 2010 Professional Edition</td>

</tr>

<tr>

<td>XCode 4.5.2 or newer</td>

</tr>

</tbody>

</table>

J. Duke

2007-12-01 00:00:00 +0000

[diff] [blame]

1923

</blockquote>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1924

1925

1926

<hr>

1927

<h3><a name="SDBE">Specific Developer Build Environments</a></h3>

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

1928

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

1929

We won't be listing all the possible environments, but

1930

we will try to provide what information we have available to us.

1931

<p>

1932

<strong>NOTE: The community can help out by updating

1933

this part of the document.

1934

</strong>

1935

1936

<h4><a name="fedora">Fedora</a></h4>

1937

1938

After installing the latest

1939

<a href="http://fedoraproject.org">Fedora</a>

1940

you need to install several build dependencies.

1941

The simplest way to do it is to execute the

1942

following commands as user <code>root</code>:

1943

1944

<code>yum-builddep java-1.7.0-openjdk</code>

1945

<br>

1946

<code>yum install gcc gcc-c++</code>

1947

</blockquote>

1948

<p>

1949

In addition, it's necessary to set a few environment

1950

variables for the build:

1951

1952

<code>export LANG=C</code>

1953

<br>

1954

<code>export PATH="/usr/lib/jvm/java-openjdk/bin:${PATH}"</code>

</blockquote>

</blockquote>

<h4><a name="centos">CentOS 5.5</a></h4>

1960

1961

After installing

1962

<a href="http://www.centos.org/">CentOS 5.5</a>

1963

you need to make sure you have

1964

the following Development bundles installed:

1965

1966

<ul>

1967

<li>Development Libraries</li>

1968

<li>Development Tools</li>

1969

<li>Java Development</li>

1970

<li>X Software Development (Including XFree86-devel)</li>

</ul>

</blockquote>

<p>

Plus the following packages:

1975

1976

<ul>

1977

<li>cups devel: Cups Development Package</li>

1978

<li>alsa devel: Alsa Development Package</li>

1979

<li>Xi devel: libXi.so Development Package</li>

</ul>

</blockquote>

<p>

The freetype 2.3 packages don't seem to be available,

1984

but the freetype 2.3 sources can be downloaded, built,

1985

and installed easily enough from

1986

1987

the freetype site</a>.

1988

Build and install with something like:

1989

1990

<code>bash ./configure</code>

<br>

<br>

<code>sudo -u root make install</code>

1995

</blockquote>

1996

<p>

1997

Mercurial packages could not be found easily, but a Google

1998

search should find ones, and they usually include Python if

it's needed.

</blockquote>

<h4><a name="debian">Debian 5.0 (Lenny)</a></h4>

2003

2004

After installing <a href="http://debian.org">Debian</a> 5

2005

you need to install several build dependencies.

2006

The simplest way to install the build dependencies is to

2007

execute the following commands as user <code>root</code>:

2008

2009

<code>aptitude build-dep openjdk-7</code>

2010

<br>

2011

<code>aptitude install openjdk-7-jdk libmotif-dev</code>

2012

</blockquote>

2013

<p>

2014

In addition, it's necessary to set a few environment

2015

variables for the build:

2016

2017

<code>export LANG=C</code>

2018

<br>

2019

<code>export PATH="/usr/lib/jvm/java-7-openjdk/bin:${PATH}"</code>

</blockquote>

</blockquote>

<h4><a name="ubuntu">Ubuntu 12.04</a></h4>

2024

2025

After installing <a href="http://ubuntu.org">Ubuntu</a> 12.04

2026

you need to install several build dependencies. The simplest

2027

way to do it is to execute the following commands:

2028

2029

<code>sudo aptitude build-dep openjdk-7</code>

2030

<br>

2031

<code>sudo aptitude install openjdk-7-jdk</code>

2032

</blockquote>

2033

<p>

2034

In addition, it's necessary to set a few environment

2035

variables for the build:

2036

2037

<code>export LANG=C</code>

2038

<br>

2039

<code>export PATH="/usr/lib/jvm/java-7-openjdk/bin:${PATH}"</code>

</blockquote>

</blockquote>

<h4><a name="opensuse">OpenSUSE 11.1</a></h4>

2044

2045

After installing <a href="http://opensuse.org">OpenSUSE</a> 11.1

2046

you need to install several build dependencies.

2047

The simplest way to install the build dependencies is to

2048

execute the following commands:

2049

2050

<code>sudo zypper source-install -d java-1_7_0-openjdk</code>

2051

<br>

2052

<code>sudo zypper install make</code>

2053

</blockquote>

2054

<p>

2055

In addition, it is necessary to set a few environment

2056

variables for the build:

2057

2058

<code>export LANG=C</code>

2059

<br>

2060

<code>export PATH="/usr/lib/jvm/java-1.7.0-openjdk/bin:$[PATH}"</code>

2061

</blockquote>

2062

<p>

2063

Finally, you need to unset the <code>JAVA_HOME</code>

2064

environment variable:

2065

2066

<code>export -n JAVA_HOME</code>

</blockquote>

</blockquote>

<h4><a name="mandriva">Mandriva Linux One 2009 Spring</a></h4>

2071

2072

After installing <a href="http://mandriva.org">Mandriva</a>

2073

Linux One 2009 Spring

2074

you need to install several build dependencies.

2075

The simplest way to install the build dependencies is to

2076

execute the following commands as user <code>root</code>:

2077

2078

<code>urpmi java-1.7.0-openjdk-devel make gcc gcc-c++

2079

freetype-devel zip unzip libcups2-devel libxrender1-devel

2080

libalsa2-devel libstc++-static-devel libxtst6-devel

libxi-devel</code>

</blockquote>

<p>

In addition, it is necessary to set a few environment

2085

variables for the build:

2086

2087

<code>export LANG=C</code>

2088

<br>

2089

<code>export PATH="/usr/lib/jvm/java-1.7.0-openjdk/bin:${PATH}"</code>

</blockquote>

</blockquote>

<h4><a name="opensolaris">OpenSolaris 2009.06</a></h4>

2094

2095

After installing <a href="http://opensolaris.org">OpenSolaris</a> 2009.06

2096

you need to install several build dependencies.

2097

The simplest way to install the build dependencies is to

2098

execute the following commands:

2099

2100

<code>pfexec pkg install SUNWgmake SUNWj7dev

2101

sunstudioexpress SUNWcups SUNWzip SUNWunzip SUNWxwhl

2102

SUNWxorg-headers SUNWaudh SUNWfreetype2</code>

2103

</blockquote>

2104

<p>

2105

In addition, it is necessary to set a few environment

2106

variables for the build:

2107

2108

<code>export LANG=C</code>

2109

<br>

2110

<code>export PATH="/opt/SunStudioExpress/bin:${PATH}"</code>

</blockquote>

</blockquote>

Kelly O'Hair

2008-04-30 19:35:26 -0700

[diff] [blame]

2114

</blockquote>

Kelly O'Hair

2013-02-23 10:47:01 -0800

[diff] [blame]

2115

2116

</blockquote>

2117

2118

2119

2120

<!-- Leave out Appendix D --

2121

2122

<hr>

2123

<h2><a name="mapping">Appendix D: Mapping Old to New</a></h2>

2124

2125

<p>This table will help you convert some idioms of the old build

2126

system to the new build system.</p>

2127

2128

2129

<th>In the old build system, you used to...</th>

2130

<th>In the new build system, you should ...</th>

2131

</tr>

2132

2133

<td>run <code>make sanity</code></td>

2134

<td>run <code>bash ./configure</code></td>

2135

</tr>

2136

2137

<td>set <code>ALT_OUTPUTDIR=build/my-special-output</code></td>

2138

<td>before building the first time:

Kelly O'Hair

2011-03-22 08:15:39 -0700

[diff] [blame]

2139

<br>

Kelly O'Hair