Re: Build issues

[Simon Josefsson]

Hi

Can you send me the output (stdout+stderr) from running ./configure,
and the files libpskc/config.log libpskc/config.status?  

/Simon

ons 2023-08-02 klockan 14:05 +0000 skrev Joseph Cossette:
> Sorry for late reply…I’ve other assigned duties that needed tending
> to.
>  
> Looks like pkg-config is already installed.  When I did this, it
> produced the following output:
>  
> # sudo apt install pkg-config
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> pkg-config is already the newest version (0.29.2-1ubuntu3).
> pkg-config set to manually installed.
> 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
>  
>  
> Hope this helps.
>  
> Thanks in advance.
>  
>  
> From:Simon Josefsson <simon@josefsson.org>
> Date: Wednesday, July 26, 2023 at 5:40 AM
> To: Joseph Cossette <joseph.cossette@jci.com>
> Cc: oath-toolkit-help@nongnu.org <oath-toolkit-help@nongnu.org>
> Subject: Re: Build issues
> Do you have pkg-config? Your config.log says:
>  
> configure:4490: checking for pkg-config
> configure:4528: result: no
> configure:4563: checking for XML2
> configure:4622: result: no
>  
> Which suggests something is wrong with pkg-config.
>  
> /Simon
> 
> 
> > 24 juli 2023 kl. 23:07 skrev Joseph Cossette
> > <joseph.cossette@jci.com>:
> >  
> > Correction:
> >  
> >    1. I get oathtool and libpath (and ubuntu builds pam) just fine.
> >  
> > I get oathtool and liboath (and ubuntu builds pam) just fine.
> >  
> > From:oath-toolkit-help-bounces+jcossej=jci.com@nongnu.org
> > <oath-toolkit-help-bounces+jcossej=jci.com@nongnu.org> on behalf of
> > Joseph Cossette <joseph.cossette@jci.com>
> > Date: Monday, July 24, 2023 at 4:52 PM
> > To: Simon Josefsson <simon@josefsson.org>
> > Cc: oath-toolkit-help@nongnu.org <oath-toolkit-help@nongnu.org>
> > Subject: Re: Build issues
> >  
> > Other than the latex/doc tools, I already had everything installed
> > mentioned in your link below, including libxmlsec.
> >  
> > Again, there is no “build error”.  It builds oathtool and liboath
> > in Yocto ARM and Ubuntu 22.04 (Ubuntu also build the pam too) just
> > fine.
> >  
> > What I don’t get is the pskc artifacts.  If I do a build from using
> > the configure command line:
> >  
> > ./configure --prefix=$PWD/../built --enable-pskc
> >  
> > I get oathtool and libpath (and ubuntu builds pam) just fine.  But
> > it doesn’t build any pskc artifacts…I believe it’s because the
> > configure script doesn’t find libxml2…so it never attempts to run
> > configure in libpskc and pskctool.
> >  
> > So there is no “build error” to see…the error is that it’s not
> > building the requested pskc artifacts…how to build these when it
> > can’t locate libxml2 ?
> >  
> > I believe our Yocto ARM build was taken directly from the
> > OpenEmbedded repository, and is an older version (oath 2.6.2), but
> > it is broken in regards to pskc artifacts also. We tried replacing
> > it with the newsest version, but it too has the same problem.
> >  
> > Hope this helps.
> >  
> >  
> > From:Simon Josefsson <simon@josefsson.org>
> > Date: Monday, July 24, 2023 at 11:54 AM
> > To: Joseph Cossette <joseph.cossette@jci.com>
> > Cc: oath-toolkit-help@nongnu.org <oath-toolkit-help@nongnu.org>
> > Subject: Re: Build issues
> > Hi
> >  
> > Can you qoute the build error you get from “make”? You need
> > libxmlsec, did you use the commands suggested here:
> >  
> > <twitter_card-
> > 570ddb06edf56a2312253c5872489847a0f385112ddbcd71ccfa1570febab5d2.jp
> > g> CONTRIBUTING.md · master · oath-toolkit / oath-toolkit · GitLab
> > gitlab.com
> >  
> > In particular: 
> > apt-get install make git autoconf automake libtool bison gengetopt
> > valgrind apt-get install libpam0g-dev libxmlsec1-dev libxml2-utils
> > apt-get install help2man gtk-doc-tools libglib2.0-dev dblatex
> >  
> > /Simon
> > 
> > 
> > 
> > 
> > > 24 juli 2023 kl. 17:46 skrev Joseph Cossette
> > > <joseph.cossette@jci.com>:
> > >  
> > > Sure.
> > >  
> > > I created a VM from standard desktop Ubuntu 22.04.2 LTS .iso
> > > file.  Added build essentials and some other tools for
> > > development, as well as any other noted dependencies for oath
> > > toolkit (Linux pam headers, libxml2, etc.,…).
> > >  
> > > Used the following command line to configure:
> > >  
> > > /configure --prefix=$PWD/../built --enable-pskc
> > >  
> > > Configure ends with the following lines, which show that pskc
> > > would not be built:
> > >  
> > >   version:          2.6.9
> > >   Install prefix:   /mnt/hgfs/snc2/third_party/oath/oath-toolkit-
> > > 2.6.9/../built
> > >   Compiler:         gcc
> > >   Build PAM module: yes
> > >   PSKC:             no
> > >  
> > > I’ve attached the config.log & config.status file for your
> > > perusal.  In searching for XML2 in the config log file it appears
> > > to indicate that it didn’t find it, even though it is installed
> > > on the system.  It then of course doesn’t even attempt to build
> > > any pskc artifacts, as where if it at least configured for pskc
> > > artifacts the resolution could then be deferred to
> > > compilation/linking steps, which is typically easier to handle
> > > for embedded systems.
> > >  
> > > As I previously mentioned, oathtool and it’s dependent library
> > > liboath appear to be building correctly for both Ubuntu and Yocto
> > > ARM.  But whenever we try to build the pskc artifacts by enabling
> > > them to configure, we basically get the same thing on both
> > > systems…namely, configure appears to not find the libxml2
> > > artifacts. No pskc artifacts, only oath artifacts get produced. 
> > > Our Yocto build is also not building the pam module.  Since we’re
> > > also building the kernel in the Yocto sandbox it successfully
> > > builds all other pams though.
> > >  
> > > I’m sure if we put more man hours into it we could come up with a
> > > custom CMake build for this package within our Yocto sandbox, but
> > > we would much prefer to use your standard build so as to be able
> > > to get any timely security fixes and testcases.  But since it
> > > appeared that there may be a build problem with the package even
> > > using a popular standard desktop Linux,  I thought we’d wait
> > > before we spin any more resources and see if you folks had any
> > > ideas before we proceeded further.
> > >  
> > > Any help in getting this built using your standard build package
> > > would be greatly appreciated.
> > >  
> > > Thanks in advance.
> > >  
> > >  
> > >  
> > >  
> > > On 7/21/23, 7:35 PM, "Simon Josefsson" <simon@josefsson.org>
> > > wrote:
> > > Hi Joseph,
> > >  
> > > Thanks for your interest.  Can you be specific about what your
> > > build
> > > problems are?  Explaining how you tried to build the package, and
> > > what
> > > error message you got will help.
> > >  
> > > OATH Toolkit is built continously in GitLab CI/CD:
> > >  
> > > https://gitlab.com/oath-toolkit/oath-toolkit/-/pipelines
> > >  
> > > The latest release 2.6.9 builds in many environments:
> > >  
> > > https://gitlab.com/oath-toolkit/oath-toolkit/-/pipelines/925626986
> > >  
> > > I maintain the Debian packages for it, which are also updated and
> > > appears to build on all architectures:
> > >  
> > > https://tracker.debian.org/pkg/oath-toolkit
> > >  
> > > Including cross-builds:
> > >  
> > > http://crossqa.debian.net/src/oath-toolkit
> > >  
> > > /Simon
> > >  
> > > Joseph Cossette <joseph.cossette@jci.com> writes:
> > >  
> > > > We’d like to use the oath toolkit for 2FA on our new embedded
> > > > device,
> > > > but we’re having issues trying to get it all built under Yocto
> > > > (or
> > > > Ubuntu 22.04 desktop for that matter).
> > > >  
> > > > We’re able to get oathtool and liboath built (and on Ubuntu
> > > > also the pam).
> > > >  
> > > > But pskctool and libpskc refuse to be configured.  After
> > > > examination
> > > > it appears that XML2 may be the cause of the problem (even
> > > > under
> > > > Ubuntu).  XML2 is installed in Yocto (and Ubuntu), but the
> > > > configure
> > > > check for the package always fails, so it’s not being included
> > > > in the
> > > > makefiles (on both platforms).
> > > >  
> > > > I did a bit of searching and saw that a 2-year old merge ticket
> > > > on
> > > > XML2 was put in by folks here…it mentions 2.70+…we’re using
> > > > 2.9.x
> > > > versions…but configure still doesn’t find them.
> > > >  
> > > > It appears (for all practical purposes), the oath toolkit
> > > > configure
> > > > procedure is broken…likely on many systems too if it can’t even
> > > > be
> > > > built out of the box on Ubuntu 22.04.
> > > >  
> > > > Not sure where to go from here on this.  We’ve already put in
> > > > quite a
> > > > few man hours into trying to get this built and have stopped
> > > > trying at
> > > > this point…it’s burning up too much resources…;(…
> > > >  
> > > > If anyone has any information on how to resolve this issue
> > > > please reply.
> > >  
> > > <config.log>
> > > <config.status>

signature.asc
Description: This is a digitally signed message part