DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 5A3JUrJb804859 Authentication-Results: delorie.com; dmarc=none (p=none dis=none) header.from=delorie.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=delorie.com X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 5A3JUrVT804838 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=gmail.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 5A3JUrVT804838 Authentication-Results: delorie.com; dkim=pass (2048-bit key, unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20230601 header.b=MwA9pQVr X-Recipient: djgpp AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762198250; x=1762803050; darn=delorie.com; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=v//b6CIH9DMnnUaKRvnCX8NmTaoXFtMgQA+NUnAnn/I=; b=MwA9pQVrA13nNHF8/YQNAleYHOMZKZMCyTc3Ryktzw5yIEZhq1vBBpdXt0nmBwh6mZ HzD5ixzc3yDCn1vT2oF/HEF+RL9oQatA0U5WZgEdnJb7YVvv6McX2W/LAZRTSLPDBRPz LT1ZlgLaQR4Cv8BFZI4+5p2ep1gCbwYNTJvT+TEIIJXbxw6Kx33RSz+O8kUMuXp8wj1x ROxA8jHTe8LCPo+oe+byVpJtsbXtfkoPqR9FpEP6e9ubmop5Dj6UhtD79qbY2BeuSXy2 Osni7GdyI9l909lVrGhw+VIHOLijrP05Jqn8868dkA5JJWPPTNPRpWG6hEydim2EIeRp S1Jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762198250; x=1762803050; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=v//b6CIH9DMnnUaKRvnCX8NmTaoXFtMgQA+NUnAnn/I=; b=XDWgw9jIJQqp1a6TXsCVAc9MvQPitJJWGS3o1EVDEAyZiFnI+N9fPOnoPU6aC5XKl7 zbN6VxH2HqxNtCMO73vECzDgyKdMWxkepc4j2C4mq4iP7od7/YJ7uduHdBD2xQHYQeYA 1FQ2A1qu6vzjdwbymk6r5ZMUR0z6A18t96ptNRJobJ1SE9wNG4XHBa2j9TtWD15Er2fU SA6stvYPSTmXLNgEDz1LR06IM2JTyDX6eQRUoLN8G/XqasQPykbmfgNk8+rnj8sLXGwq Qc60DdtIItFU2/5lljXx2EO8f0qncRduYMlM7Ns6LApNQWIVGkSeLkuuASLeFjE8b4Jt pKuw== X-Gm-Message-State: AOJu0YwBfU4I9rZ72TkxUp7Cm3Z9ifFbGrALPjj+M+rYRpmjJIHds0af oymkdFuBqGiF3hAhFp0AI08+UxxG59OSVdqyIGa7GFF9Y+M4+GzKgeO+/sDwPJnKa9VSu0hF1M7 Hw1VZCX6bpp/C6N6AEAz8oCiRWV+1oSVPgbBS X-Gm-Gg: ASbGncstgD0xgsPeeD10jWEHzI0AEgzBAtfVjSCfZbxm47LYuyvdFFGsW3l7dFebLYf 9wJJsSHq2to5PtTQ+RMsynumtpDh0wiEIhpI2kyN2MxrGlJGT8ZiPWC5InNvr2tVPVn4UBNmX/V 0EU5wB75YROw2NgFGVn7PNFra08h/K8ucasvSfdXgwg5uJdFBkQTyqYA2xN5C2wmMb6bXEAUD6c 4a1RwEao6JUR/V3ynjUWQ0tdCaHqWB/XVW7rFls4hZULLsCyzWyoB3/1zo5cpoJvd7+aXwkAwV4 2Bbimw== X-Google-Smtp-Source: AGHT+IHEhADWnx9JMBjt77pBqvOzj2zd7MN7bRyd767qh1llhCr9DC4N1GhBCJfJYbiEgYdt6jmh7Oc/1izyklwmpyE= X-Received: by 2002:a17:907:1c28:b0:b71:854:4e49 with SMTP id a640c23a62f3a-b710854688emr430400966b.56.1762198248681; Mon, 03 Nov 2025 11:30:48 -0800 (PST) MIME-Version: 1.0 References: <86v7jsgumx DOT fsf AT gnu DOT org> In-Reply-To: From: "Louis Santillan (lpsantil AT gmail DOT com) [via djgpp AT delorie DOT com]" Date: Mon, 3 Nov 2025 11:30:35 -0800 X-Gm-Features: AWmQ_blo1DVT8QZqnNoHDSKX0hYwpfOkaHmXCtj6H2lFiAzZdcoisbaAj2tuZA0 Message-ID: Subject: Re: How to cross compile djgpp software from Unix to DOS? To: djgpp AT delorie DOT com Content-Type: multipart/alternative; boundary="000000000000a2f42b0642b5c03d" Reply-To: djgpp AT delorie DOT com --000000000000a2f42b0642b5c03d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 3, 2025 at 10:54=E2=80=AFAM John Doe (altaptitude AT proton DOT me) [v= ia djgpp AT delorie DOT com] wrote: [SNIP] > Ok i guess Emacs was a bad example, however i'm having trouble with other > djgpp software too. Djgpp's Bash docs also only have instructions for > compiling on DOS, and when i tried running 'make bash.exe > CC=3Di586-pc-msdosdjgpp-gcc' it would fail because it would try to run th= e > .exe file in the directory (./mksyntax.exe) which obviously a GNU/Linux > system can't do so that would fail. I couldn't find where exactly it was > instructed to run those so i couldn't remove that. I had no success runni= ng > the configure scripts myself with --host=3Di586-pc-msdosdjgpp or > CC=3Di586-pc-msdosdjgpp-gcc either. > > I don't think `make bash.exe CC=3Di586-pc-msdosdjgpp-gcc` is a valid target= . `bsh4428s/gnu/bash-4.4.28/djgpp/readme` details the specific environment setup (for DOS) you need and the build process. It does not list `bash.exe` as a target. --000000000000a2f42b0642b5c03d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Nov 3, 2025 at 10:54=E2=80=AFAM J= ohn Doe (altaptitude AT proton DOT me= ) [via djgpp AT delorie DOT com] <djgpp AT delorie DOT com> wrote:
[SNIP]
Ok i guess Emacs was a bad example, ho= wever i'm having trouble with other djgpp software too. Djgpp's Bas= h docs also only have instructions for compiling on DOS, and when i tried r= unning 'make bash.exe CC=3Di586-pc-msdosdjgpp-gcc' it would fail be= cause it would try to run the .exe file in the directory (./mksyntax.exe) w= hich obviously a GNU/Linux system can't do so that would fail. I couldn= 't find where exactly it was instructed to run those so i couldn't = remove that. I had no success running the configure scripts myself with --h= ost=3Di586-pc-msdosdjgpp or CC=3Di586-pc-msdosdjgpp-gcc either.


I don't think `make bash.exe CC=3D= i586-pc-msdosdjgpp-gcc` is a valid target.=C2=A0 `bsh4428s/gnu/bash-4.4.28/= djgpp/readme` details the specific environment setup (for DOS) you need and= the build process.=C2=A0 It does not list `bash.exe` as a target.=C2=A0
--000000000000a2f42b0642b5c03d--