X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Date:	Sat, 05 Aug 2023 11:58:02 +0000
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
	s=protonmail3; t=1691236698; x=1691495898;
	bh=k4KgHyFcwjBHD8iS0CgZOkrXET13WphDTfzb63529PY=;
	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=xC+4dwRFenrbn083orJzDw+pezClD5YNf6/T5IACDokYIq1jkA3phkZLpzYttHDIv
	tyt/deYcEnQfuNvN9Xonu2nIY+mThv1qAxD4/l5CtHbyhiiEimk9McaA+5NQj0NyES
	jJIalanPliUxuV/JvXD0V3pMl+4hDPzeg4GTeHb9gsQhFqs+07xbAfUaXwsJ+N+Xfd
	WjLHuQY4/ZL5DUxQ/t6CjY9vAS05LWhtoN8hMUzSJ/wJ2kq/1alDfSCgThQKPoo8Tu
	AAIHEzJQ7ijV2ONTaFn/LWh6ifrtF3xfjf65rPyLbjvIny9eNcxqRj9yZ62jAdX7Pd
	UP++qAVlY3MyA==
To:	djgpp AT delorie DOT com
From:	"gnufan42 (gnufan42 AT protonmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Subject:	Re: compilation of sqlite3 on dos using djgpp
Message-ID:	<HLMPpSIC9AG_-6AOOqQ-0_FrhFiQcrE2UST2yRRJnG6-AGqU1_1i1PRnRj0x0TSV406lf8iy3Kj1vM6X8cww834BagchZkotRuv4K5o1fQM=@protonmail.com>
In-Reply-To:	<e2405853-1614-4aae-b290-9f094171af07n@googlegroups.com>
References:	<43bcdb29-6ac3-4cdf-a0ca-e73adb60bf91 AT googlegroups DOT com> <e968bcf9-dc60-48cf-b071-51186badd430 AT googlegroups DOT com> <e2405853-1614-4aae-b290-9f094171af07n AT googlegroups DOT com>
Feedback-ID:	32728074:user:proton
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id 375BwKkw004205
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

------- Original Message -------
On Wednesday, February 22nd, 2023 at PM 10:57, HILMAN AHWAS A. (hilmanahwaa AT gmail DOT com) [via djgpp AT delorie DOT com] <djgpp AT delorie DOT com> wrote:


> On Monday, February 18, 2013 at 2:02:33 AM UTC+7, <@email omitted> wrote:
> 
> > Well, on a lazy Sunday afternoon I tried to compile SQLite too.
> > 
> > The following steps allowed to compile it:
> > 
> > 1. run "configure --disable-threadsafe"
> > 
> > 2. modify this in sqlite3.c:
> > 
> > #ifdef DJGPP
> > { "fstat", 0, 0 },
> > //#define osFstat(a,b,c) 0
> > #define osFstat(a,b) 0 //djgpp - replacing above
> > #define MAP_SHARED 0
> > #define MAP_FAILED 0
> > #define ETIMEDOUT 9000 //unused number
> > #define ENOTCONN 9001 //unused number
> > 
> > #else
> > 
> > 3. take out munmap:
> > 
> > for(i=0; i<p->nRegion; i++){
> > if( p->h>=0 ){
> > //djgpp munmap(p->apRegion[i], p->szRegion);
> > }else{
> > sqlite3_free(p->apRegion[i]);
> > }
> > }
> > 
> > 4. take out mmap:
> > 
> > if( pShmNode->h>=0 ){
> > /* djgpp
> > pMem = mmap(0, szRegion,
> > pShmNode->isReadonly ? PROT_READ : PROT_READ|PROT_WRITE,
> > MAP_SHARED, pShmNode->h, szRegion*(i64)pShmNode->nRegion
> > );
> > */
> > if( pMem==MAP_FAILED ){
> > rc = unixLogError(SQLITE_IOERR_SHMMAP, "mmap", pShmNode->zFilename);
> > goto shmpage_out;
> > }
> > 
> > Then it did compile and seemed to work so far. The library does not use mmap, only the shell program sqlite3.exe does and I guess that will work so far without mmap in DOS.
> > 
> > Georg
> 
> 
> Where do I place those lines of code?

Why wasn't mmap implemented in the first place?

- Raw text -