DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 5A4FlNMv1284552
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 5A4FlNRn1284534
Authentication-Results: delorie.com; dmarc=pass (p=quarantine dis=none) header.from=proton.me
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=proton.me
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 5A4FlNRn1284534
Authentication-Results: delorie.com;
	dkim=pass (2048-bit key, unprotected) header.d=proton.me header.i=@proton.me header.a=rsa-sha256 header.s=protonmail header.b=kDLBchie
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me;
	s=protonmail; t=1762271241; x=1762530441;
	bh=Y9nAS9DGO7B2UW1VLPJYnYaDaZ4QlAGEIRjYjyPYDWs=;
	h=Date:To:From:Subject:Message-ID:In-Reply-To:References:
	 Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
	 Message-ID:BIMI-Selector;
	b=kDLBchie4+R0hbV9KoSKgZhFPGSoTs9GdvcUhgRBePanRX57mP+gYAK+nkUzvJQTn
	 eWFeNTulECOBXHdlawE1pcYKpa4hbCBSYS8YwYLgA7OM3L57ycvYYjbhYc9CsAmTZe
	 jksBzuGe6i1srTTCVc5S9o1whoXc/yBhY8f6cl7uyLvlm6rdobDtTm8b2eNBfHiIhu
	 Fpts2O4PHXkcP+nfpjasSfA+IdF24ZxtuuQl/gcF3bUH+b4GW93AXtoGfGpT0yIi6l
	 19P0GeIGYn6urZSHnNEBYq3uusn7d9rJmLmcIxMB2sxlv6mN8ZOhS4H71kkcHXbw/I
	 VFEDMP2yPJzrA==
Date: Tue, 04 Nov 2025 15:47:19 +0000
To: djgpp AT delorie DOT com
From: "John Doe (altaptitude AT proton DOT me) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Subject: Re: How to cross compile djgpp software from Unix to DOS?
Message-ID: <OLnd8xyaUnFHIvJcgppD8ABd5aQlaqBXBHAAA5eDvIi5nE5COJ0m1vaG7V9kS_B2itiWCy_3MXAbgUnrckb0cwVoVb6CdtnuNoam4WDqqcw=@proton.me>
In-Reply-To: <CAB9Rao818s+FM2A_32_+UyjujksZrpG=zehu+GRVkMjEs800Og@mail.gmail.com>
References: <ahuNp1rAxw3Ko15_Mn4lCOaOI5eV9RjS8SdHWlzh3PZKtZK2wXG6jUKt1P3_YK1jX6BL_bHBdLjobDxyB7FMz3UM5t3t14ACCv3lFR2QIuc=@proton.me> <86v7jsgumx DOT fsf AT gnu DOT org> <V082qFEnlxirTYqs8R-UefRunm4GXvZzZVUYxu7qHKhCztWWHgw1wDY3zLzs9DsUg0BY0KASkEUBK1eansTRxN82AY4HyPVkvpE3w2DzhaI=@proton.me> <CAB9Rao818s+FM2A_32_+UyjujksZrpG=zehu+GRVkMjEs800Og AT mail DOT gmail DOT com>
Feedback-ID: 130132440:user:proton
X-Pm-Message-ID: c6e92ed4994156192b0f2c1ac3aebe49c29e9812
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 5A4FlNRm1284539
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



> I don't think `make bash.exe CC=i586-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.

I believe bash.exe is a target because when running it it tries to do something, whereas when trying with any non existant target make says 'make: *** No rule to make target 'example'.  Stop.'

Regardless the results aren't any better when running just make.