From: Aidan Van Dyk <aidan@highrise.ca>
To: Boyd Lynn Gerber <gerberb@zenez.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Compile fix for SCO OPenServer
Date: Wed, 30 Jul 2008 16:43:39 -0400 [thread overview]
Message-ID: <20080730204339.GJ10399@yugib.highrise.ca> (raw)
In-Reply-To: <alpine.LNX.1.10.0807301403360.13032@xenau.zenez.com>
[-- Attachment #1: Type: text/plain, Size: 2621 bytes --]
* Boyd Lynn Gerber <gerberb@zenez.com> [080730 16:09]:
> I have just tried this on 4 OpenServer 6.0 machines fresh installed and I
> do not need this added. I am trying to figure out what is different on
> his. It appears he is using the exact same version of the compiler as
> well.
>
> My uname -a gives me this...
>
> SCO_SV tech0 5 6.0.0 i386
>
> and the gcc -V gives me the exact same compiler. So I do not know why he
> has to have the additional __OPENSERVER__. This does break my OpenServer
> 5.0.7 fresh install as well. So I would not use it. What I do not
> understand is why the !defined(__USLC__) does not catch it. It should.
Sorry, a bit premature on my end...
I tried a "default" gmake, and hit an error right away:
UX:cc: ERROR: Invalid subargument: -Wall
And immediately pulled my changes from last january into the fix it. My
changes included a local config.mak CFLAGS override which was the real
fix.
To build with no source changes, I need:
NO_MKDTEMP=1 SNPRINTF_RETURNS_BOGUS=1 CFLAGS=-g NO_POSIX_ONLY_PROGRAMS=1
How about something like this:
diff --git a/Makefile b/Makefile
index 798a2f2..c42040f 100644
--- a/Makefile
+++ b/Makefile
@@ -602,6 +602,7 @@ ifeq ($(uname_S),SCO_SV)
endif
ifeq ($(uname_R),5)
CC = cc
+ CFLAGS = -g
BASIC_CFLAGS += -Kthread
endif
NEEDS_SOCKET = YesPlease
@@ -615,6 +616,8 @@ ifeq ($(uname_S),SCO_SV)
BASIC_LDFLAGS += -L/usr/local/lib
NO_STRCASESTR = YesPlease
NO_MEMMEM = YesPlease
+ NO_MKDTEMP = YesPlease
+ SNPRINTF_RETURNS_BOGUS = YesPlease
INSTALL = ginstall
TAR = gtar
endif
Unfortunately, I have access to only that one SCO box, so I have no idea
of mkdtemp and sprintf problems are on all SCO, or just R=5 ones.
That allows me to build with NO_POSIX_ONLY_PROGRAMS=1, because for some reason, the
linker complains on linking git-shell:
Undefined first referenced
symbol in file
hexval_table abspath.o
null_sha1 abspath.o
trust_executable_bit abspath.o
has_symlinks abspath.o
UX:ld: ERROR: Symbol referencing errors. No output written to git-shell
These are all extern varualbes declared in cache.h, but no defined in
any of the objects git-shell links, normally not a problem, but this is SCO.
--
Aidan Van Dyk Create like a god,
aidan@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-07-30 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 17:21 [PATCH] Compile fix for SCO OpenServer Aidan Van Dyk
2008-07-30 18:49 ` Compile fix for SCO OPenServer Aidan Van Dyk
2008-07-30 20:01 ` Junio C Hamano
2008-07-30 20:09 ` Boyd Lynn Gerber
2008-07-30 20:18 ` Junio C Hamano
2008-07-30 20:43 ` Aidan Van Dyk [this message]
2008-07-30 21:28 ` Boyd Lynn Gerber
2008-07-30 22:56 ` Aidan Van Dyk
2008-07-30 23:30 ` Boyd Lynn Gerber
2008-07-30 23:44 ` Aidan Van Dyk
2008-07-31 0:00 ` Boyd Lynn Gerber
2008-07-31 0:11 ` Aidan Van Dyk
2008-07-31 0:32 ` Boyd Lynn Gerber
2008-07-30 20:13 ` Boyd Lynn Gerber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080730204339.GJ10399@yugib.highrise.ca \
--to=aidan@highrise.ca \
--cc=gerberb@zenez.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.