mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Help! Got a "configure: error: C compiler can


From: Nagaev Boris
Subject: Re: [Mingw-cross-env-list] Help! Got a "configure: error: C compiler cannot create executables" when configure.
Date: Sun, 8 Jan 2017 14:18:22 +0000

I have MXE repo in /data/mxe/mxe-after-cleanup
I used the following commands in the directory of libsearpc:

./autogen.sh
export PATH="/data/mxe/mxe-after-cleanup/usr/bin/:$PATH"
./configure --host=i686-w64-mingw32.static
--build=x86_64-unknown-linux-gnu
--prefix=/data/mxe/mxe-after-cleanup/usr/i686-w64-mingw32.static
--enable-static --disable-shared
make
make install

Configure options were taken from definition of macro
MXE_CONFIGURE_OPTS in Makefile.

It works. The following files were installed:

        i686-w64-mingw32.static/bin/searpc-codegen.py
        i686-w64-mingw32.static/include/searpc-client.h
        i686-w64-mingw32.static/include/searpc-named-pipe-transport.h
        i686-w64-mingw32.static/include/searpc-server.h
        i686-w64-mingw32.static/include/searpc-utils.h
        i686-w64-mingw32.static/include/searpc.h
        i686-w64-mingw32.static/lib/libsearpc.a
        i686-w64-mingw32.static/lib/libsearpc.la
        i686-w64-mingw32.static/lib/pkgconfig/libsearpc.pc
        i686-w64-mingw32.static/lib/python2.7/

By the way, consider adding the library to MXE. In that case it could
be built with `make libsearpc`. See http://mxe.cc/#creating-packages

On Sun, Jan 8, 2017 at 5:42 AM, mxe coder <address@hidden> wrote:
> It's here: https://github.com/haiwen/libsearpc
> and here's download link:
> https://github.com/haiwen/libsearpc/archive/v3.1-latest.tar.gz
>
> Sent: Sunday, January 08, 2017 at 9:35 AM
>
> From: "Nagaev Boris" <address@hidden>
> To: "mxe coder" <address@hidden>
> Cc: "mingw-cross-en." <address@hidden>
> Subject: Re: [Mingw-cross-env-list] Help! Got a "configure: error: C
> compiler cannot create executables" when configure.
> What software are you trying to build?
>
> On Sun, Jan 8, 2017 at 12:48 AM, mxe coder <address@hidden> wrote:
>> Yes, I've added the absolute path of "mxe/usr/bin" to PATH by modify
>> .bashrc
>> file, and I've checked it by "export" command in terminal.
>>
>> Sent: Saturday, January 07, 2017 at 11:38 PM
>> From: "Nagaev Boris" <address@hidden>
>> To: "mxe coder" <address@hidden>
>> Cc: "mingw-cross-en." <address@hidden>
>> Subject: Re: [Mingw-cross-env-list] Help! Got a "configure: error: C
>> compiler cannot create executables" when configure.
>> On Sat, Jan 7, 2017 at 1:45 PM, mxe coder <address@hidden> wrote:
>>> Hello everyone,
>>> I've got errors as following when I tried to compile a open-source
>>> project
>>> with "./configure --prefix=/home/release --host=i686-w64-mingw32.static
>>> --build=i686":
>>>
>>> checking for i686-w64-mingw32.static-gcc... i686-w64-mingw32.static-gcc
>>> checking whether the C compiler works... no
>>> configure: error: in `/home/libgo-3.1':
>>> configure: error: C compiler cannot create executables
>>> See `config.log' for more details
>>>
>>> Here's the config.log:
>>>
>>> configure:3229: error: in `/home/libgo-3.1':
>>> configure:3231: error: C compiler cannot create executables
>>>
>>> Here's codes near line 3231 in configure file:
>>>
>>> if test -z "$ac_file"; then :
>>> { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
>>> $as_echo "no" >&6; }
>>> $as_echo "$as_me: failed program was:" >&5
>>> sed 's/^/| /' conftest.$ac_ext >&5
>>> { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
>>> $as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
>>> as_fn_error 77 "C compiler cannot create executables
>>> See \`config.log' for more details" "$LINENO" 5; }
>>> else
>>> { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
>>> $as_echo "yes" >&6; }
>>> fi
>>>
>>> Can someone help, please!
>>
>> Hey
>>
>> Have you added mxe/usr/bin to PATH?
>>
>> --
>> Best regards,
>> Boris Nagaev
>
>
>
> --
> Best regards,
> Boris Nagaev



-- 
Best regards,
Boris Nagaev



reply via email to

[Prev in Thread] Current Thread [Next in Thread]