Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > alt.lang.basic.compiler > #3
| From | Paul <nospam@needed.invalid> |
|---|---|
| Newsgroups | alt.comp.os.windows-10, alt.comp.freeware, alt.lang.basic.compiler |
| Subject | Re: If I wanted to build the openssl binary from source code, which free compiler is used nowadays for such things? |
| Date | 2020-04-26 16:59 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <r84snd$vu2$1@dont-email.me> (permalink) |
| References | <r84reg$l5u$1@news.mixmin.net> |
Cross-posted to 3 groups.
Arlen Holder wrote:
> If I wanted to build the openssl binary from source code...
> o <https://www.openssl.org/source/> which is currently 1.1.1g: o
> <https://www.openssl.org/source/openssl-1.1.1g.tar.gz>
> Which free compiler is used nowadays for such things?
>
> It was clearly suggested in this thread just now to compile it myself:
> o Which openssl Windows binary do you recommend (to have the latest
> official version)?
> <https://groups.google.com/forum/#!topic/alt.comp.freeware/mZgki-TvHlo>
>
> Bear in mind I haven't compiled from src in a decade.
> o But also bear in mind I like to write general purpose tutorials.
>
> So maybe it would be useful to write up a general purpose tutorial to walk
> a noob through the steps of compiling that specific src code on Windows.
>
> For starters, the general purpose tutorial would assume the basics:
> a. Native Windows 10
> b. Canonical freeware
>
> Rest assured I've _tried_ to compile in the past decades a few times,
> where, oh, about 50% or 75% of the time it fails miserably.
>
> Often with errors so cryptic that you just want to cry reading them.
> Usually because some dependency was assumed that simply doesn't exist.
>
> Anyway, I'm willing to try compiling openssl from source, where the first
> question to ask those who actually do compile every once in a while, is
> what freeware compiler is the canonical choice nowadays for Windows 10?
The first question you ask, is what did the designers intend ?
On Windows, there are two kinds of executables. If you use
Visual Studio, the EXE can be debugged with WinDBG. If you
use a gcc-based build environment, the executable can only
be debugged with "gdb" in the same kit. Both are loadable
by Windows, so the loading works OK.
Visual Studio builds, they profit from having certain
config files in the build directory. Some yahoos provide
VS tarballs but remove the important files that automate
the build (and then you know the author of the software
is jerking your chain, and there's NO WAY it will build).
Whereas one form of gcc material, may have a "./configure"
executable, that sniffs all the bits and prepares Makefiles.
(A Makefile being similar to the function that at least
some of the Visual Studio stuff provides.)
This means, a buildmeister might keep a fleet of compilers
and junk. For example, some builds will have "CMAKE" and
there's an invocation step involving CMAKE before anything
else. Those builds involve a single tree concept (when a company
like Adobe puts some of the build materials outside the tree,
you'll wanna smack somebody).
So rather than assuming "you're going shopping for N95 masks",
it's not really a shopping trip. The first part of the
exercise is "contemplation of what problem I'm solving".
How screwed up are the provided materials ? The answer
to that will tell you where to look for a compiler.
Of course you could read the INSTALL file in the build
tree (a common feature in FOSS), as well-written text descriptions
may tell you exactly what to do. For example, maybe I'd
find such a thing in Firefox, and the first thing it
would tell me is to discard that tarball, and use hg
or git or something, and pull down the software package
which is 50% larger. They put the weirdest information
in these files sometimes.
You have to be a detective, as much as a CS grad.
The stuff in the INSTALL file, is frequently a portion of
the text on the web page too.
Paul
Back to alt.lang.basic.compiler | Previous | Next — Previous in thread | Next in thread | Find similar
If I wanted to build the openssl binary from source code, which free compiler is used nowadays for such things? Arlen Holder <arlenholder@anyexample.com> - 2020-04-27 04:37 +0800
Re: If I wanted to build the openssl binary from source code, which free compiler is used nowadays for such things? Paul <nospam@needed.invalid> - 2020-04-26 16:59 -0400
Re: If I wanted to build the openssl binary from source code, which free compiler is used nowadays for such things? Arlen Holder <arlenholder@anyexample.com> - 2020-04-27 07:27 +0100
Re: If I wanted to build the openssl binary from source code, which free compiler is used nowadays for such things? "Gary R. Schmidt" <grschmidt@acm.org> - 2020-04-27 13:03 +1000
Re: If I wanted to build the openssl binary from source code, which free compiler is used nowadays for such things? Arlen Holder <arlenholder@anyexample.com> - 2020-04-27 06:44 +0100
Re: If I wanted to build the openssl binary from source code, which free compiler is used nowadays for such things? Paul <nospam@needed.invalid> - 2020-04-27 03:16 -0400
Re: If I wanted to build the openssl binary from source code, which free compiler is used nowadays for such things? "Mayayana" <mayayana@invalid.nospam> - 2020-04-27 07:57 -0400
Re: If I wanted to build the openssl binary from source code, which free compiler is used nowadays for such things? Arlen Holder <arlenholder@anyexample.com> - 2020-04-27 17:10 +0100
csiph-web