From: David Huggins-Daines <dhd@linuxcare.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] problems with gcc 2.96
Date: 10 Jul 2000 10:00:32 -0400 [thread overview]
Message-ID: <87snticcfz.fsf@linuxcare.com> (raw)
In-Reply-To: willy@thepuffingroup.com's message of "Mon, 10 Jul 2000 08:28:44 -0400"
willy@thepuffingroup.com writes:
> On Mon, Jul 10, 2000 at 10:06:06AM +1000, Alan Modra wrote:
> > On Sun, 9 Jul 2000 willy@thepuffingroup.com wrote:
> >
> > > /home/willy/parisc/hppa1.1-linux/include/bits/stdio-lock.h:29:2: #error libio needs recursive mutexes for _IO_MTSAFE_IO
> > > make[1]: *** [iogetline.o] Error 1
> > >
> > > dhd, you must have solved this already?
> >
> > Errm, unless your glibc versions differ. I did a merge on June 10. Ducks
> > for cover.
>
> I spoke to dhd last night and apparently the solution is to
> --disable-multilib for gcc. i'm just trying it now and it appears to
> get a lot further. time to update the recipe, i guess.
I've already told willy this, but this is due to the C++ support.
Configure with --enable-languages=c for the time being until it's sorted.
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next prev parent reply other threads:[~2000-07-10 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-09 19:00 [parisc-linux] problems with gcc 2.96 willy
[not found] ` <Pine.LNX.4.21.0007100959080.684-100000@front.linuxcare.com.au>
[not found] ` <20000710082844.C16294@vodka.thepuffingroup.com>
2000-07-10 14:00 ` David Huggins-Daines [this message]
2000-07-10 14:16 ` David Huggins-Daines
2000-07-10 14:38 ` Alan Modra
2000-07-10 14:59 ` David Huggins-Daines
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87snticcfz.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=alan@linuxcare.com.au \
--cc=parisc-linux@thepuffingroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox