bug#29620: closed (configure fails when cross-compiling for the same architecture)

[GNU bug Tracking System]

Your message dated Mon, 10 Aug 2020 15:44:09 +0000
with message-id 
<CAOqdjBf225TCWucRY6KjREkoeFfMbqpg8m1FssGxTcxoR8Wu7Q@mail.gmail.com>
and subject line Re: bug#29620: configure fails when cross-compiling for the 
same architecture
has caused the debbugs.gnu.org bug report #29620,
regarding configure fails when cross-compiling for the same architecture
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
29620: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29620
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> configure fails when cross-compiling for the same architecture
>
>
>
>
> Date: 
>
> Sat, 9 Dec 2017 00:10:05 +0000
>
>
>
>
> I tried building Paul's MPX patch on a CPU that doesn't support MPX,
> so I could run the executable with Intel's CPU emulator. I used
> ./configure CFLAGS="-O2 -g3 -mmpx -fcheck-pointer-bounds", but that
> failed because the executable produced by the tputs test cannot run
> (natively) on my CPU.
>
> It would be nice to have a configure option to specify that while
> build and target machines share the same architecture, they don't
> share the same -m flags, so that we're effectively cross-compiling. Is
> this possible with autoconf?
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#29620: configure fails when cross-compiling for the same architecture
>
>
>
>
> Date: 
>
> Mon, 10 Aug 2020 15:44:09 +0000
>
>
>
>
> On Mon, Aug 10, 2020 at 3:42 PM Stefan Kangas <stefan@marxist.se> wrote:
> > So should this be closed?
>
> Yes, thanks!
>
>
> --- End Message ---