From: Toon Knapen (toon.knapen_at_[hidden])
Date: 2003-07-10 11:29:05
> Hmmm. I'll have to figura out another way to check for things
> in the path :-(
Well, it's not a show-stopper for me so no rush.
> >> Now for vacpp, I do try and detect it by seeing if 'xlc' is
> >> in the path. Is 'xlc' not normally in the path for the
> >> compiler? Is there a standard place the compiler is
> >> installed? And like above, what does 'uname' return?
> >Yes it's in the path. But invoking 'xlc' (without arguments)
> results in
> >the man pages being displayed and thus the command never
> returns unless
> >hitting 'q' or <space> a few times.
> OK. But build.sh doesn't invoke the command (xlc) when
> checking if it's in the path. Or is it for you, somehow?
I honestly don't understand what's going wrong. First I'm not great at
shell programming, second all these different platforms always behave a
/little/ different which makes building reliable scripts very hard. I'm
working on automatic scripts to update the boost status pages every
night on 4 different OS's and it's hard ;-(
But again, I don't mind having to specify the extra argument to specify
the toolset to be used.
> >But I've finally succeeded in porting bjam to solaris/sunpro. All
> >changes are minor including :
> >Another remark I have is that filesys.h provides function signatures
> >for functions that are not defined in filesys.c.
> Not sure if that's our fault (Boost.Jam), or Perforce being sloppy.
Here's another one: builtins.c had it's own signature for regex_compile
that does not correspond with the signature in compile.h nor with the
implementation in subst.c. So I removed it and included compile.h
Now finally jam0 gets build on solaris, bjam not yet ;-(
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