All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [tpm2] git clone vs tar file of tpm2-tss & bitbake
@ 2018-02-19 21:24 Scheie, Peter M
  0 siblings, 0 replies; 4+ messages in thread
From: Scheie, Peter M @ 2018-02-19 21:24 UTC (permalink / raw)
  To: tpm2

[-- Attachment #1: Type: text/plain, Size: 4076 bytes --]

Problem fixed.  I had to set PNWHITELIST_openembedded-layer_append = “autoconf-archive” and then get autoconf-archive-2012.04.07.tar.gz, not the latest autoconf-archive tar file.  This way I was able to use the recipe built into WindRiver Linux.  And then everything built as expected.  Thanks for the help everyone.

Peter

From: emmanueldeloget53(a)gmail.com [mailto:emmanueldeloget53(a)gmail.com] On Behalf Of Emmanuel Deloget
Sent: Saturday, February 17, 2018 3:12 AM
To: Scheie, Peter M
Cc: tpm2(a)lists.01.org
Subject: Re: [tpm2] git clone vs tar file of tpm2-tss & bitbake

Hello,


On Fri, Feb 16, 2018 at 8:25 PM, Scheie, Peter M <Petre.Scheie(a)gd-ms.com<mailto:Petre.Scheie(a)gd-ms.com>> wrote:
I’m trying to incorporate tpm2-tss into my bitbake (Wind River Linux 8/yocto) build.  We’re on an air-gapped network, so I started by downloading the tpm2-tss-1.3.0.tar.gz file from the releases, moved that to the isolated network, and then used the tpm2-tss_1.2.0.bb<http://tpm2-tss_1.2.0.bb> and tpm2-tss.inc recipes, with the ARC_URI in the former being modified thusly:

                #SRC_URI = "git://github.com/01org/${BPN}.git;protocol=git;tag=${PV};name=${BPN};destsuffix=${BPN};branch=1.x<http://github.com/01org/$%7BBPN%7D.git;protocol=git;tag=$%7BPV%7D;name=$%7BBPN%7D;destsuffix=$%7BBPN%7D;branch=1.x>"
       SRC_URI = “file://tpm2-tss<file:///\\tpm2-tss>”

And I commented out the whole do_config_prepend section in tpm2-tss.inc since it shouldn’t be necessary (right?  Besides, the tar file doesn’t have the bootstrap script).

But when I ran configure, I got errors (or perhaps they’re warnings?) about tpm2-tss-1.3.0/ not being a git directory, which is true, it isn’t—it isn’t supposed to be, right?  So, next, I git cloned tpm2-tss via an outside machine that did have internet access, tar’d up that directory, moved it to the isolated network, and plopped it into my bitbake build environment.  Now when I run configure, I don’t get the git errors, although autoconf is still failing because of “possibly undefined macros” which happens even with the git version and which I’ve mentioned elsewhere*.  But to try to solve the autoconf issues, I’m trying to make my setup as orthodox as possible.  I can take the release tar file and successfully build that outside my bitbake build environment, so I think I should be able to use it inside the bitbake build.  Suggestions?


BTW, should the recipe file be tpm2-tss-1.3.0.bb<http://tpm2-tss-1.3.0.bb> rather than tpm2-tss-1.2.0.bb<http://tpm2-tss-1.2.0.bb>?


*The real problem in building tpm2-tss inside bitbake is that it fails saying macros such as AC_SUBST “may be undefined”.  This suggests that autoconf-archive is missing, but it isn’t.  We’ve added autconf-archive to our build, tagged it as native so it’s pulled into the build environment, listed it as a dependency for tpm2-tss, and can see it being built when we try to  build tpm2-ss, but tpm2-tss still fails with the same AC_SUBST-may-be-undefined error.  So, it seems something else is wrong somewhere.  Thus my effort to try to align my build for tpm2-tss to be as “normal” as possible.


​I did this job for integration in lede/openwrt, so I guess the work is similar.

The missing aclocal macros are from the ​autoconf-archive package (https://www.gnu.org/software/autoconf-archive/). You can download individual macros here: https://www.gnu.org/software/autoconf-archive/The-Macros.html. I don't remember which one are used (you can find out by yourself by reading the configure.ac<http://configure.ac> files). Copy the missing m4 files in the m4 directory before calling autoreconf and this should be ok.

The version issue is less important - all you're missing is the version information which is not that important. If it's really needed, you can patch the configure.ac<http://configure.ac> file to either read the version from a file or directly put the correct version number within the file.

Best regards,

-- Emmanuel Deloget

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 10563 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [tpm2] git clone vs tar file of tpm2-tss & bitbake
@ 2018-02-17  9:11 Emmanuel Deloget
  0 siblings, 0 replies; 4+ messages in thread
From: Emmanuel Deloget @ 2018-02-17  9:11 UTC (permalink / raw)
  To: tpm2

[-- Attachment #1: Type: text/plain, Size: 3478 bytes --]

Hello,


On Fri, Feb 16, 2018 at 8:25 PM, Scheie, Peter M <Petre.Scheie(a)gd-ms.com>
wrote:

> I’m trying to incorporate tpm2-tss into my bitbake (Wind River Linux
> 8/yocto) build.  We’re on an air-gapped network, so I started by
> downloading the tpm2-tss-1.3.0.tar.gz file from the releases, moved that to
> the isolated network, and then used the tpm2-tss_1.2.0.bb and
> tpm2-tss.inc recipes, with the ARC_URI in the former being modified
> thusly:
>
>
>
>                 #SRC_URI = "git://github.com/01org/${BPN}
> .git;protocol=git;tag=${PV};name=${BPN};destsuffix=${BPN};branch=1.x
> <http://github.com/01org/$%7BBPN%7D.git;protocol=git;tag=$%7BPV%7D;name=$%7BBPN%7D;destsuffix=$%7BBPN%7D;branch=1.x>
> "
>
>        SRC_URI = “file://tpm2-tss”
>
>
>
> And I commented out the whole do_config_prepend section in tpm2-tss.inc
> since it shouldn’t be necessary (right?  Besides, the tar file doesn’t have
> the bootstrap script).
>
>
>
> But when I ran configure, I got errors (or perhaps they’re warnings?)
> about tpm2-tss-1.3.0/ not being a git directory, which is true, it isn’t—it
> isn’t supposed to be, right?  So, next, I git cloned tpm2-tss via an
> outside machine that did have internet access, tar’d up that directory,
> moved it to the isolated network, and plopped it into my bitbake build
> environment.  Now when I run configure, I don’t get the git errors,
> although autoconf is still failing because of “possibly undefined macros”
> which happens even with the git version and which I’ve mentioned
> elsewhere*.  But to try to solve the autoconf issues, I’m trying to make my
> setup as orthodox as possible.  I can take the release tar file and
> successfully build that outside my bitbake build environment, so I think I
> should be able to use it inside the bitbake build.  Suggestions?
>
>
>
>
>
> BTW, should the recipe file be tpm2-tss-1.3.0.bb rather than
> tpm2-tss-1.2.0.bb?
>
>
>
>
>
> *The real problem in building tpm2-tss inside bitbake is that it fails
> saying macros such as AC_SUBST “may be undefined”.  This suggests that
> autoconf-archive is missing, but it isn’t.  We’ve added autconf-archive to
> our build, tagged it as native so it’s pulled into the build environment,
> listed it as a dependency for tpm2-tss, and can see it being built when we
> try to  build tpm2-ss, but tpm2-tss still fails with the same
> AC_SUBST-may-be-undefined error.  So, it seems something else is wrong
> somewhere.  Thus my effort to try to align my build for tpm2-tss to be as
> “normal” as possible.
>


​I did this job for integration in lede/openwrt, so I guess the work is
similar.

The missing aclocal macros are from the ​autoconf-archive package (
https://www.gnu.org/software/autoconf-archive/). You can download
individual macros here:
https://www.gnu.org/software/autoconf-archive/The-Macros.html. I don't
remember which one are used (you can find out by yourself by reading the
configure.ac files). Copy the missing m4 files in the m4 directory before
calling autoreconf and this should be ok.

The version issue is less important - all you're missing is the version
information which is not that important. If it's really needed, you can
patch the configure.ac file to either read the version from a file or
directly put the correct version number within the file.

Best regards,

-- Emmanuel Deloget

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5757 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [tpm2] git clone vs tar file of tpm2-tss & bitbake
@ 2018-02-17  3:17 Trevor Woerner
  0 siblings, 0 replies; 4+ messages in thread
From: Trevor Woerner @ 2018-02-17  3:17 UTC (permalink / raw)
  To: tpm2

[-- Attachment #1: Type: text/plain, Size: 326 bytes --]

On Fri, Feb 16, 2018 at 2:25 PM, Scheie, Peter M <Petre.Scheie(a)gd-ms.com>
wrote:

> We’re on an air-gapped network, so I started by downloading the
> tpm2-tss-1.3.0.tar.gz file from the releases
>

Does this help?

https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 880 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [tpm2] git clone vs tar file of tpm2-tss & bitbake
@ 2018-02-16 19:25 Scheie, Peter M
  0 siblings, 0 replies; 4+ messages in thread
From: Scheie, Peter M @ 2018-02-16 19:25 UTC (permalink / raw)
  To: tpm2

[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]

I'm trying to incorporate tpm2-tss into my bitbake (Wind River Linux 8/yocto) build.  We're on an air-gapped network, so I started by downloading the tpm2-tss-1.3.0.tar.gz file from the releases, moved that to the isolated network, and then used the tpm2-tss_1.2.0.bb and tpm2-tss.inc recipes, with the ARC_URI in the former being modified thusly:

                #SRC_URI = "git://github.com/01org/${BPN}.git;protocol=git;tag=${PV};name=${BPN};destsuffix=${BPN};branch=1.x"
       SRC_URI = "file://tpm2-tss<file:///\\tpm2-tss>"

And I commented out the whole do_config_prepend section in tpm2-tss.inc since it shouldn't be necessary (right?  Besides, the tar file doesn't have the bootstrap script).

But when I ran configure, I got errors (or perhaps they're warnings?) about tpm2-tss-1.3.0/ not being a git directory, which is true, it isn't-it isn't supposed to be, right?  So, next, I git cloned tpm2-tss via an outside machine that did have internet access, tar'd up that directory, moved it to the isolated network, and plopped it into my bitbake build environment.  Now when I run configure, I don't get the git errors, although autoconf is still failing because of "possibly undefined macros" which happens even with the git version and which I've mentioned elsewhere*.  But to try to solve the autoconf issues, I'm trying to make my setup as orthodox as possible.  I can take the release tar file and successfully build that outside my bitbake build environment, so I think I should be able to use it inside the bitbake build.  Suggestions?


BTW, should the recipe file be tpm2-tss-1.3.0.bb rather than tpm2-tss-1.2.0.bb?


*The real problem in building tpm2-tss inside bitbake is that it fails saying macros such as AC_SUBST "may be undefined".  This suggests that autoconf-archive is missing, but it isn't.  We've added autconf-archive to our build, tagged it as native so it's pulled into the build environment, listed it as a dependency for tpm2-tss, and can see it being built when we try to  build tpm2-ss, but tpm2-tss still fails with the same AC_SUBST-may-be-undefined error.  So, it seems something else is wrong somewhere.  Thus my effort to try to align my build for tpm2-tss to be as "normal" as possible.

Peter


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4980 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2018-02-19 21:24 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-02-19 21:24 [tpm2] git clone vs tar file of tpm2-tss & bitbake Scheie, Peter M
  -- strict thread matches above, loose matches on Subject: below --
2018-02-17  9:11 Emmanuel Deloget
2018-02-17  3:17 Trevor Woerner
2018-02-16 19:25 Scheie, Peter M

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.