On Wed, 2002-02-27 at 23:04, Matthias Klose wrote:
> No problem. I'll update the CVS this weekend. Please wait with the
> upload until the current version did move to testing (should be in
> three days).
Which current version are we talking about? According to
update-excuses:
* gcc-defaults (0.1
Philip Blundell writes:
> On Wed, 2002-02-27 at 19:27, Matthias Klose wrote:
> > Philip Blundell writes:
> > > On Wed, 2002-02-27 at 17:04, Adam C Powell IV wrote:
> > > > 3.0 fixes this problem, but then maintainers must hand-build using
> > > > g77-3.0, which is not a viable long-term solution.
On Wed, 2002-02-27 at 19:27, Matthias Klose wrote:
> Philip Blundell writes:
> > On Wed, 2002-02-27 at 17:04, Adam C Powell IV wrote:
> > > 3.0 fixes this problem, but then maintainers must hand-build using
> > > g77-3.0, which is not a viable long-term solution. I know some arches
> > > have 3.
Philip Blundell writes:
> On Wed, 2002-02-27 at 17:04, Adam C Powell IV wrote:
> > 3.0 fixes this problem, but then maintainers must hand-build using
> > g77-3.0, which is not a viable long-term solution. I know some arches
> > have 3.0 as their default compiler. So, what are the criteria, and
On Wed, 2002-02-27 at 17:04, Adam C Powell IV wrote:
> 3.0 fixes this problem, but then maintainers must hand-build using
> g77-3.0, which is not a viable long-term solution. I know some arches
> have 3.0 as their default compiler. So, what are the criteria, and
> what's the procedure, for cha
Greetings,
g77-2.95 has a nasty bug on ARM which prevents linking of any FORTRAN
libs (#90363). Our current status is that all packages with binaries
which link to FORTRAN libs fail to build! This bug is not likely to be
fixed.
3.0 fixes this problem, but then maintainers must hand-build usin
6 matches
Mail list logo
