From: "Frank van den Beuken" <Frank.van.den.Beuken@rdlabs.qasystems.nl>
To: <binutils@sourceware.cygnus.com>
Subject: RE: still reloc overflow?
Date: Wed, 05 Jul 2000 01:56:00 -0000 [thread overview]
Message-ID: <000101bfe667$689f17e0$410410ac@geneve.qasehv.nl> (raw)
I found that the problem I'd like to be solved is
http://sourceware.cygnus.com/ml/binutils/2000-03/msg00203.html
What is the status of this problem?
I really would like this to be fixed so that I can replace
MSVC++ in our build procedure with the solaris->mingw32
crossgcc.
Greetings,
Frank
> This works. Thanks!
> However, I still have the "reloc overflow" that I hoped would
> be solved:
> /cadappl/gcc/2.95.2/i386-pc-mingw32/bin/as:
> transLALRParser.o: reloc overflow: 0x17681 > 0xffff
> transLALRParser.o: File truncated
>
> I thought this was fixed, or is this not the same problem
> as mentioned in
> http://sourceware.cygnus.com/ml/binutils/2000-04/msg00223.html
>
> Greetings,
> Frank
>
> > If you can't download the CVS tree of libtool, you may just edit
> > configure scripts and, wherever you find:
> >
> > case "$target" in
> > NONE) lt_target="$host" ;;
> > *) lt_target="$target" ;;
> > esac
> >
> > replace it with:
> >
> > lt_target="$host"
>
>
next reply other threads:[~2000-07-05 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-05 1:56 Frank van den Beuken [this message]
2000-07-05 2:50 ` Frank van den Beuken
2000-07-05 4:14 ` QNX Neutrino (new targets, GPL) Anders Norlander
2000-07-05 13:12 ` Ian Lance Taylor
2000-07-05 21:58 ` Anders Norlander
-- strict thread matches above, loose matches on Subject: below --
2000-07-04 2:34 unable to build binutils-2.10 solaris->i386-pc-mingw32 Alexandre Oliva
2000-07-04 3:32 ` still reloc overflow? Frank van den Beuken
2000-07-04 4:23 ` Alan Modra
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='000101bfe667$689f17e0$410410ac@geneve.qasehv.nl' \
--to=frank.van.den.beuken@rdlabs.qasystems.nl \
--cc=binutils@sourceware.cygnus.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).