From: Michael Shatz <shatz@dsit.co.il>
To: gdb@sourceware.org
Subject: Re: Problem building cross-debugger
Date: Wed, 13 Feb 2008 17:49:00 -0000 [thread overview]
Message-ID: <15461364.post@talk.nabble.com> (raw)
In-Reply-To: <15419409.post@talk.nabble.com>
Michael Shatz wrote:
>
>
>
> Jim Blandy wrote:
>>
>>
>> "Gerrit van Niekerk" <gerritvn at gpvno.co.za> writes:
>>>>> I am trying to use Cygwin to build a Cygwin host, DJGPP target version
>>>>> of GDB:
>>>>> config --target=djgpp All libraries seem to build ok (make does not
>>>>> stop), but
>>>>> the final link gives a number of undefined references
>>>
>>>> There is now only one undefined reference remaining: `_bfd_i386_arch'
>>>
>>> This is turning out to be a very one-sided thread :)
>>> I managed to get the link phase to work by explicitly including
>>> ../bfd/cpu-i386.o in the gcc command doing the final link. Perhaps
>>> the GDB maintainers can have a look at the cause of the problem.
>>
>> I think the reason you haven't gotten much interaction is that you may
>> be the only person on the list who's working with such a
>> configuration. If you could figure out the source of the problem and
>> suggest a patch, that would get things rolling.
>>
>>
>
> I got exactly the same problem building i386-elf target on i686-pc-cygwin
> host with gcc 3.4.4. The problem exists both for binutils-2.16.1 and for
> binutils-2.17.
>
> Thank you, Gerrit. Your tip helped me to go on.
> Other errors prevented me from building readelf.exe. Hopefullly I could
> live with one from standard cygwin distribution.
>
>
Finally found the problem.
It's all about cygwin "textmode" mount huck.
When the build drive (or may be source, or both, in my case they were the
same) is mounted in the text mode the following command misbehaves:
/bin/sh ./libtool --tag=CC --mode=link i686-pc-cygwin-gcc -W -Wall
-Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -o libbfd.la
-rpath /usr/local/emb386/i686-pc-cygwin/i386-elf/lib -release `cat
libtool-soversion` archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo
cache.lo coffgen.lo corefile.lo format.lo init.lo libbfd.lo opncls.lo
reloc.lo section.lo syms.lo targets.lo hash.lo linker.lo srec.lo binary.lo
tekhex.lo ihex.lo stabs.lo stab-syms.lo merge.lo dwarf2.lo simple.lo `cat
ofiles`
Either 'libtool' or, more likely, 'sh' somehow ignores the tail of the
'ofiles' file which happens to contain the cpu-i386.o
When running from binary-mounted drive everything compiles as expected.
Hope it helps.
--
View this message in context: http://www.nabble.com/Problem-building-cross-debugger-tp14897094p15461364.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-02-13 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 22:20 Gerrit van Niekerk
2008-01-18 9:36 ` Gerrit van Niekerk
2008-01-18 16:26 ` Gerrit van Niekerk
2008-01-18 18:53 ` Jim Blandy
2008-01-18 19:27 ` Gerrit van Niekerk
2008-02-11 20:02 ` Michael Shatz
2008-02-13 17:49 ` Michael Shatz [this message]
2008-02-13 20:21 ` Gerrit van Niekerk
2008-02-13 21:19 ` Brian Dessent
2008-02-13 20:49 ` Dave Korn
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=15461364.post@talk.nabble.com \
--to=shatz@dsit.co.il \
--cc=gdb@sourceware.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