<feed xmlns='http://www.w3.org/2005/Atom'>
<title>busybox-w32/scripts, branch symlink</title>
<subtitle>A mirror of https://github.com/rmyorston/busybox-w32.git
</subtitle>
<id>https://git.lua4.win/busybox-w32/atom?h=symlink</id>
<link rel='self' href='https://git.lua4.win/busybox-w32/atom?h=symlink'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/'/>
<updated>2021-02-21T10:35:21+00:00</updated>
<entry>
<title>.gitignore: support building on Windows</title>
<updated>2021-02-21T10:35:21+00:00</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2021-02-20T21:33:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=379e128a3a4f5343cbd4a9f1be3538cf76af82e2'/>
<id>urn:sha1:379e128a3a4f5343cbd4a9f1be3538cf76af82e2</id>
<content type='text'>
These items are already listed, albeit without `.exe` suffix.
Presumably, this is because BusyBox-w32 is traditionally cross-compiled
on Linux.

However, we are about to introduce a CI build definition that builds
BusyBox-w32 in MSYS2 (using mingw-w64-gcc), meaning that those
executables might very well exist _with_ `.exe` suffix.

Let's ignore those, too.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
</content>
</entry>
<entry>
<title>win32: fixes to build on Windows/MSYS2/mingw-w64</title>
<updated>2021-02-21T09:51:08+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2021-02-20T13:07:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=4bca7987f38b24867d93efc4a11a1ef661734056'/>
<id>urn:sha1:4bca7987f38b24867d93efc4a11a1ef661734056</id>
<content type='text'>
To investigate GitHub issue #200 it was necessary to perform
build on Window using the MSYS2/mingw-w64 toolchain.  This
threw up some issues:

- The settings for _WIN32_WINNT and __USE_MINGW_ANSI_STDIO differ
  from those in Fedora resulting in compiler errors and warnings.
  Force the defaults I'm used to.

- The workaround to allow native compilation of mconf.c was broken
  by a subsequent upstream change.  Make it work again.
</content>
</entry>
<entry>
<title>Merge branch 'busybox' into merge</title>
<updated>2021-01-14T13:28:49+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2021-01-14T13:28:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=89963b524d211e1aec12b72b3725be05ee95c8cf'/>
<id>urn:sha1:89963b524d211e1aec12b72b3725be05ee95c8cf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tar: add TODO about a bug with non-writable directories on extract</title>
<updated>2021-01-01T12:34:25+00:00</updated>
<author>
<name>Denys Vlasenko</name>
<email>vda.linux@googlemail.com</email>
</author>
<published>2021-01-01T12:34:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=9daa877d6bdc8dd470ffd86839550c54957eac73'/>
<id>urn:sha1:9daa877d6bdc8dd470ffd86839550c54957eac73</id>
<content type='text'>
Signed-off-by: Denys Vlasenko &lt;vda.linux@googlemail.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'busybox' into merge</title>
<updated>2020-07-09T12:10:58+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2020-07-09T12:10:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=9c0b2f7020d7c30b21a930ef54be632e092e533b'/>
<id>urn:sha1:9c0b2f7020d7c30b21a930ef54be632e092e533b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>randomconfig fixes</title>
<updated>2020-06-23T22:27:37+00:00</updated>
<author>
<name>Denys Vlasenko</name>
<email>vda.linux@googlemail.com</email>
</author>
<published>2020-06-23T22:27:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=7c443d110d4dc51ba48bad8ed1427716b754bf2e'/>
<id>urn:sha1:7c443d110d4dc51ba48bad8ed1427716b754bf2e</id>
<content type='text'>
Signed-off-by: Denys Vlasenko &lt;vda.linux@googlemail.com&gt;
</content>
</entry>
<entry>
<title>randomconfig fixes</title>
<updated>2020-06-23T19:28:19+00:00</updated>
<author>
<name>Denys Vlasenko</name>
<email>vda.linux@googlemail.com</email>
</author>
<published>2020-06-23T19:28:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=5fa5c4bde8b9ab75fa0ed37ee2fafca3fd46288a'/>
<id>urn:sha1:5fa5c4bde8b9ab75fa0ed37ee2fafca3fd46288a</id>
<content type='text'>
Signed-off-by: Denys Vlasenko &lt;vda.linux@googlemail.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'busybox' into merge</title>
<updated>2020-05-29T10:03:33+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2020-05-29T09:49:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=53c09d0e1720bd927a2995f87df324a9854f1771'/>
<id>urn:sha1:53c09d0e1720bd927a2995f87df324a9854f1771</id>
<content type='text'>
</content>
</entry>
<entry>
<title>build system: remove KBUILD_STR()</title>
<updated>2020-04-29T12:52:19+00:00</updated>
<author>
<name>Jean-Philippe Brucker</name>
<email>jean-philippe@linaro.org</email>
</author>
<published>2020-03-12T16:19:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=ed8af51b600fd16d22c6663a241547c3a9d7f2b4'/>
<id>urn:sha1:ed8af51b600fd16d22c6663a241547c3a9d7f2b4</id>
<content type='text'>
When using GNU Make &gt;=4.3, the KBUILD_STR() definition interferes badly
with dependency checks during build, and forces a complete rebuild every
time Make runs.

In if_changed_rule, Kconfig checks if the command used to build a file
has changed since last execution. The previous command is stored in the
generated .&lt;file&gt;.o.cmd file. For example applets/.applets.o.cmd defines
a "cmd_applets/applets.o" variable:

	cmd_applets/applets.o := gcc ... -D"KBUILD_STR(s)=#s" ...

Here the '#' should be escaped with a backslash, otherwise GNU Make
interprets it as starting a comment, and ignore the rest of the
variable. As a result of this truncation, the previous command doesn't
equal the new command and Make rebuilds each target.

The problem started to appear when GNU Make 4.3 (released January 2020),
introduced a backward-incompatible fix to macros containing a '#'. While
the above use of '#', a simple Make variable, still needs to be escaped,
a '#' within a function invocation doesn't need to be escaped anymore.
As Martin Dorey explained on the GNU Make discussion [1], the above
declaration is generated from make-cmd, defined as:

	make-cmd = $(subst \#,\\\#,$(subst $$,$$$$,$(call escsq,$(cmd_$(1))))

Since GNU Make 4.3, the first argument of subst should not have a
backslash. make-cmd now looks for literally \# and doesn't find it, and
as a result doesn't add the backslash when generating .o.cmd files.

[1] http://savannah.gnu.org/bugs/?20513

We could fix it by changing make-cmd to "$(subst #,\#,...)", but to
avoid compatibility headaches, simply get rid of the KBUILD_STR
definition, as done in Linux by b42841b7bb62 ("kbuild: Get rid of
KBUILD_STR"). Quote the string arguments directly rather than asking the
preprocessor to quote them.

Signed-off-by: Jean-Philippe Brucker &lt;jean-philippe@linaro.org&gt;
Signed-off-by: Denys Vlasenko &lt;vda.linux@googlemail.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'busybox' into merge</title>
<updated>2019-03-12T13:47:44+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2019-03-12T13:47:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=fd0e6a01a68047e959ef13f3161ce302b438d2b1'/>
<id>urn:sha1:fd0e6a01a68047e959ef13f3161ce302b438d2b1</id>
<content type='text'>
</content>
</entry>
</feed>
