From: Boyd Lynn Gerber <gerberb@zenez.com>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Compile fix for SCO OPenServer
Date: Wed, 30 Jul 2008 18:00:23 -0600 [thread overview]
Message-ID: <alpine.LNX.1.10.0807301747160.13032@xenau.zenez.com> (raw)
In-Reply-To: <20080730234455.GN10399@yugib.highrise.ca>
On Wed, 30 Jul 2008, Aidan Van Dyk wrote:
> * Boyd Lynn Gerber <gerberb@zenez.com> [080730 19:30]:
> > I have m4-1.4.3 at
> >
> > ftp://ftp.zenez.com/pub/zenez/prgms/m4-1.4.3-osr6-all.tar.gz
> >
> > I really have to be able to use configure for most of my OpenSource
> > Projects for SCO OS's.
> >
> > I made the changes so that most things work with the auto tools.
>
> I'm not a SCO guru by any means...
>
> I'm just a user on someone else's SCO machine, just trying to make sure
> that the software I write is "fairly portable"...
>
> I'm willing to carry a good and useful tool (like git) in my home
> directory in that endeavour, but I'm not carrying all of the GNU stack
> in my home directory so I can run configure git is a bit much ;-)
That make sense. All though m4 is
test5 > l /usr/local/bin/m4
-rwxr-xr-x 1 gerberb zenez 280524 Jul 23 2005 /usr/local/bin/m4
Which is not that big. I have it in my ~/.bin/ on my clients machines.
You really need a good m4 for most things. Sendmail expecially. Also for
the latest bind with the DNS security fix. I some times need bc as well.
test5 > l /usr/local/bin/bc
-rwxr-xr-x 1 bin bin 85088 May 19 17:20 /usr/local/bin/bc
> > I did a VM install of OpenServer 6 to try things out. I was able to get
> > your -Wall failure, but once I ran the CC=cc CXX=CC ./configure I was able
> > to run gmake without any errors. I did have to install the M4 from above
> > to get configure to work. So, the straight out of the box install has to
> > have gnu m4 to run configure.
>
> So configure.ac must have some magic in it that allows configure to
> notice -Wall doesn't work. You can see what it choose in
> config.mak.autogen I think. But I'm pretty glad for the kbuild style
> Makefile in git not requiring autoconf/automake/etc.
I do not see anything really obvious, but below is config.mak.autogen
test5 > cat config.mak.autogen
# git Makefile configuration, included in main Makefile
# config.mak.autogen. Generated from config.mak.in:config.mak.append by
configure.
CC = cc
CFLAGS = -Kalloca -Kthread
AR = gar
TAR = gtar
#INSTALL = @INSTALL@ # needs install-sh or install.sh in
sources
TCLTK_PATH = wish
prefix = /usr/local
exec_prefix = ${prefix}
bindir = ${exec_prefix}/bin
#gitexecdir = ${exec_prefix}/libexec/git-core/
datarootdir = @datarootdir@
template_dir = ${prefix}/share/git-core/templates/
mandir=${prefix}/man
srcdir = .
export exec_prefix mandir
export srcdir VPATH
ASCIIDOC8=
NEEDS_SSL_WITH_CRYPTO=
NO_OPENSSL=
NO_CURL=
NO_EXPAT=
NEEDS_LIBICONV=
NEEDS_SOCKET=YesPlease
NO_SYS_SELECT_H=
NO_D_INO_IN_DIRENT=
NO_D_TYPE_IN_DIRENT=YesPlease
NO_SOCKADDR_STORAGE=
NO_IPV6=
NO_C99_FORMAT=
NO_STRCASESTR=YesPlease
NO_MEMMEM=YesPlease
NO_STRLCPY=
NO_STRTOUMAX=
NO_SETENV=
NO_UNSETENV=
NO_MKDTEMP=YesPlease
NO_ICONV=
OLD_ICONV=
NO_DEFLATE_BOUND=
FREAD_READS_DIRECTORIES=UnfortunatelyYes
SNPRINTF_RETURNS_BOGUS=UnfortunatelyYes
# config.mak.append. Generated by configure.
> > -g and -O2 are mutually exclusive. You can have either one but not both.
>
> Yes, and I think the default to cc matches -g, not -O2, hence my
> failures unless setting -O2.
>
> > I do have tcl and tk
>
> I'm sure... I might even find it burried somewhere on this machine too,
> but I have no real need for it.
OK.
So what do you think we need to have. I really do not see the need for
__OPENSERVER__. Do you?
--
Boyd Gerber <gerberb@zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
next prev parent reply other threads:[~2008-07-31 0:01 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
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 [this message]
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=alpine.LNX.1.10.0807301747160.13032@xenau.zenez.com \
--to=gerberb@zenez.com \
--cc=aidan@highrise.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).