[Top][All Lists]

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

Re: Compiling sed using Mingw under Windows 10-64

From: Assaf Gordon
Subject: Re: Compiling sed using Mingw under Windows 10-64
Date: Tue, 12 Jun 2018 01:46:11 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

(adding address@hidden mailing list)


On 10/06/18 09:08 PM, address@hidden wrote:
I’m experiencing an issue while attempting to compile Sed 4.5 on Windows. Specifically, I’m getting this error:

Making all in gnulib-tests

make[2]: *** No rule to make target 'lib/netinet/in.h', needed by 'all'.  Stop.

make[2]: *** Waiting for unfinished jobs....

make[2]: Entering directory '/c/mingw_distro_setup/build/gnulib-tests'

   GEN      dirent.h

make[2]: Leaving directory '/c/mingw_distro_setup/build/gnulib-tests'

make[2]: Entering directory '/c/mingw_distro_setup/build/gnulib-tests'

   GEN      inttypes.h

make[2]: Leaving directory '/c/mingw_distro_setup/build/gnulib-tests'

make[2]: Entering directory '/c/mingw_distro_setup/build/gnulib-tests'

   GEN      arpa/inet.h

make[2]: Leaving directory '/c/mingw_distro_setup/build/gnulib-tests'

make[1]: *** [Makefile:2819: all-recursive] Error 1

make: *** [Makefile:2081: all] Error 2

Sed’s Makefile apparently doesn’t have a target for lib/netinet/in.h, meaning that it isn’t getting generated (or at least not generated properly) when I call configure.

This is the configure call I’m using:

./configure –build=x86_64-w64-mingw32 –host=x86_64-w64-mingw32 –prefix=../dest –disable-nls

For reference, I’m running the script on Windows 10 x64 with MSYS2 and MinGW-w64 (latest versions for both).

Few issues here:

The line you reported above says "Making all in gnulib-tests".
These are unit-tests for gnulib (the gnu portability library which
is used by sed).
When this message appears, it means sed was already built successfully,
and sed's unit-tests have already been executed.

While it is nice to run gnulib's tests, it is not needed for casual installations.

To verify that sed itself is built, please try the following:
    make check SUBDIRS=.

The last command ensures only sed's tests are executed, not gnulib's tests. It should succeed (unless there are test failure on your platform).

The message "make[2]: *** Waiting for unfinished jobs...." hints
you are building in parallel (using "make -j").
This might be the cause for the gnulib-tests failures - it could be
that some intricate dependency for one of the header files do not
play nicely in parallel builds.
If you do want to run the gnulib-tests (e.g. with "make check"),
try once without a parallel build - if that succeeds,
then it is likely related to the makefile rules
(and if so, we would appreciate to hear back a report about it).

If you are building in a native environment (i.e. compiling on the same
system you intend to run the binaries) - why are the "--host" and
"--build" parameters needed in your "./configure" ?
Does the build fail without them?

 - Assaf

reply via email to

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