linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: gcc and threads
Date: Fri, 26 Nov 2004 21:26:07 +0100	[thread overview]
Message-ID: <20041126202607.GY2067@lug-owl.de> (raw)
In-Reply-To: <B0004146823@hermes.imsd.uni-mainz.de>

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

On Thu, 2004-11-25 17:25:54 +0100, Christian Stalp <stalp@imbei.uni-mainz.de>
wrote in message <B0004146823@hermes.imsd.uni-mainz.de>:
> Hello everybody,
> does anyone know, how to enable the thread-support for gcc ?

There are several parts that need proper configury to actually reach a
multi-threaded application:

	- a thread library (typically linuxthreads or NPTL) is needed
	- GCC needs to make use out of that
	- your application must use it (pthread_create() et al.) and of
	  course link agains it (-lpthread)

If you're a typical Linux user on a mainstream platform (ie. you can
install your distribution's libc and gcc), then you can just start
hacking a thread-using application.

If you're working on the embedded border, you've probably to first build
a cross compiler. This is a major task, you may want to look at
"crosstool", a number of scripts to aid the user in this task, written
by Dan Kegel.

However, your question isn't specific in any way, so you may want to ask
another question not that broad :-)

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-11-26 20:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25 16:25 gcc and threads Christian Stalp
2004-11-26 20:26 ` Jan-Benedict Glaw [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=20041126202607.GY2067@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).