From: "H . J . Lu" <hjl@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] IA64 Linux library problem
Date: Fri, 21 Jul 2000 22:22:45 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205221@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205213@msgid-missing>
On Thu, Jul 20, 2000 at 10:14:40AM +0200, Einar Saltnes wrote:
> "H . J . Lu" wrote:
> >
> > On Wed, Jul 19, 2000 at 05:30:23PM +0200, Einar Saltnes wrote:
> > > Hello!
> > >
> > > We are experiencing some problems using some library routines on ia64.
> > > We have an Itanium monoprocessor from Fujitsu Siemens running Red Hat
> > > Linux
> > > Development Release for IA-64.
> > >
>
> > > 2)
> > > We also experience errors using
> > > cout << xxx << endl;
> > > when linking with the pthread library.
> > > Using "endl" will give segmentation fault when linking with pthread
> > > library, while the very same statement will be OK when not linking with
> >
> > It is a known problem. libc is MT safe. But libstdc++ is not configured
> > for MT safe.
> >
> > H.J.
>
> Thank You for the reply!
> We don't quite understand that libstdc++ is not configured MT safe, as
> the program stack shows the call to "pthread_mutex_lock".
> However, we are looking for solutions to continue our work on the ia64
> and Linux combination.
> Do You have any suggestions of what we should/can do to get a MT safe
> libstdc++ or do You have any indications of when a MT safe libstdc++
> will be available?
>
I put a new rpms for alpha RedHat ia64 distribution at:
http://ftp.valinux.com/pub/support/hjl/ia64
There are 2 rpms and 2 small patches. I also enabled the shared
libstdc++.
BTW, the next official ia64 gcc release is ok.
H.J.
prev parent reply other threads:[~2000-07-21 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 15:30 [Linux-ia64] IA64 Linux library problem Einar Saltnes
2000-07-19 15:39 ` H . J . Lu
2000-07-21 22:22 ` H . J . Lu [this message]
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=marc-linux-ia64-105590678205221@msgid-missing \
--to=hjl@valinux.com \
--cc=linux-ia64@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.