RejectedSoftware Forums

Sign up

Sudden appearance of dub warnings

dub 1.2.0 building a project using dmd 2.073.0 puts out the following warnings on x86_64 Linux.

This seems not to be project specific. It occurs building a working project that previously had no such warnings and has not been changed since when that was so, both before and after dub upgrade and dub --force.

## Warning for package libasync, configuration 32mscoff ##

The following compiler flags have been specified in the package description file. They are handled by DUB and direct use in packages is discouraged. Alternatively, you can set the DFLAGS environment variable to pass custom flags to the compiler, or use one of the suggestions below:

-m32mscoff: Use --arch=x86/--arch=x86_64/--arch=x86_mscoff to specify the target architecture

I get this several times for libasync and memutils, more than once each.

Should I be concerned?

Re: Sudden appearance of dub warnings

On Sun, 12 Feb 2017 15:18:25 GMT, Carl Sturtivant wrote:

dub 1.2.0 building a project using dmd 2.073.0 puts out the following warnings on x86_64 Linux.

Note that this is vibe.d 0.7.30, NOT one of the new betas.

Re: Sudden appearance of dub warnings

Am 12.02.2017 um 19:12 schrieb Carl Sturtivant:

On Sun, 12 Feb 2017 15:18:25 GMT, Carl Sturtivant wrote:

dub 1.2.0 building a project using dmd 2.073.0 puts out the following warnings on x86_64 Linux.

Note that this is vibe.d 0.7.30, NOT one of the new betas.

The warnings will be silenced by the upcoming version 1.2.1 of DUB and
are generally not an immediate issue, it's just that they could in
theory interfere with DUB's own command line logic. Since there is now
support for a "x86_mscoff" architecture, the libraries should simply
remove those manual compiler flags.

I've proposed the corresponding changes:
https://github.com/etcimon/libasync/pull/75
https://github.com/etcimon/memutils/pull/13