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>

Erik Joelsson

2013-08-30 10:13:25 +0200

[diff] [blame^]

1213

<b>Q:</b> The <code>generated-configure.sh</code> file looks horrible!

Kelly O'Hair

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

[diff] [blame]

1214

How are you going to edit it?

1215

<br>

Erik Joelsson

2013-08-30 10:13:25 +0200

[diff] [blame^]

1216

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

Kelly O'Hair

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

[diff] [blame]

1217

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

Erik Joelsson

2013-08-30 10:13:25 +0200

[diff] [blame^]

1218

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

1219

which are much more readable.

Kelly O'Hair

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

[diff] [blame]

1220

</p>

1221

Kelly O'Hair

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

[diff] [blame]

1222

<p>

1223

Erik Joelsson

2013-08-30 10:13:25 +0200

[diff] [blame^]

1224

Why is the <code>generated-configure.sh</code> file checked in,

Kelly O'Hair

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

[diff] [blame]

if it is generated?

<br>

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

1229

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

1230

as the first step.

1231

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

1232

to start building OpenJDK, and to minimize

1233

the number of external dependencies required.

</p>

<p>

Do you require a specific version of autoconf for regenerating

Erik Joelsson

2013-08-30 10:13:25 +0200

[diff] [blame^]

1239

<code>generated-configure.sh</code>?

Kelly O'Hair

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

[diff] [blame]

1240

<br>

1241

Erik Joelsson

2013-08-30 10:13:25 +0200

[diff] [blame^]

1242

Yes, version 2.69 is required and should be easy

1243

enough to aquire on all supported operating

1244

systems. The reason for this is to avoid

1245

large spurious changes in <code>generated-configure.sh</code>.

</p>

<p>

How do you regenerate <code>generated-configure.sh</code>

1251

after making changes to the input files?

1252

<br>

1253

1254

Regnerating <code>generated-configure.sh</code>

1255

should always be done using the

1256

script <code>common/autoconf/autogen.sh</code> to

1257

ensure that the correct files get updated. This

1258

script should also be run after mercurial tries to

1259

merge <code>generated-configure.sh</code> as a

1260

merge of the generated file is not guaranteed to

1261

be correct.

Kelly O'Hair

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

[diff] [blame]

</p>

<p>

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

1267

They look like gibberish.

1268

<br>

1269

1270

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

1271

limitations on certain platforms (Windows, Solaris).

1272

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

1273

command lines containing too many files will not work properly.

1274

These

1275

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

1276

command line in the makefile and then uncompress it safely.

1277

We're

1278

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

1279

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

</p>

<p>

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

1285

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

1286

<br>

1287

1288

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

1289

several log levels:

1290

</p>

Kelly O'Hair

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

[diff] [blame]

1291

Kelly O'Hair

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

[diff] [blame]

1292

<ul>

Kelly O'Hair

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

[diff] [blame]

1293

<li>

Kelly O'Hair

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

[diff] [blame]

1294

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

Kelly O'Hair

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

[diff] [blame]

1295

</li>

1296

<li>

Kelly O'Hair

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

[diff] [blame]

1297

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

1298

than warn.

Kelly O'Hair

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

[diff] [blame]

1299

</li>

1300

<li>

Kelly O'Hair

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

[diff] [blame]

1301

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

1302

prints all macro calls for compilation definitions.

Kelly O'Hair

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

[diff] [blame]

1303

</li>

1304

<li>

Kelly O'Hair

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

[diff] [blame]

1305

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

1306

lines as well.

Kelly O'Hair

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

[diff] [blame]

1307

</li>

Kelly O'Hair

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

[diff] [blame]

1308

</ul>

Kelly O'Hair

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

[diff] [blame]

1309

</blockquote>

1310

Kelly O'Hair

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

[diff] [blame]

1311

<p>

1312

1313

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

1314

<br>

1315

1316

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

1317

configuration.

1318

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

1319

configuration options,

1320

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?

1326

<br>

1327

1328

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

1329

library,

1330

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

1331

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

1332

exceptions for some native libraries where the source files are spread

Erik Joelsson

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

[diff] [blame]

1333

over many directories which also contain sources for other

Kelly O'Hair

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

[diff] [blame]

1334

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

Erik Joelsson

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

[diff] [blame]

1335

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,

1341

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

1342

<br>

1343

1344

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

1345

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

1346

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

1347

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]

1353

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

1354

described in this document. What about those?

Kelly O'Hair

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

