Liste des Groupes | Revenir à c theory |
On Tue, 13 May 2025 10:32:48 -0000 (UTC), vallor <vallor@cultnix.org>Compiles with Microsoft Visual Studio Community Edition 2017
wrote in <vvv74g$1mff2$1@dont-email.me>:
On Mon, 28 Apr 2025 07:40:12 +0100, Richard Heathfield <rjh@cpax.org.uk>So to get it to compile -m32 with its included headers, I have to
wrote in <vun7sc$2fjjl$3@dont-email.me>:
>On 28/04/2025 06:22, vallor wrote:>On Sun, 27 Apr 2025 21:06:29 -0400, Richard Damon>
<richard@damon-family.org> wrote in
<8d96b4dc99c7e8643b6fda45f200891d920b2acd@i2pn2.org>:
>Which is just an admission that your HHH's are not actual correct>
emulator, and you can only apply that statement in the version of
your claims where you retract your claim about Halt7.c being part of
the system (as then then is one and only one HHH), and thus your DD
just is not a program unless you include HHH as part of it, and thus
each is a DIFFFERENT input.
Sorry to butt in...
>
Where does one find this Halt7.c?
<https://github.com/plolcott/x86utm>
>
(If you're expecting something amazing, prepare yourself for a
disappointment.)
Thank you.
>
Looks complicated. Appears to obfuscate the issue.
do this:
*DON'T DO THIS* // sudo apt install linux-libc-dev:i386 // *DON'T DO THIS*
Inspecting the results of what it wanted to do (removing a lot
of the system), it was apparent that it would screw up my
workstation royally.
So, I thought I'd try building Halt7.o 64-bit, from whose warnings
it was apparent that this is hard-coded for 32-bits, including 32-bit
pointers.
$ egrep "warning|note" nohup.out | wc -l
74
I guess I could install a 32-bit virtual machine and try it there,
but I'm not _that_ interested.
Les messages affichés proviennent d'usenet.