gdbserver cross compile

gdbserver cross compile

[Harris, Jeff]

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?  

Thanks,
Jeff

Re: gdbserver cross compile

[Daniel Jacobowitz]

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

Re: GdbServer cross compile

[Stan Shebs]

On Wed, May 20, 2015 at 11:36 AM, Uladzimir Kryvian
<newinferno@gmail.com> wrote:
> Hello!
> I want compile gdb server for AmigaOS. It uses m68k processor.
> I've compiled "https://github.com/cahirwpz/m68k-amigaos-toolchain" and
> want to use it in gdbserver compilation.
> But I don't know how to do that?
>
> Can you help me with cross-compiling gdbserver for it?

This is going to be disappointing I'm afraid - gdbserver is not a
general-purpose stub.  It expects to call a variety of OS system
facilities to do its process control and such, and there is no AmigaOS
port.  Existing ports are Linux, Neutrino, and Win32; the Win32 port
might be the simplest starting point for a port, but to finish will
need some in-depth understanding of the Exec kernel and its API/ABI.

Stan

GdbServer cross compile

[Uladzimir Kryvian]

Hello!
I want compile gdb server for AmigaOS. It uses m68k processor.
I've compiled "https://github.com/cahirwpz/m68k-amigaos-toolchain" and
want to use it in gdbserver compilation.
But I don't know how to do that?

Can you help me with cross-compiling gdbserver for it?

RE: gdbserver cross compile

[Harris, Jeff]

That's what I was planning on doing.  It does appear to work.

-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@mvista.com] 
Sent: Monday, May 05, 2003 5:53 PM
To: Harris, Jeff
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver cross compile


To be honest, I don't remember how I solved this in our local
environment... you could just rebuild that one configure file locally
with 2.5x if that works.  I think it's simple enough to work in both. 
Most other configure files in the source are not.

On Mon, May 05, 2003 at 05:46:16PM -0400, Harris, Jeff wrote:
> 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
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: gdbserver cross compile

[Daniel Jacobowitz]

To be honest, I don't remember how I solved this in our local
environment... you could just rebuild that one configure file locally
with 2.5x if that works.  I think it's simple enough to work in both. 
Most other configure files in the source are not.

On Mon, May 05, 2003 at 05:46:16PM -0400, Harris, Jeff wrote:
> 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
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

RE: gdbserver cross compile

[Harris, Jeff]

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