[diff] [blame]

1355

<br>

1356

1357

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

1358

experimental features.

1359

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]

1360

is just a placeholder. Others depend on

Kelly O'Hair

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

[diff] [blame]

1361

pieces of code or infrastructure that is currently

1362

not ready for prime time.

</p>

<p>

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

1368

<br>

1369

1370

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

1371

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

1372

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

1373

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

1374

comparison, even

1375

when building twice with the old build system.

1376

For these, we compare relevant aspects

1377

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

1378

Note that we still don't have 100%

1379

equivalence, but we're close.

</p>

<p>

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

1385

Why don't you fix it?

1386

<br>

1387

1388

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

1389

technically possible to the old build output.

1390

If things were weird in the old build,

1391

they will be weird in the new build.

1392

Often, things were weird before due to obscurity,

1393

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

1394

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

1395

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

1405

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

1406

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

1407

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

1408

system and some will need to wait until after.

1409

</p>

1410

1411

<p>

Kelly O'Hair

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

[diff] [blame]

1412

1413

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

1414

<br>

1415

1416

Yes, this is the minimal (or roughly minimal)

1417

set of compiled output needed for a developer to actually

1418

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

1419

development fashion, when doing a normal make,

1420

you should only spend time recompiling what's changed

1421

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

1422

needed to actually run and test your code.

1423

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

1424

target is not needed for a normal developer who wants to

1425

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

1426

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

1427

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

</p>

<p>

I usually set a specific environment variable when building,

1433

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]

1437

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]

1438

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

Erik Joelsson

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

[diff] [blame]

1439

Email us and we will add support for it!

Kelly O'Hair

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

[diff] [blame]

1440

</p>

1441

Kelly O'Hair

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

[diff] [blame]

1442

</blockquote>

Kelly O'Hair

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

[diff] [blame]

1443

1444

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

Kelly O'Hair

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

[diff] [blame]

1445

Kelly O'Hair

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

[diff] [blame]

1446

1447

<p>Building OpenJDK requires a lot of horsepower.

1448

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

1449

of resources such as

1450

parallel threads and memory.

1451

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

1452

values for such options based on your hardware.

1453

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

1454

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

<ul>

<li>

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

1459

—

1460

number of cores in the build system,

1461

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

1462

</li>

1463

<li>

1464

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

1465

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

1466

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

</li>

</ul>

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

1471

to the Bootstrap JDK, using e.g.

1472

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

1473

Doing this will override the default JVM arguments

1474

passed to the Bootstrap JDK.</p>

1475

1476

1477

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

1478

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

1479

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

1480

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

1481

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

1482

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

1483

1484

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

1485

you will get a performance summary,

1486

indicating how well the build will perform. Here you will

1487

also get performance hints.

1488

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

1489

1490

<h4>Building with ccache</h4>

1491

1492

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

1493

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

1494

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

1495

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

1496

does not work correctly with the precompiled headers used in

1497

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

1498

highly recommend installing it. This is currently only supported on

1499

linux.</p>

1500

1501

<h4>Building on local disk</h4>

1502

1503

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

1504

make sure the build directory is situated on local disk.

1505

The performance

1506

penalty is extremely high for building on a network share,

1507

close to unusable.</p>

1508

1509

<h4>Building only one JVM</h4>

1510

1511

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

1512

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

1513

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

1514

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

1515

mimic the old behavior on platforms that support it,

1516

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

1517

1518

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

1519

1520

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

1521

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

1522

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

1523

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

1524

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

1525

1526

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

1527

power for other processes, you can run

1528

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

1529

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

1530

which will disable parallelism.</p>

1531

1532

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

1533

builds default and override with fast if you're

1534

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

1535

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

1536

If you want to run with more

1537

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

1538

J. Duke

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

[diff] [blame]

1539

</blockquote>

Kelly O'Hair

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

[diff] [blame]

1540

1541

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

1542

1543

1544

<h4>Solving build problems</h4>

1545

1546

1547

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

1548

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

1549

is to re-run the build with more verbosity.

1550

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

1551

<br>

1552

