> maybe if linking with static libraries is an option?
i guess that's always possible, but kinda ugly.
randolph
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Randolph Chung writes:
> > Is that one available somewhere on an ia64 box, preferably one accessible
> > to John?
>
> gcc-snapshot package, but we cannot use that to build binaries to go into the
> archive (uses different library versions)
maybe if linking with static libraries is an option?
> I
> Is that one available somewhere on an ia64 box, preferably one accessible
> to John?
gcc-snapshot package, but we cannot use that to build binaries to go into the
archive (uses different library versions)
I'm not sure which box John has access to, but mail
[EMAIL PROTECTED] and they can install
> > There appear to (still) be some issues with g++-3.0 on ia64. Under some
> > optimisation switches, the executable is built, but segfaults. Under others,
> > g++-3.-0 dies.
>
> fwiw with gcc version 3.1 20020331 (prerelease) the problem appears to
> be fixed. I think this might be the same/re
> There appear to (still) be some issues with g++-3.0 on ia64. Under some
> optimisation switches, the executable is built, but segfaults. Under others,
> g++-3.-0 dies.
fwiw with gcc version 3.1 20020331 (prerelease) the problem appears to
be fixed. I think this might be the same/related to pr/53
Package: g++-3.0
Version: 1:3.0.4-7
Severity: important
The following bug report owes a lot to John Eaton's work. I reported a
problem with the octave2.1 package on the ia64 platform to him, the upstream
authors. Bdale kindly provided an account on ia64 for John.
There appear to (still) be so
6 matches
Mail list logo
