From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-11-24 09:59:27
Thanks for the toolset file! It looks like there's still a lot of
Win32-specific flotsam in there (remember, gcc-tools.jam works with
Cygwin-g++). In particular, the IMPLIB_COMMAND stuff doesn't really belong
in a unix-specific toolset. Try stripping out anything you don't understand,
to make a minimal toolset, and see if that still works... it seems everybody
uses gcc as their prototype; I really should clean it up and add some
comments so that people know how to proceed!
Boost.Python currently has a few known problems which keep it from working
with Intel, though this one doesn't seem to be the deal-breaker I expected
to see from this compiler.
I guess you hadn't noticed, but a full-fledged effort to distribute binaries
is already underway. Vladimir Prus has been making RPMs and windows
installers, and Toon Knapen has been compiling jam for lots of different
What problems did you have building the delivered jam_src?
Vladimir's RPM/installer is doing some fancy stuff which determines
BOOST_ROOT automatically, so that should be less of an issue.
We'll get the Python version thing straightened out, too. Thanks for your
----- Original Message -----
From: "joerg.walter" <jhr.walter_at_[hidden]>
recently I've bought a new box and installed Linux (SuSE 7.3), so I've got a
MSFZ, at least partially :-). Then I noticed, that Intel released it's
compiler on Linux (especially in a free and unsupported license variant :-).
Download and install of the compiler worked fine for me.
The simplest solution to integrate the new compiler in my working
environment was to adapt the copy of an existing jam tool file and to extend
Toon Knapen's jamfiles for ublas. I'll send the jam tool file for the Intel
Linux compiler attached.
To be sure, that the first version of the tool file is reasonably correct, I
builded all(?) of boost (1.25.1) using the command 'jam -sTOOLS=intel' in
the boost root directory. The compiler reported some warnings in
boost.regexp and boost.threads and one error in boost.python. The build log
is also attached.
Once I understand the regression test mechanics, I'll check them also.
I noticed a few things that I would like to mention also:
- It's a little bit confusing to identify the 'best' jam executable. I fear
that boost will have to distribute binaries one day.
- A build of the delivered jam_src was difficult for me, but may be that was
a novice's problem ;-)
- It seems to be very important to set BOOST_ROOT correctly. Jam messages
are cryptic otherwise. In one case I even managed it to generate a 100 MB
logfile before terminating the build (that looked a little bit like an
- By default the installed Python version is 2.1 on SuSE 7.3 (no more 1.5).
P.S.: is it ok, not to post this to the boost mailing list?
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk