All of lore.kernel.org
 help / color / mirror / Atom feed
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:59:35 -0400	[thread overview]
Message-ID: <877lauc9pk.fsf@linuxcare.com> (raw)
In-Reply-To: Alan Modra's message of "Tue, 11 Jul 2000 00:38:58 +1000 (EST)"

Alan Modra <alan@linuxcare.com.au> writes:

> Yeah, I got enthusiastic about implementing linuxthreads, and put in
> support for parisc style spinlocks using ldcw (Load and Clear Word).
> We need to grab a lock by clearing it so the locks need to be initialised
> to non-zero, which is exactly opposite to other glibc spinlocks.  My
> enthusiasm waned when I hit a missing syscall - forget what it was now.

glibc doesn't really want to compile with linuxthreads for me -
something breaks in the way errno is handled and I get "undefined
reference to errno" when linking.

Jes says we don't really want to mess with that stuff until we have
shared libs working, and I'm inclined to trust him on that :-)

I guess for now we can just ignore libstdc++ and friends...

-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

      reply	other threads:[~2000-07-10 14:59 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
2000-07-10 14:16       ` David Huggins-Daines
2000-07-10 14:38         ` Alan Modra
2000-07-10 14:59           ` David Huggins-Daines [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=877lauc9pk.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 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.