From: "Matías López Bergero" <mlopezb@udesa.edu.ar>
To: linux-admin@vger.kernel.org
Subject: Re: configure error in glibc 2.3.3
Date: Wed, 08 Sep 2004 18:28:55 -0300 [thread overview]
Message-ID: <413F7997.1070702@udesa.edu.ar> (raw)
In-Reply-To: <413F5E37.8040804@udesa.edu.ar>
Matías López Bergero wrote:
> Hello,
> I'm tring to upgrade my GNU libc, but I'm geting an error wen I ran the
> configure script.
>
> This is the error message:
>
> running configure fragment for sysdeps/i386/elf
> running configure fragment for nptl/sysdeps/phthread
> configure: error: CFI directive support in assembler is required
I have had upgrade the version of GNU assembler and that solved the
error message in the configure procedure, but a new one has destroyed my
happiness :-P
This is the new error that I get during the configure process:
checking for forced unwind support... no
configure: error: forced unwind support is required
So far, I couldn't find the source of this error message.
The lack of unwind is in the compiler?
How can I add or enable the unwind support??
Please apologies if this is a very sealy question, but the only
information that I was able to find was a libunwind library, that come
with some rpm based distros. Unfortunately I'm using redhat 8, and I
couldn't find the package that provides that library.
Best Regards,
Matías.
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2004-09-08 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 19:32 configure error in glibc 2.3.3 Matías López Bergero
2004-09-08 21:28 ` Matías López Bergero [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=413F7997.1070702@udesa.edu.ar \
--to=mlopezb@udesa.edu.ar \
--cc=linux-admin@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).