[15977] in Kerberos-V5-bugs
[krbdev.mit.edu #8672] KFW 4.1 credential cache issue
daemon@ATHENA.MIT.EDU (Benjamin Kaduk via RT)
Tue May 1 06:39:01 2018
Mail-followup-to: rt@krbdev.mit.edu
mail-copies-to: never
From: "Benjamin Kaduk via RT" <rt-comment@KRBDEV-PROD-APP-1.mit.edu>
In-Reply-To: <rt-8672@krbdev.mit.edu>
Message-ID: <rt-8672-48464.11.3961194654703@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #8672'":;
Date: Tue, 1 May 2018 06:38:52 -0400 (EDT)
Reply-To: rt-comment@KRBDEV-PROD-APP-1.mit.edu
Content-Type: multipart/mixed; boundary="===============5294236388425707360=="
Errors-To: krb5-bugs-bounces@mit.edu
--===============5294236388425707360==
I don't have that configuration on the machine in front of me, but from
memory, it was Windows 7 Enterprise (I used the subsystem for unix
applications to get awk/sed, but I understand the SUA was removed in a
later release), Visual Studio 2010 Professional, Strawberry Perl, and
Windows SDK 7.1. (The perl 5.12.4 version you cite below seems a
rather old version, though I don't know for sure that that version is
old enough to cause problems.)
-Ben
[hy93@cornell.edu - Mon Apr 30 13:11:42 2018]:
> I first used Strawberry perl, it gave me error when doing nmake -f
> Makefile.in prep-windows . Then I used ActivateState perl, it
> generated error when doing nmake.
>
> What is the build environment that you can successfully build KFW
4.1?
>
> Hong
>
>
> On 4/29/18, 10:13 AM, "Benjamin Kaduk via RT" <rt-
> comment@krbdev.mit.edu> wrote:
>
> [hy93@cornell.edu - Thu Apr 26 09:25:58 2018]:
>
> > Thanks for your reply. I followed the instruction from the
> README in
> > the source of the tarball. Here is my build environment:
> >
> > Windows 2012 R2
> > Microsoft visual studio 12.0
> > Windows SDK 8
> > Perl 5.12.4
>
> I don't have a whole lot of experience with VS 2013 (or access to
> such
> a setup at the moment), but one common source of trouble is
> ensuring
> that all the moving pieces agree on whether 32- or 64-bit code is
> being
> built (and potentially also what processor architecture). This
> includes at least the way that the cmd.exe shell is spawned
and/or
> initialized, and the value of the CPU environment variable. The
> build
> log snippet implies that something is trying to build 64-bit code
> (the
> "obj/AMD64" in the path to libecho), but I note that the README
> instructions start off by building the 32-bit code. (It's okay
to
> just
> build the 64-bit code and not the 32-bit code for local testing;
> the
> 32-bit build is included in the instructions there so that the
32-
> bit
> libraries can be included in the 64-bit MSI installer.)
>
> Separately, sometimes the source of the perl binary can be
> relevant --
> do you have Strawberry Perl, ActiveState Perl, or something else?
>
>
--===============5294236388425707360==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
--===============5294236388425707360==--
