From: david mosberger <dmosberger@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: debian/testing cannot compile static with gcc3.3.5
Date: Fri, 19 Aug 2005 18:40:47 +0000 [thread overview]
Message-ID: <ed5aea4305081911405ec357e0@mail.gmail.com> (raw)
In-Reply-To: <20050819162011.GB6405@frankl.hpl.hp.com>
I'm running Debian/unstable and static linking of a dummy hello world
program works fine, both with gcc 3.3.6 and gcc 4.0.2.
debian-ia64@lists.debian.org might be a better place to take this
discussion, though.
--david
On 8/19/05, Stephane Eranian <eranian@hpl.hp.com> wrote:
> Hello,
>
> I recently upgraded my system to the latest testing.
> Since then, I cannot comile any program with static linking:
>
> $ cc hello.c -o hello -g -static
> /usr/bin/ld: __libc_errno: TLS definition in /usr/lib/gcc-lib/ia64-linux/3.3.5/../../../libc.a(errno.o) section .tbss mismatches non-TLS reference in /usr/lib/gcc-lib/ia64-linux/3.3.5/../../../libc.a(check_fds.o)
> /usr/lib/gcc-lib/ia64-linux/3.3.5/../../../libc.a: could not read symbols: Bad value
> collect2: ld returned 1 exit status
>
> I have the following packages installed. So it seems that somehow libc6.1-dev
> has a problem compared to the shared libc.
>
> ii binutils 2.16.1-2 The GNU assembler, linker and binary utiliti
> ii binutils-dev 2.16.1-2 The GNU binary utilities (BFD development fi
> ii binutils-doc 2.15-5 Documentation for the GNU assembler, linker
> ii libc6.1 2.3.2.ds1-22 GNU C Library: Shared libraries and Timezone
> ii libc6.1-dbg 2.3.2.ds1-22 GNU C Library: Libraries with debugging symb
> ii libc6.1-dev 2.3.2.ds1-22 GNU C Library: Development Libraries and Hea
> ii libc6.1-pic 2.3.2.ds1-22 GNU C Library: PIC archive library
> ii libc6.1-prof 2.3.2.ds1-22 GNU C Library: Profiling Libraries
> ii gcc 3.3.5-1 The GNU C compiler
> ii gcc-3.3 3.3.5-8 The GNU C compiler
> ii gcc-3.3-base 3.3.5-8 The GNU Compiler Collection (base package)
> ii gcc-3.4 3.4.3-6 The GNU C compiler
> ii gcc-3.4-base 3.4.3-6 The GNU Compiler Collection (base package)
> ii gcc-4.0 4.0.1-2 The GNU C compiler
> ii gcc-4.0-base 4.0.1-2 The GNU Compiler Collection (base package)
> ii libgcc1 4.0.1-2 GCC support library
>
> --
>
> -Stephane
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536
next prev parent reply other threads:[~2005-08-19 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 16:20 debian/testing cannot compile static with gcc3.3.5 Stephane Eranian
2005-08-19 16:37 ` Andreas Schwab
2005-08-19 18:35 ` Christoph Lameter
2005-08-19 18:40 ` david mosberger [this message]
2005-08-19 22:49 ` Peter Chubb
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=ed5aea4305081911405ec357e0@mail.gmail.com \
--to=dmosberger@gmail.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.