# 1.3.2.gde1d fails to build on OpenBSD 4 messages from 2006-05-15 to 2006-05-15. Participants: Randal L. Schwartz, Timo Hirvonen, Linus Torvalds. Thread: https://gitlist.dev/t/4147 ## Randal L. Schwartz, 2006-05-15 14:24 Subject: 1.3.2.gde1d fails to build on OpenBSD Message-ID: <86psiftlgf.fsf@blue.stonehenge.com> URL: https://gitlist.dev/e/86psiftlgf.fsf%40blue.stonehenge.com ``` GIT_VERSION = 1.3.2.gde1d gcc -o sha1_file.o -c -g -O2 -Wall -I/usr/local/include -DSHA1_HEADER='' -DNO_STRCASESTR sha1_file.c sha1_file.c:16:20: stdint.h: No such file or directory gmake: *** [sha1_file.o] Error 1 I think you want #include on OpenBSD. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! ``` ## Randal L. Schwartz, 2006-05-15 15:57 Subject: Re: 1.3.2.gde1d fails to build on OpenBSD Message-ID: <86bqtzth57.fsf@blue.stonehenge.com> URL: https://gitlist.dev/e/86bqtzth57.fsf%40blue.stonehenge.com In-Reply-To: <20060515185819.ff05f6fe.tihirvon@gmail.com> ``` >>>>> "Timo" == Timo Hirvonen writes: >> I think you want >> >> #include >> >> on OpenBSD. Timo> I think it should be #include . It works at least on BSD Timo> and Linux. Yes, that's present in OpenBSD. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! ``` ## Timo Hirvonen, 2006-05-15 15:58 Subject: Re: 1.3.2.gde1d fails to build on OpenBSD Message-ID: <20060515185819.ff05f6fe.tihirvon@gmail.com> URL: https://gitlist.dev/e/20060515185819.ff05f6fe.tihirvon%40gmail.com In-Reply-To: <86psiftlgf.fsf@blue.stonehenge.com> ``` merlyn@stonehenge.com (Randal L. Schwartz) wrote: > > GIT_VERSION = 1.3.2.gde1d > gcc -o sha1_file.o -c -g -O2 -Wall -I/usr/local/include -DSHA1_HEADER='' -DNO_STRCASESTR sha1_file.c > sha1_file.c:16:20: stdint.h: No such file or directory > gmake: *** [sha1_file.o] Error 1 > > I think you want > > #include > > on OpenBSD. I think it should be #include . It works at least on BSD and Linux. -- http://onion.dynserv.net/~timo/ ``` ## Linus Torvalds, 2006-05-15 16:00 Subject: Re: 1.3.2.gde1d fails to build on OpenBSD Message-ID: URL: https://gitlist.dev/e/Pine.LNX.4.64.0605150854420.3866%40g5.osdl.org In-Reply-To: <86psiftlgf.fsf@blue.stonehenge.com> ``` On Mon, 15 May 2006, Randal L. Schwartz wrote: > > GIT_VERSION = 1.3.2.gde1d > gcc -o sha1_file.o -c -g -O2 -Wall -I/usr/local/include -DSHA1_HEADER='' -DNO_STRCASESTR sha1_file.c > sha1_file.c:16:20: stdint.h: No such file or directory > gmake: *** [sha1_file.o] Error 1 > > I think you want > > #include > > on OpenBSD. Gaah. This was one reason why I absolutely _detested_ those "intXX_t" types historically. I thought the world had gotten over it, and they were all so common and standard that we'd never need to worry about it. Randal: we already _do_ include , as part of the standard set of headers in git-compat-util.h. So the problem is that that wasn't enough on OS X, which wanted . Junio: I'd suggest just using "unsigned int", or just defining your own types in "cache.h". I would suggest typedef unsigned char u8; typedef unsigned short u16; typedef unsigned int u32; typedef signed char s8; typedef short s16; typedef int s32; which is the only sane way to avoid idiotic crap like autoconf, and which avoids that whole "standard namespace" issue. Yeah, some people will complain. Ten years later, they _still_ complain about me doing this right in the kernel. But you can sleep well, knowing that the complainers are standards-weenies that have read books, but never seen the real world. Linus ```