From: "Björn Runåker (QIC)" <Bjorn.Runaker@mic.ericsson.se>
To: "'Frank Ch. Eigler'" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: RE: compiling sid in cygwin
Date: Wed, 14 Aug 2002 06:09:00 -0000 [thread overview]
Message-ID: <634E1DDCE357E7479E1EA3B4F5EECB7001A432D7@esealnt879.al.sw.ericsson.se> (raw)
Hello,
Doing:
./configure --disable-nls
make
Result:
...
[directory sid/component/cgen-cpu]
.libs/impgen /usr/lib/libintl.dll.a > .libs/libintl.dll.a-def
Signal 11
make[6]: ** [libcgencpu.la] Error 139
...
Running last command manually results in segmentation fault.
Running make again get you pass this and it stops when building sid.exe
with following errors:
../../component/cgen-cpu/.libs/libcgencpu.a(m32r-asm.o): In function 'm32r_cgen_build_insn_regex':
In function 'm32r-asm.c:454: undefined reference to 'xregcomp'
....
Anybody seen this before?
Suggestions how to solve this?
Regards,
Bjorn
-----Original Message-----
From: Frank Ch. Eigler [mailto:fche@redhat.com]
Sent: Wednesday, August 07, 2002 4:48 PM
To: Björn Runåker (QIC)
Cc: 'sid@sources.redhat.com'
Subject: Re: compiling sid in cygwin
Hi -
On Wed, Aug 07, 2002 at 01:08:16PM +0200, Björn Runåker (QIC) wrote:
> I have problems when compiling sid.
> I can get ./configure to work [...] but
> make stops when it doesn't find msgfmt.
Yes, sid's neighbouring source trees are fragile with respect to
i18n issues. Repeat your configure job, this time with "--disable-nls",
and you will have better luck. An alternative way is to run make with
"MSGFMT=true".
> [...]
> I use latest version of cygwin and latest snapshot of sid.
Sounds good.
- FChE
next reply other threads:[~2002-08-14 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 6:09 Björn Runåker (QIC) [this message]
2002-09-07 9:41 ` Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
2002-08-07 4:11 Björn Runåker (QIC)
2002-08-07 7:48 ` Frank Ch. Eigler
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=634E1DDCE357E7479E1EA3B4F5EECB7001A432D7@esealnt879.al.sw.ericsson.se \
--to=bjorn.runaker@mic.ericsson.se \
--cc=fche@redhat.com \
--cc=sid@sources.redhat.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).