From: "Harris, Jeff" <JeffH@aiinet.com>
To: 'Daniel Jacobowitz' <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: RE: gdbserver cross compile
Date: Mon, 05 May 2003 21:47:00 -0000 [thread overview]
Message-ID: <3B785392832ED71192AE00D0B7B0D75B1C647D@aimail.aiinet.com> (raw)
I tried setting both cross_compiling and ac_cv_prog_cc_cross environment
variables to "yes" before running configure. Neither seemed to stop it from
running its program and overriding my values.
In thinking about setting ac_cv_header_stdc to yes, this also won't help
since the problem program, the one which checks ctype macros, will still be
run unless I can get cross_compiling to be set to "yes".
Jeff
-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@mvista.com]
Sent: Monday, May 05, 2003 5:35 PM
To: Harris, Jeff
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver cross compile
On Mon, May 05, 2003 at 05:29:48PM -0400, Harris, Jeff wrote:
> I was having problems with getting gdbserver to correctly detect whether
it
> is being built with a cross-compiler or not. I was trying to
cross-compile
> from i386 (RedHat 7.2) to i386(gcc 3.2.3 and glibc 2.3.2). The configure
> script for gdbserver looks to have been created with an old version of
> autoconf (2.13 I believe). The mechanism it uses to detect a cross
compiler
> simply tries to compile a simple program and run it. If it runs, it
decides
> it isn't cross-compiling otherwise it is cross-compiling.
>
> My problem was that while this program runs with the cross-compiler, the
> program to detect whether standard C headers are used does not run. As a
> result, the STDC_HEADERS #define is not set and ultimately a compile error
> to occur.
>
> There doesn't seem to be a way to override the configure script's
detection
> mechanism. However, if I rerun autoconf (version 2.53) in the gdbserver
> directory, the resulting configure script is updated to include better
> logic. Basically, it compares the build and host options to configure to
> determine its cross-compile state. This mechanism works for me since I
have
> different values for these options.
>
> Is an updated version of configure something that would be considered for
> GDB 5.4?
Sadly, no. You can't use autoconf 2.5x with the current source tree,
in general; the conversion process is still being talked about.
It's pretty easy to fake out the 2.13 logic for this case. I don't
remember exactly what the magic was, since I can't find any specific
reference to it in our cross build scripts; but all you should need to
do is preload one of the configure script's cache variables with
something that says no, don't run programs.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2003-05-05 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 21:47 Harris, Jeff [this message]
2003-05-05 21:53 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2015-05-20 16:36 GdbServer " Uladzimir Kryvian
2015-05-20 16:51 ` Stan Shebs
2003-05-05 22:06 gdbserver " Harris, Jeff
2003-05-05 21:30 Harris, Jeff
2003-05-05 21:35 ` Daniel Jacobowitz
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=3B785392832ED71192AE00D0B7B0D75B1C647D@aimail.aiinet.com \
--to=jeffh@aiinet.com \
--cc=drow@mvista.com \
--cc=gdb@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).