Maybe we should take this to starlink-internal?
Norman wrote:
> Now I come to rebuild everything, I discover that parsecon now fails to
> build on the Mac. And gks currently doesn't build, for a broadly
> similar-looking linking reason (and different from that reported
> recently by Al, on Linux). I recall there are a couple of other
> components which I've discovered, or been told, have stopped working on
> either OSX or Linux. What gives? This _was_ all working the last time
> I tried -- I know, because I was doing it on OSX consistently, and would
> have noticed if nothing was working! In particular, I'm pretty sure
> this was working for me after I reorganised the messgen and
> documentation handling recently, so I don't _think_ this was me, though
> I have no way of knowing.
>
> ARGHHH. When did all this stop working? We have no clue.
>
> How close are we to having a consistently building `make world', on any
> platform? We have no clue.
>
> Is there any progress with the nightly builds? We don't have to wait
> until everything is building: we don't have to do `make world' nightly
> on all platforms, as we could just do `make /blah/manifests/xxx' for
> some suitably chosen component `xxx', and inch that towards `make world'
> as and when things were observed to build. At least then we'd know when
> things broke, and thus have a better chance at working out what it was
> that broke them.
Agreed pretty much, I was a bit alarmed to discover that I was having
problems rebuilding the SSC under RH9, which is pretty much our primary
build platform. I'd, naively I guess, I assumed we already had nightly
builds and since Steve wasn't screaming at us it all worked, at least
on Linux. Until this (last!?) week I hadn't tried to build things on
anything other then the Mac as was therefore assuming the problems I
was running into were Mac specific.
Al.
|