[build2] libpq build failure

Klaim - Joël Lamotte mjklaim at gmail.com
Tue Oct 1 13:29:32 UTC 2019


On Tue, 1 Oct 2019 at 15:23, <d.patrushev at prosoftsystems.ru> wrote:

> Well, I just followed the build instructions “Installing ODB with build2”,
> using the configuration I just posted (MSVC).
>
>
>
> First, this:
>
> bpkg create -d msvc-release cc^
>
>   config.cxx=cl^
>
>   "config.cc.coptions=/O2 /MD"^
>
>   config.install.root=C:\odb\release
>
>
>
> Then, this:
>
> > cd msvc-XXX
>
> > bpkg add https://pkg.cppget.org/1/beta
>
> > bpkg fetch
>
> > bpkg build libodb
>
> > bpkg build libodb-sqlite
>
> > bpkg build libodb-pgsql
>
> > bpkg build libodb-mysql
>
> > bpkg build libodb-mssql
>
> > bpkg install --all --recursive
>
>
>
> I was building libodb-pgsql, libpq specifically, when I got this error.
>
>
>

I'm upgrading my build2 version to last stage, after that I'll try to
reproduce it to confirm.


>
>
> *From:* users <users-bounces at build2.org> *On Behalf Of *Klaim - Joel
> Lamotte
> *Sent:* Tuesday, October 1, 2019 6:15 PM
> *To:* users at build2.org
> *Subject:* Re: [build2] libpq build failure
>
>
>
> (re-posting this as I didn't include the group by mistake)
>
>
>
> On Tue, 1 Oct 2019 at 13:50, Патрушев Данил Андреевич <
> d.patrushev at prosoftsystems.ru> wrote:
>
> Hi. I am trying to build odb-pgsql but libpq fails to build (Windwows 10,
> msvc x64, I tried both https://pkg.cppget.org/1/beta and
> https://stage.build2.org/1 ) with an error message  “header
> 'ibpq\version.' not found and cannot be generated”.   It seems to be due to
> the fact that for some reason version.h is not autogenerated from
> version.h.in, so there is no version.h to be included. I worked around it
> by cleaning the build files to include just the rule that generates this
> file and it worked – version.h appeared in the directory. After that I
> restored the build files to their original state and finished the build.
>
>
>
> Interesting, I'm seeing a very similar issue with my libsodium package BUT
> that issue is not visible on the public (stage) CI  or if the package is
> built as a dependency.
>
> I've been investigating without much success but so far I assumed I was
> doing something wrong in my build scripts.
>
> Can you write a specific repro-case to see the issue?
>
>
>
> I made a github issue in my repo for my specific case as I am not sure if
> it's specific to my build files or if it's a bug in build2:
>
> https://github.com/Klaim/klaim-proto-libsodium/issues/1
>
>
>
> Joël
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.build2.org/archives/users/attachments/20191001/2cab70d7/attachment.html>


More information about the users mailing list