public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Stefano Gallina <warx_sg@yahoo.com>
Cc: sid@sources.redhat.com
Subject: Re: New kind of error building SID ! Please Help !
Date: Mon, 03 Feb 2003 18:26:00 -0000	[thread overview]
Message-ID: <20030203132655.B7176@redhat.com> (raw)
In-Reply-To: <20030203104740.48710.qmail@web41114.mail.yahoo.com>; from warx_sg@yahoo.com on Mon, Feb 03, 2003 at 11:47:40AM +0100

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

Hi -

> [...] this time i got the following error....please help me !:
> 
> ../../component/cgen-cpu/.libs/libcgencpu.a(xstormy16-dis.o)(.text+0x289):
> In function `xstormy16_cgen_print_operand':
> /SOURCETREE/src/sid/component/cgen-cpu/xstormy16/../../../../opcodes/xstormy16-dis.c:171: undefined reference to `_dcgettext__'
> [...]

For some reason, especially on cygwin, the NLS functions of opcodes/bfd
don't consistently get built into sid correctly.  Try reconfiguring your
build tree with "--disable-nls".


- FChE

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

  reply	other threads:[~2003-02-03 18:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-01 14:21 new sid snapshot available fche
2003-02-03 10:47 ` New kind of error building SID ! Please Help ! Stefano Gallina
2003-02-03 18:26   ` Frank Ch. Eigler [this message]
2003-02-04 10:05 ` File not found ! building Sid ! Help Stefano Gallina
2003-02-06  9:40 ` Sid building under Linux ok...but... Help Stefano Gallina
2003-02-06 20:39   ` Frank Ch. Eigler
2003-02-15 10:43     ` Error Building Ecos with RedHat 8.0 Stefano Gallina
2003-02-15 12:18       ` I didn't apply the path to build Ecos! SORRY ! Stefano Gallina
2003-02-15 13:47       ` Error Building Ecos with RedHat 8.0 Gary D. Thomas
2003-02-16 13:23       ` Ben Elliston

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=20030203132655.B7176@redhat.com \
    --to=fche@redhat.com \
    --cc=sid@sources.redhat.com \
    --cc=warx_sg@yahoo.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).