The build log (with both stdout and stderr intermingled,

1553

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

1554

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

1555

<br>

1556

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

1564

of the build log.

1565

<br>

1566

A build can fail for any number of reasons.

1567

Most failures

1568

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

1569

pre-build requirements have not been met.

1570

The first step in

1571

troubleshooting a build failure is to recheck that you have satisfied

1572

all the pre-build requirements for your platform.

1573

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

1574

sure that what it found makes sense for your system.

1575

Look for strange error messages or any difficulties that

1576

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

1577

<br>

1578

Some of the more common problems with builds are briefly

1579

described

1580

below, with suggestions for remedies.

1581

<ul>

1582

<li>

1583

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

1584

1585

Some virus scanning software has been known to

1586

corrupt the

1587

downloading of zip bundles.

1588

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

1589

'real time'

1590

virus scanning features to prevent this corruption.

1591

This type of "real time" virus scanning can also

1592

slow down the

1593

build process significantly.

1594

Temporarily disabling the feature, or excluding the build

1595

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

1603

simultaneous C++ compiles, try setting the

1604

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

1605

Then try increasing the count slowly to an acceptable

1606

level for your system. Also:

1607

1608

Creating the javadocs can be very slow,

1609

if you are running

1610

javadoc, consider skipping that step.

1611

<br>

1612

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

1613

The VM build tends to be CPU intensive

1614

(many C++ compiles),

1615

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

1616

<br>

1617

Faster compiles are possible using a tool called

1618

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

</blockquote>

</blockquote>

</li>

<li>

<b>File time issues:</b>

1624

1625

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

1626

1627

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

1628

File `xxx' has modification time in

1629

the future.</code>

1630

<br>

1631

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

1632

Your build may

1633

be incomplete.</code>

1634

</blockquote>

1635

These warnings can occur when the clock on the build

1636

machine is out of

1637

sync with the timestamps on the source files.

1638

Other errors, apparently

1639

unrelated but in fact caused by the clock skew,

1640

can occur along with

1641

the clock skew warnings.

1642

These secondary errors may tend to obscure the

1643

fact that the true root cause of the problem

1644

is an out-of-sync clock.

1645

<p>

1646

If you see these warnings, reset the clock on the

1647

build

1648

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

1649

or delete the directory

1650

containing the build output, and restart the

1651

build from the beginning.

</blockquote>

</li>

<li>

<b>Error message:

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

1657

1658

Increase the amount of swap space on your build machine.

1659

This could be caused by overloading the system and

1660

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>

1670

1671

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

1672

This is installed as part of a specific package

1673

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

1674

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

1675

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

1676

Various parts of the JDK build require a static

1677

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

1678

portability of the built images.

</blockquote>

</li>

<li>

<b>Linux Error Message:

1683

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

1684

1685

This is probably an issue with SELinux (See

1686

1687

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

1688

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

1689

performance reasons.

1690

<p>

1691

To completely disable SELinux:

1692

<ol>

1693

1694

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

1695

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

1696

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

1697

</ol>

1698

<p>

1699

Alternatively, instead of completely disabling it you could

1700

disable just this one check.

1701

<ol>

1702

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

1703

<li>In the SELinux Management Tool which appears,

1704

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

1705

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

1706

<li>Check the first item, labeled

1707

"Allow all unconfined executables to use

1708

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

</ol>

</blockquote>

</li>

<li>

<b>Windows Error Messages:</b>

1714

<br>

1715

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

1716

<br>

1717

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

1718

<br>

1719

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

1720

<br>

1721

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

1722

<br>

1723

1724

The CYGWIN software can conflict with other non-CYGWIN

1725

software. See the CYGWIN FAQ section on

1726

1727

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

</blockquote>

</li>

<li>

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

1732

1733

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

1734

issue with the disk or disk partition being used.

1735

Sometimes it comes with a "Permission Denied" message.

</blockquote>

</li>

</ul>

</blockquote>

</blockquote>

1742

1743

</blockquote>

1744

1745

Kelly O'Hair

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

[diff] [blame]

1746

<hr>

Kelly O'Hair

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

[diff] [blame]

1747

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

J. Duke

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

[diff] [blame]

1748

Kelly O'Hair

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

[diff] [blame]

1749

Kelly O'Hair

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

[diff] [blame]

1750

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

Kelly O'Hair

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

[diff] [blame]

1751

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

1752

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

Kelly O'Hair

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

[diff] [blame]

1753

A few notes about using GNU make:

1754

<ul>

1755

<li>

Kelly O'Hair

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

[diff] [blame]

1756

You need GNU make version 3.81 or newer.

Kelly O'Hair

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

[diff] [blame]

1757

If the GNU make utility on your systems is not

1758

3.81 or newer,

1759

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

Kelly O'Hair

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

[diff] [blame]

1760

</li>

1761

<li>

Kelly O'Hair

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

[diff] [blame]

1762

Place the location of the GNU make binary in the

1763

<code>PATH</code>.

Kelly O'Hair

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

[diff] [blame]

1764

</li>

1765

<li>

1766

<strong>Solaris:</strong>

Kelly O'Hair

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

[diff] [blame]

1767

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

Kelly O'Hair

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

[diff] [blame]

1768

If your Solaris system has the software

Kelly O'Hair

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

[diff] [blame]

1769

from the Solaris Developer Companion CD installed,

1770

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

1771

which will be located in either the

1772

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

1773

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

Kelly O'Hair

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

[diff] [blame]

1774

</li>

1775

<li>

1776

<strong>Windows:</strong>

Kelly O'Hair

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

[diff] [blame]

1777

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]

1782

</li>

1783

</ul>

J. Duke

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

[diff] [blame]

1784

<p>

Kelly O'Hair

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

[diff] [blame]

1785

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

1791

1792

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

Kelly O'Hair

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

[diff] [blame]

1793

</p>

Kelly O'Hair

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

[diff] [blame]

1794

1795

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

Kelly O'Hair

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

[diff] [blame]

1796

Kelly O'Hair

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

[diff] [blame]

1797

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]

1798

1799

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

Kelly O'Hair

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

[diff] [blame]

1800

Building is a little different depending on the OS but is

1801

basically done with:

1802

1803

<code>bash ./configure</code>

1804

<br>

1805

1806

</blockquote>

Kelly O'Hair

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

[diff] [blame]

1807

</blockquote>

Edvard Wendelin

1f736c8

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

[diff] [blame]

1808

Kelly O'Hair

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

[diff] [blame]

1809

</blockquote>

1810

1811

Edvard Wendelin

1f736c8

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

[diff] [blame]

1812

<hr>

Kelly O'Hair

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

[diff] [blame]

1813

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

Kelly O'Hair

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

[diff] [blame]

1814

Kelly O'Hair

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

[diff] [blame]

1815

1816

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

J. Duke

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

[diff] [blame]

1817

Kelly O'Hair

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

[diff] [blame]

1818

This file often describes specific requirements for what we

1819

call the

1820

"minimum build environments" (MBE) for this

1821

specific release of the JDK.

1822

What is listed below is what the Oracle Release

1823

Engineering Team will use to build the Oracle JDK product.

1824

Building with the MBE will hopefully generate the most compatible

1825

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

1826

of the same base OS and hardware architecture.

1827

In some cases, these represent what is often called the

1828

least common denominator, but each Operating System has different

1829

aspects to it.

J. Duke

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

[diff] [blame]

1830

<p>

Kelly O'Hair

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

[diff] [blame]

1831

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

1832

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

1833

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

1834

the minimums listed below are simply recommendations.

1835

<p>

1836

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

1837

oldest release we can guarantee builds and works, and the

1838

specific version of the compilers used could be critical.

1839

<p>

1840

With Windows the critical aspect is the Visual Studio compiler

1841

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

1842

systems can do the builds and where the resulting bits can

1843

be used.<br>

1844

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

1845

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

1846

<p>

1847

With Linux, it was just a matter of picking a

1848

stable distribution that is a good representative for Linux

1849

in general.<br>

1850

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

1851

but it has not been completely determined yet, possibly

1852

Ubuntu 12.04 X64, unbiased community feedback would be welcome on

1853

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

1854

<p>

1855

It is understood that most developers will NOT be using these

1856

specific versions, and in fact creating these specific versions

1857

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

1858

It is expected that developers are more often using the more

1859

recent releases and distributions of these operating systems.

1860

<p>

1861

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

1862

common problem.

1863

Similarly, compilation problems related to changes to the

1864

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

1865

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

1866

Please report these types of problems as bugs so that they

1867

can be dealt with accordingly.

</p>

<thead>

<tr>

<th>Base OS and Architecture</th>

1873

1874

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

1875

<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>

1893

<td>Solaris 10 Update 6</td>

1894

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

</tr>

<tr>

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

1902

<td>Solaris 10 Update 6</td>

1903

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

</tr>

<tr>

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

1911

<td>Windows XP</td>

1912

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

</tr>

<tr>

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

1920

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

1921

<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]

1938

</blockquote>

Kelly O'Hair

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

[diff] [blame]

1939

1940

1941

<hr>

1942

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

Kelly O'Hair

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

[diff] [blame]

1943

Kelly O'Hair

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

[diff] [blame]

1944

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

1945

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

1946

<p>

1947

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

1948

this part of the document.

1949

</strong>

1950

1951

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

1952

1953

After installing the latest

1954

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

1955

you need to install several build dependencies.

1956

The simplest way to do it is to execute the

1957

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

1958

1959

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

1960

<br>

1961

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

1962

</blockquote>

1963

<p>

1964

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

1965

variables for the build:

1966

1967

<code>export LANG=C</code>

1968

<br>

1969

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

</blockquote>

</blockquote>

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

1975

1976

After installing

1977

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

1978

you need to make sure you have

1979

the following Development bundles installed:

1980

1981

<ul>

1982

<li>Development Libraries</li>

1983

<li>Development Tools</li>

1984

<li>Java Development</li>

1985

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

</ul>

</blockquote>

<p>

Plus the following packages:

1990

1991

<ul>

1992

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

1993

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

1994

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

</ul>

</blockquote>

<p>

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

1999

but the freetype 2.3 sources can be downloaded, built,

2000

and installed easily enough from

2001

2002

the freetype site</a>.

2003

Build and install with something like:

2004

2005

<code>bash ./configure</code>

<br>

<br>

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

2010

</blockquote>

2011

<p>

2012

Mercurial packages could not be found easily, but a Google

2013

search should find ones, and they usually include Python if

it's needed.

</blockquote>

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

2018

2019

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

2020

you need to install several build dependencies.

2021

The simplest way to install the build dependencies is to

2022

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

2023

2024

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

2025

<br>

2026

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

2027

</blockquote>

2028

<p>

2029

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

2030

variables for the build:

2031

2032

<code>export LANG=C</code>

2033

<br>

2034

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

</blockquote>

</blockquote>

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

2039

2040

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

2041

you need to install several build dependencies. The simplest

2042

way to do it is to execute the following commands:

2043

2044

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

2045

<br>

2046

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

2047

</blockquote>

2048

<p>

2049

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

2050

variables for the build:

2051

2052

<code>export LANG=C</code>

2053

<br>

2054

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

</blockquote>

</blockquote>

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

2059

2060

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

2061

you need to install several build dependencies.

2062

The simplest way to install the build dependencies is to

2063

execute the following commands:

2064

2065

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

2066

<br>

2067

<code>sudo zypper install make</code>

2068

</blockquote>

2069

<p>

2070

In addition, it is necessary to set a few environment

2071

variables for the build:

2072

2073

<code>export LANG=C</code>

2074

<br>

2075

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

2076

</blockquote>

2077

<p>

2078

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

2079

environment variable:

2080

2081

<code>export -n JAVA_HOME</code>

</blockquote>

</blockquote>

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

2086

2087

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

2088

Linux One 2009 Spring

2089

you need to install several build dependencies.

2090

The simplest way to install the build dependencies is to

2091

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

2092

2093

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

2094

freetype-devel zip unzip libcups2-devel libxrender1-devel

2095

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

libxi-devel</code>

</blockquote>

<p>

In addition, it is necessary to set a few environment

2100

variables for the build:

2101

2102

<code>export LANG=C</code>

2103

<br>

2104

<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>

2109

2110

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

2111

you need to install several build dependencies.

2112

The simplest way to install the build dependencies is to

2113

execute the following commands:

2114

2115

<code>pfexec pkg install SUNWgmake SUNWj7dev

2116

sunstudioexpress SUNWcups SUNWzip SUNWunzip SUNWxwhl

2117

SUNWxorg-headers SUNWaudh SUNWfreetype2</code>

2118

</blockquote>

2119

<p>

2120

In addition, it is necessary to set a few environment

2121

variables for the build:

2122

2123

<code>export LANG=C</code>

2124

<br>

2125

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

</blockquote>

</blockquote>

Kelly O'Hair

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

[diff] [blame]

2129

</blockquote>

Kelly O'Hair

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

[diff] [blame]

2130

2131

</blockquote>

2132

2133

2134

2135

<!-- Leave out Appendix D --

2136

2137

<hr>

2138

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

2139

2140

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

2141

system to the new build system.</p>

2142

2143

2144

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

2145

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

2146

</tr>

2147

2148

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

2149

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

2150

</tr>

2151

2152

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

2153

<td>before building the first time:

Kelly O'Hair

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

[diff] [blame]

2154

<br>

Kelly O'Hair