mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Jared Young <headgeek@li.nu-x.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help!!! Pthread Sh*T
Date: Tue, 8 Apr 2003 12:13:30 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0304081209110.24014@chaos> (raw)
In-Reply-To: <20030408123417.5485ba9e.headgeek@li.nu-x.net>

On Tue, 8 Apr 2003, Jared Young wrote:

> I installed pthread libaries recently, anyhow, I keep getting errors what I cannot work around with gcc and make in general. I cannot even compile a new gcc to allow for the new pthread extenstion. I uninstalled pthread libs in hopes to restore prior state but umm yah. After reinstalling::
>
> Current Kernel:2.4.20
> Current GCC:2.95.3
> Current Pthread:1.4.1
>
> This was the error I got when building commoncpp-2-1.0.9, but this error is similar in everything else I try to build.
>
> ::Configure options::::
> ./configure  --prefix=/usr --sysconfdir=/etc --with-pthread --with-ftp
>

You need to reinstall your header files either from backups or from
your distribution. Just overwrite /usr/include/... on down and it will
fix it. Lucky you didn't overwrite libraries ;) That would require
starting from scratch.

In the future, you need to build pthreads into/at-the-same-time as
you build a 'C' runtime library. They then get installed together to
keep them compatible.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.


      reply	other threads:[~2003-04-08 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 16:34 Jared Young
2003-04-08 16:13 ` Richard B. Johnson [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=Pine.LNX.4.53.0304081209110.24014@chaos \
    --to=root@chaos.analogic.com \
    --cc=headgeek@li.nu-x.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®