Is there a way to hold automatic build
32 views
Skip to first unread message
Igor Korot
Sep 3, 2021, 9:28:39 AM9/3/21
to wx-u...@googlegroups.com
Hi, guys,
I' about to resurrect my old changes and wonder
if it's possible to hold the automatic builds until
I'm done testing on all 3 platforms.
Thank you
.
I' about to resurrect my old changes and wonder
if it's possible to hold the automatic builds until
I'm done testing on all 3 platforms.
Thank you
.
Vadim Zeitlin
Sep 3, 2021, 12:47:06 PM9/3/21
to wx-u...@googlegroups.com
On Fri, 3 Sep 2021 08:28:14 -0500 Igor Korot wrote:
IK> if it's possible to hold the automatic builds until
IK> I'm done testing on all 3 platforms.
First of all, the automatic builds are only done for the PRs, you
absolutely don't need to open a PR immediately, but can wait until you've
tested everything locally.
Second, you can "[skip ci]" in the commit message(s) to, well, skip the CI
runs.
However the first solution is still better.
Regards,
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/
IK> if it's possible to hold the automatic builds until
IK> I'm done testing on all 3 platforms.
First of all, the automatic builds are only done for the PRs, you
absolutely don't need to open a PR immediately, but can wait until you've
tested everything locally.
Second, you can "[skip ci]" in the commit message(s) to, well, skip the CI
runs.
However the first solution is still better.
Regards,
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/
Igor Korot
Sep 3, 2021, 1:18:07 PM9/3/21
to wx-u...@googlegroups.com
Vadim,
On Fri, Sep 3, 2021 at 11:47 AM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Fri, 3 Sep 2021 08:28:14 -0500 Igor Korot wrote:
>
> IK> if it's possible to hold the automatic builds until
> IK> I'm done testing on all 3 platforms.
>
> First of all, the automatic builds are only done for the PRs, you
> absolutely don't need to open a PR immediately, but can wait until you've
> tested everything locally.
>
> Second, you can "[skip ci]" in the commit message(s) to, well, skip the CI
> runs.
>
> However the first solution is still better.
I'm trying to resurrect the PR - m"Move To Trash" one to be exact.
So, when I rebase the code and fix it on one platform, I was hoping to
push the changes
pull it on the other platform, make sure its correct and then let the automatic
builds kick in.
Thank you.
On Fri, Sep 3, 2021 at 11:47 AM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Fri, 3 Sep 2021 08:28:14 -0500 Igor Korot wrote:
>
> IK> if it's possible to hold the automatic builds until
> IK> I'm done testing on all 3 platforms.
>
> First of all, the automatic builds are only done for the PRs, you
> absolutely don't need to open a PR immediately, but can wait until you've
> tested everything locally.
>
> Second, you can "[skip ci]" in the commit message(s) to, well, skip the CI
> runs.
>
> However the first solution is still better.
So, when I rebase the code and fix it on one platform, I was hoping to
push the changes
pull it on the other platform, make sure its correct and then let the automatic
builds kick in.
Thank you.
Vadim Zeitlin
Sep 3, 2021, 1:34:56 PM9/3/21
to wx-u...@googlegroups.com
On Fri, 3 Sep 2021 12:17:53 -0500 Igor Korot wrote:
IK> I'm trying to resurrect the PR - m"Move To Trash" one to be exact.
IK> So, when I rebase the code and fix it on one platform, I was hoping to
IK> push the changes
IK> pull it on the other platform, make sure its correct and then let the automatic
IK> builds kick in.
You can do all this in a temporary branch in your repository and then
(force) push it to the branch of this PR.
Or you could just close this one and create a new one if it's simpler for
IK> I'm trying to resurrect the PR - m"Move To Trash" one to be exact.
IK> So, when I rebase the code and fix it on one platform, I was hoping to
IK> push the changes
IK> pull it on the other platform, make sure its correct and then let the automatic
IK> builds kick in.
You can do all this in a temporary branch in your repository and then
(force) push it to the branch of this PR.
Or you could just close this one and create a new one if it's simpler for
Igor Korot
Sep 3, 2021, 2:19:45 PM9/3/21
to wx-u...@googlegroups.com
Vadim,
On Fri, Sep 3, 2021 at 12:34 PM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Fri, 3 Sep 2021 12:17:53 -0500 Igor Korot wrote:
>
> IK> I'm trying to resurrect the PR - m"Move To Trash" one to be exact.
> IK> So, when I rebase the code and fix it on one platform, I was hoping to
> IK> push the changes
> IK> pull it on the other platform, make sure its correct and then let the automatic
> IK> builds kick in.
>
> You can do all this in a temporary branch in your repository and then
> (force) push it to the branch of this PR.
>
> Or you could just close this one and create a new one if it's simpler for
> you.
It probably is.
Are we still using Bakefile? What version?
How do I run it?
Thank you.
On Fri, Sep 3, 2021 at 12:34 PM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Fri, 3 Sep 2021 12:17:53 -0500 Igor Korot wrote:
>
> IK> I'm trying to resurrect the PR - m"Move To Trash" one to be exact.
> IK> So, when I rebase the code and fix it on one platform, I was hoping to
> IK> push the changes
> IK> pull it on the other platform, make sure its correct and then let the automatic
> IK> builds kick in.
>
> You can do all this in a temporary branch in your repository and then
> (force) push it to the branch of this PR.
>
> Or you could just close this one and create a new one if it's simpler for
> you.
Are we still using Bakefile? What version?
How do I run it?
Thank you.
Igor Korot
Sep 3, 2021, 8:53:12 PM9/3/21
to wx-u...@googlegroups.com
Vadim,
On Fri, Sep 3, 2021 at 5:24 PM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Fri, 3 Sep 2021 13:19:32 -0500 Igor Korot wrote:
>
> IK> Are we still using Bakefile? What version?
> IK>
> IK> How do I run it?
>
> The instructions in docs/contributing/how-to-add-files-to-build-system.md
> should still be valid.
[code]
igor@WaylandGnome ~/bakefile $ git status
On branch legacy-0.2-branch
Your branch is up to date with 'origin/legacy-0.2-branch'.
nothing to commit, working tree clean
igor@WaylandGnome ~/bakefile $
igor@WaylandGnome ~/bakefile $ ls -la
total 144
drwxr-xr-x 15 igor igor 4096 Sep 3 19:22 .
drwxr-xr-x 19 igor igor 4096 Sep 3 19:22 ..
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 admin
-rw-r--r-- 1 igor igor 1437 Sep 3 19:22 AUTHORS
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 autoconf
-rw-r--r-- 1 igor igor 10156 Sep 3 19:22 bakefile.iss
-rw-r--r-- 1 igor igor 1076 Sep 3 19:22 bakefile.spec
-rw-r--r-- 1 igor igor 1106 Sep 3 19:22 bakefile.vim
-rw-r--r-- 1 igor igor 2475 Sep 3 19:22 bash_completion
-rwxr-xr-x 1 igor igor 247 Sep 3 19:22 bootstrap
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 build
-rwxr-xr-x 1 igor igor 671 Sep 3 19:22 chversion.sh
-rw-r--r-- 1 igor igor 658 Sep 3 19:22 configure.in
-rw-r--r-- 1 igor igor 1062 Sep 3 19:22 COPYING
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 debian
drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 doc
drwxr-xr-x 7 igor igor 4096 Sep 3 19:22 .git
drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 macosx
-rw-r--r-- 1 igor igor 6024 Sep 3 19:22 Makefile.am
-rw-r--r-- 1 igor igor 841 Sep 3 19:22 makefile.vc
-rw-r--r-- 1 igor igor 15146 Sep 3 19:22 NEWS
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 output
-rw-r--r-- 1 igor igor 860 Sep 3 19:22 PACKAGING_LEGACY.md
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 presets
-rw-r--r-- 1 igor igor 1964 Sep 3 19:22 README
drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 rules
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 schema
drwxr-xr-x 4 igor igor 4096 Sep 3 19:22 src
drwxr-xr-x 31 igor igor 4096 Sep 3 19:22 tests
-rw-r--r-- 1 igor igor 255 Sep 3 19:22 THANKS
igor@WaylandGnome ~/bakefile $ emerge -pv bakefile
[/code]
According to the README, I should do:
[code]
./configure && make && make install
[/code]
but I don't see any configure script here.
Thank you.
On Fri, Sep 3, 2021 at 5:24 PM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Fri, 3 Sep 2021 13:19:32 -0500 Igor Korot wrote:
>
> IK> Are we still using Bakefile? What version?
> IK>
> IK> How do I run it?
>
> The instructions in docs/contributing/how-to-add-files-to-build-system.md
> should still be valid.
igor@WaylandGnome ~/bakefile $ git status
On branch legacy-0.2-branch
Your branch is up to date with 'origin/legacy-0.2-branch'.
nothing to commit, working tree clean
igor@WaylandGnome ~/bakefile $
igor@WaylandGnome ~/bakefile $ ls -la
total 144
drwxr-xr-x 15 igor igor 4096 Sep 3 19:22 .
drwxr-xr-x 19 igor igor 4096 Sep 3 19:22 ..
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 admin
-rw-r--r-- 1 igor igor 1437 Sep 3 19:22 AUTHORS
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 autoconf
-rw-r--r-- 1 igor igor 10156 Sep 3 19:22 bakefile.iss
-rw-r--r-- 1 igor igor 1076 Sep 3 19:22 bakefile.spec
-rw-r--r-- 1 igor igor 1106 Sep 3 19:22 bakefile.vim
-rw-r--r-- 1 igor igor 2475 Sep 3 19:22 bash_completion
-rwxr-xr-x 1 igor igor 247 Sep 3 19:22 bootstrap
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 build
-rwxr-xr-x 1 igor igor 671 Sep 3 19:22 chversion.sh
-rw-r--r-- 1 igor igor 658 Sep 3 19:22 configure.in
-rw-r--r-- 1 igor igor 1062 Sep 3 19:22 COPYING
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 debian
drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 doc
drwxr-xr-x 7 igor igor 4096 Sep 3 19:22 .git
drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 macosx
-rw-r--r-- 1 igor igor 6024 Sep 3 19:22 Makefile.am
-rw-r--r-- 1 igor igor 841 Sep 3 19:22 makefile.vc
-rw-r--r-- 1 igor igor 15146 Sep 3 19:22 NEWS
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 output
-rw-r--r-- 1 igor igor 860 Sep 3 19:22 PACKAGING_LEGACY.md
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 presets
-rw-r--r-- 1 igor igor 1964 Sep 3 19:22 README
drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 rules
drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 schema
drwxr-xr-x 4 igor igor 4096 Sep 3 19:22 src
drwxr-xr-x 31 igor igor 4096 Sep 3 19:22 tests
-rw-r--r-- 1 igor igor 255 Sep 3 19:22 THANKS
igor@WaylandGnome ~/bakefile $ emerge -pv bakefile
[/code]
According to the README, I should do:
[code]
./configure && make && make install
[/code]
but I don't see any configure script here.
Thank you.
Igor Korot
Sep 3, 2021, 9:01:04 PM9/3/21
to wx-u...@googlegroups.com
And then,
[code]
igor@WaylandGnome ~/bakefile $ emerge -pv swig
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-lang/swig-4.0.2::gentoo USE="pcre -ccache -doc" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
* IMPORTANT: 2 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
igor@WaylandGnome ~/bakefile $ nano README
igor@WaylandGnome ~/bakefile $ emerge -pv libxslt
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-libs/libxslt-1.1.34-r1::gentoo USE="crypt -debug
-examples -static-libs -verify-sig" ABI_X86="(64) -32 (-x32)" 3,470
KiB
Total: 1 package (1 reinstall), Size of downloads: 3,470 KiB
* IMPORTANT: 2 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
igor@WaylandGnome ~/bakefile $ bootstrap
bash: bootstrap: command not found
igor@WaylandGnome ~/bakefile $
[/code]
Thank you.
igor@WaylandGnome ~/bakefile $ emerge -pv swig
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-lang/swig-4.0.2::gentoo USE="pcre -ccache -doc" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
* IMPORTANT: 2 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
igor@WaylandGnome ~/bakefile $ nano README
igor@WaylandGnome ~/bakefile $ emerge -pv libxslt
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-libs/libxslt-1.1.34-r1::gentoo USE="crypt -debug
-examples -static-libs -verify-sig" ABI_X86="(64) -32 (-x32)" 3,470
KiB
Total: 1 package (1 reinstall), Size of downloads: 3,470 KiB
* IMPORTANT: 2 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
igor@WaylandGnome ~/bakefile $ bootstrap
bash: bootstrap: command not found
igor@WaylandGnome ~/bakefile $
[/code]
Thank you.
Vadim Zeitlin
Sep 4, 2021, 6:23:53 AM9/4/21
to wx-u...@googlegroups.com
On Fri, 3 Sep 2021 19:52:33 -0500 Igor Korot wrote:
IK> Vadim,
IK>
IK> On Fri, Sep 3, 2021 at 5:24 PM Vadim Zeitlin <va...@wxwidgets.org> wrote:
IK> >
IK> > The instructions in docs/contributing/how-to-add-files-to-build-system.md
IK> > should still be valid.
IK>
IK> [code]
IK> igor@WaylandGnome ~/bakefile $ git status
IK> On branch legacy-0.2-branch
IK> Your branch is up to date with 'origin/legacy-0.2-branch'.
IK>
IK> nothing to commit, working tree clean
IK> igor@WaylandGnome ~/bakefile $
IK>
IK> igor@WaylandGnome ~/bakefile $ ls -la
IK> total 144
IK> drwxr-xr-x 15 igor igor 4096 Sep 3 19:22 .
IK> drwxr-xr-x 19 igor igor 4096 Sep 3 19:22 ..
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 admin
IK> -rw-r--r-- 1 igor igor 1437 Sep 3 19:22 AUTHORS
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 autoconf
IK> -rw-r--r-- 1 igor igor 10156 Sep 3 19:22 bakefile.iss
IK> -rw-r--r-- 1 igor igor 1076 Sep 3 19:22 bakefile.spec
IK> -rw-r--r-- 1 igor igor 1106 Sep 3 19:22 bakefile.vim
IK> -rw-r--r-- 1 igor igor 2475 Sep 3 19:22 bash_completion
IK> -rwxr-xr-x 1 igor igor 247 Sep 3 19:22 bootstrap
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 build
IK> -rwxr-xr-x 1 igor igor 671 Sep 3 19:22 chversion.sh
IK> -rw-r--r-- 1 igor igor 658 Sep 3 19:22 configure.in
IK> -rw-r--r-- 1 igor igor 1062 Sep 3 19:22 COPYING
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 debian
IK> drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 doc
IK> drwxr-xr-x 7 igor igor 4096 Sep 3 19:22 .git
IK> drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 macosx
IK> -rw-r--r-- 1 igor igor 6024 Sep 3 19:22 Makefile.am
IK> -rw-r--r-- 1 igor igor 841 Sep 3 19:22 makefile.vc
IK> -rw-r--r-- 1 igor igor 15146 Sep 3 19:22 NEWS
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 output
IK> -rw-r--r-- 1 igor igor 860 Sep 3 19:22 PACKAGING_LEGACY.md
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 presets
IK> -rw-r--r-- 1 igor igor 1964 Sep 3 19:22 README
IK> drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 rules
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 schema
IK> drwxr-xr-x 4 igor igor 4096 Sep 3 19:22 src
IK> drwxr-xr-x 31 igor igor 4096 Sep 3 19:22 tests
IK> -rw-r--r-- 1 igor igor 255 Sep 3 19:22 THANKS
IK> igor@WaylandGnome ~/bakefile $ emerge -pv bakefile
IK> [/code]
IK>
IK> According to the README, I should do:
IK>
IK> [code]
IK> ./configure && make && make install
IK> [/code]
IK>
IK> but I don't see any configure script here.
You need to run "./bootstrap" script.
Dealing with bakefile is unpleasant (and we'll replace it with something
else soon), but the thing I don't understand is that you had already
changed the makefiles in your original PR version. How did you do it then
if you didn't use it?
IK> Vadim,
IK>
IK> On Fri, Sep 3, 2021 at 5:24 PM Vadim Zeitlin <va...@wxwidgets.org> wrote:
IK> >
IK> > On Fri, 3 Sep 2021 13:19:32 -0500 Igor Korot wrote:
IK> >
IK> > IK> Are we still using Bakefile? What version?
IK> >
IK> > IK>
IK> > IK> How do I run it?
IK> >
IK> > IK> How do I run it?
IK> > The instructions in docs/contributing/how-to-add-files-to-build-system.md
IK> > should still be valid.
IK>
IK> [code]
IK> igor@WaylandGnome ~/bakefile $ git status
IK> On branch legacy-0.2-branch
IK> Your branch is up to date with 'origin/legacy-0.2-branch'.
IK>
IK> nothing to commit, working tree clean
IK> igor@WaylandGnome ~/bakefile $
IK>
IK> igor@WaylandGnome ~/bakefile $ ls -la
IK> total 144
IK> drwxr-xr-x 15 igor igor 4096 Sep 3 19:22 .
IK> drwxr-xr-x 19 igor igor 4096 Sep 3 19:22 ..
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 admin
IK> -rw-r--r-- 1 igor igor 1437 Sep 3 19:22 AUTHORS
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 autoconf
IK> -rw-r--r-- 1 igor igor 10156 Sep 3 19:22 bakefile.iss
IK> -rw-r--r-- 1 igor igor 1076 Sep 3 19:22 bakefile.spec
IK> -rw-r--r-- 1 igor igor 1106 Sep 3 19:22 bakefile.vim
IK> -rw-r--r-- 1 igor igor 2475 Sep 3 19:22 bash_completion
IK> -rwxr-xr-x 1 igor igor 247 Sep 3 19:22 bootstrap
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 build
IK> -rwxr-xr-x 1 igor igor 671 Sep 3 19:22 chversion.sh
IK> -rw-r--r-- 1 igor igor 658 Sep 3 19:22 configure.in
IK> -rw-r--r-- 1 igor igor 1062 Sep 3 19:22 COPYING
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 debian
IK> drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 doc
IK> drwxr-xr-x 7 igor igor 4096 Sep 3 19:22 .git
IK> drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 macosx
IK> -rw-r--r-- 1 igor igor 6024 Sep 3 19:22 Makefile.am
IK> -rw-r--r-- 1 igor igor 841 Sep 3 19:22 makefile.vc
IK> -rw-r--r-- 1 igor igor 15146 Sep 3 19:22 NEWS
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 output
IK> -rw-r--r-- 1 igor igor 860 Sep 3 19:22 PACKAGING_LEGACY.md
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 presets
IK> -rw-r--r-- 1 igor igor 1964 Sep 3 19:22 README
IK> drwxr-xr-x 3 igor igor 4096 Sep 3 19:22 rules
IK> drwxr-xr-x 2 igor igor 4096 Sep 3 19:22 schema
IK> drwxr-xr-x 4 igor igor 4096 Sep 3 19:22 src
IK> drwxr-xr-x 31 igor igor 4096 Sep 3 19:22 tests
IK> -rw-r--r-- 1 igor igor 255 Sep 3 19:22 THANKS
IK> igor@WaylandGnome ~/bakefile $ emerge -pv bakefile
IK> [/code]
IK>
IK> According to the README, I should do:
IK>
IK> [code]
IK> ./configure && make && make install
IK> [/code]
IK>
IK> but I don't see any configure script here.
You need to run "./bootstrap" script.
Dealing with bakefile is unpleasant (and we'll replace it with something
else soon), but the thing I don't understand is that you had already
changed the makefiles in your original PR version. How did you do it then
if you didn't use it?
Igor Korot
Sep 4, 2021, 9:32:44 AM9/4/21
to wx-u...@googlegroups.com
Vadim,
I don't remember what I did.
And how I installed bakeries.
I'll try that today.
Igor Korot
Sep 4, 2021, 2:21:32 PM9/4/21
to wx-u...@googlegroups.com
Vadim,
Got couple of warnings on the bootstrap run:
[code]
igor@WaylandGnome ~/bakefile $ ./bootstrap
aclocal-1.16: warning: autoconf input should be named 'configure.ac',
not 'configure.in'
automake-1.16: warning: autoconf input should be named 'configure.ac',
not 'configure.in'
configure.in:14: installing 'admin/compile'
configure.in:8: installing 'admin/config.guess'
configure.in:8: installing 'admin/config.sub'
configure.in:11: installing 'admin/install-sh'
configure.in:11: installing 'admin/missing'
automake-1.16: warning: autoconf input should be named 'configure.ac',
not 'configure.in'
Makefile.am:130: warning: source file 'src/bottlenecks.c' is in a subdirectory,
Makefile.am:130: but option 'subdir-objects' is disabled
automake-1.16: warning: possible forward-incompatibility.
automake-1.16: At least a source file is in a subdirectory, but the
'subdir-objects'
automake-1.16: automake option hasn't been enabled. For now, the
corresponding output
automake-1.16: object file(s) will be placed in the top-level
directory. However,
automake-1.16: this behaviour will change in future Automake versions: they will
automake-1.16: unconditionally cause object files to be placed in the
same subdirectory
automake-1.16: of the corresponding sources.
automake-1.16: You are advised to start using 'subdir-objects' option
throughout your
automake-1.16: project, to avoid future incompatibilities.
Makefile.am:130: warning: source file 'src/bkl_c_wrap.c' is in a subdirectory,
Makefile.am:130: but option 'subdir-objects' is disabled
Makefile.am: installing 'admin/depcomp'
Makefile.am:101: installing 'admin/py-compile'
[code]
igor@WaylandGnome ~/bakefile $ ./bootstrap
aclocal-1.16: warning: autoconf input should be named 'configure.ac',
not 'configure.in'
automake-1.16: warning: autoconf input should be named 'configure.ac',
not 'configure.in'
configure.in:14: installing 'admin/compile'
configure.in:8: installing 'admin/config.guess'
configure.in:8: installing 'admin/config.sub'
configure.in:11: installing 'admin/install-sh'
configure.in:11: installing 'admin/missing'
automake-1.16: warning: autoconf input should be named 'configure.ac',
not 'configure.in'
Makefile.am:130: warning: source file 'src/bottlenecks.c' is in a subdirectory,
Makefile.am:130: but option 'subdir-objects' is disabled
automake-1.16: warning: possible forward-incompatibility.
automake-1.16: At least a source file is in a subdirectory, but the
'subdir-objects'
automake-1.16: automake option hasn't been enabled. For now, the
corresponding output
automake-1.16: object file(s) will be placed in the top-level
directory. However,
automake-1.16: this behaviour will change in future Automake versions: they will
automake-1.16: unconditionally cause object files to be placed in the
same subdirectory
automake-1.16: of the corresponding sources.
automake-1.16: You are advised to start using 'subdir-objects' option
throughout your
automake-1.16: project, to avoid future incompatibilities.
Makefile.am:130: warning: source file 'src/bkl_c_wrap.c' is in a subdirectory,
Makefile.am:130: but option 'subdir-objects' is disabled
Makefile.am: installing 'admin/depcomp'
Makefile.am:101: installing 'admin/py-compile'
igor@WaylandGnome ~/bakefile $
[/code]
Thank you.
>
[/code]
Thank you.
>
Igor Korot
Sep 4, 2021, 2:43:12 PM9/4/21
to wx-u...@googlegroups.com
And then running configure I got the following:
[code]
igor@WaylandGnome ~/bakefile $ ./configure && make
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to
x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain
format... func_convert_file_noop
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m
elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for a Python interpreter with version >= 2.3.0... python
checking for python... /usr/bin/python
checking for python version... 3.9
checking for python platform... linux
checking for python script directory... ${prefix}/lib/python3.9/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python3.9/site-packages
checking for Python include path... File "<string>", line 1
from distutils import sysconfig; print sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
configure: error: cannot find Python include path
igor@WaylandGnome ~/bakefile $
[/code]
The fix is to use:
[code]
igor@WaylandGnome ~/bakefile $ python
Python 3.9.6 (default, Aug 8 2021, 17:26:32)
[GCC 10.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from distutils import sysconfig
>>> print sysconfig.get_python_inc()
File "<stdin>", line 1
print sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
>>> print( sysconfig.get_python_inc() )
/usr/include/python3.9
>>>
[/code]
Thank you.
[code]
igor@WaylandGnome ~/bakefile $ ./configure && make
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to
x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain
format... func_convert_file_noop
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m
elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for a Python interpreter with version >= 2.3.0... python
checking for python... /usr/bin/python
checking for python version... 3.9
checking for python platform... linux
checking for python script directory... ${prefix}/lib/python3.9/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python3.9/site-packages
checking for Python include path... File "<string>", line 1
from distutils import sysconfig; print sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
configure: error: cannot find Python include path
igor@WaylandGnome ~/bakefile $
[/code]
The fix is to use:
[code]
igor@WaylandGnome ~/bakefile $ python
Python 3.9.6 (default, Aug 8 2021, 17:26:32)
[GCC 10.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from distutils import sysconfig
>>> print sysconfig.get_python_inc()
File "<stdin>", line 1
print sysconfig.get_python_inc()
^
SyntaxError: invalid syntax
>>> print( sysconfig.get_python_inc() )
/usr/include/python3.9
>>>
[/code]
Thank you.
Igor Korot
Sep 4, 2021, 2:46:28 PM9/4/21
to wx-u...@googlegroups.com
And after fixing this in configure, I got:
checking for Python include path... /usr/include/python3.9
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
Making all in doc
make[1]: Entering directory '/home/igor/bakefile/doc'
make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'. Stop.
make[1]: Leaving directory '/home/igor/bakefile/doc'
make: *** [Makefile:1018: all-recursive] Error 1
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
Making all in doc
make[1]: Entering directory '/home/igor/bakefile/doc'
make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'. Stop.
make[1]: Leaving directory '/home/igor/bakefile/doc'
make: *** [Makefile:1018: all-recursive] Error 1
igor@WaylandGnome ~/bakefile $
[/code]
Thank you.
[/code]
Thank you.
Vadim Zeitlin
Sep 4, 2021, 5:17:44 PM9/4/21
to wx-u...@googlegroups.com
On Sat, 4 Sep 2021 13:42:33 -0500 Igor Korot wrote:
IK> And then running configure I got the following:
...
IK> checking for Python include path... File "<string>", line 1
IK> from distutils import sysconfig; print sysconfig.get_python_inc()
IK> ^
IK> SyntaxError: invalid syntax
You need to use Python 2 for bakefile.
IK> And then running configure I got the following:
...
IK> checking for Python include path... File "<string>", line 1
IK> from distutils import sysconfig; print sysconfig.get_python_inc()
IK> ^
IK> SyntaxError: invalid syntax
You need to use Python 2 for bakefile.
Igor Korot
Sep 4, 2021, 5:21:25 PM9/4/21
to wx-u...@googlegroups.com
Vadim,
On Sat, Sep 4, 2021, 16:17 Vadim Zeitlin <va...@wxwidgets.org> wrote:
On Sat, 4 Sep 2021 13:42:33 -0500 Igor Korot wrote:
IK> And then running configure I got the following:
...
IK> checking for Python include path... File "<string>", line 1
IK> from distutils import sysconfig; print sysconfig.get_python_inc()
IK> ^
IK> SyntaxError: invalid syntax
You need to use Python 2 for bakefile.
IIUC, this syntaxes is supported in both versions.
Thank you.
Scott Talbert
Sep 4, 2021, 5:38:43 PM9/4/21
to wx-u...@googlegroups.com
On Sat, 4 Sep 2021, Igor Korot wrote:
> Vadim,
>
> On Sat, Sep 4, 2021, 16:17 Vadim Zeitlin <va...@wxwidgets.org> wrote:
> On Sat, 4 Sep 2021 13:42:33 -0500 Igor Korot wrote:
>
> IK> And then running configure I got the following:
> ...
> IK> checking for Python include path... File "<string>", line
> 1
> IK> from distutils import sysconfig; print
> sysconfig.get_python_inc()
> IK> ^
> IK> SyntaxError: invalid syntax
>
> You need to use Python 2 for bakefile.
>
>
> IIUC, this syntaxes is supported in both versions.
Bakefile needs a lot more work than that to support Python 3. Believe me,
> Vadim,
>
> On Sat, Sep 4, 2021, 16:17 Vadim Zeitlin <va...@wxwidgets.org> wrote:
> On Sat, 4 Sep 2021 13:42:33 -0500 Igor Korot wrote:
>
> IK> And then running configure I got the following:
> ...
> IK> checking for Python include path... File "<string>", line
> 1
> IK> from distutils import sysconfig; print
> sysconfig.get_python_inc()
> IK> ^
> IK> SyntaxError: invalid syntax
>
> You need to use Python 2 for bakefile.
>
>
> IIUC, this syntaxes is supported in both versions.
I tried. You need to use Python 2 unfortunately.
Scott
Igor Korot
Sep 4, 2021, 7:58:21 PM9/4/21
to wx-u...@googlegroups.com
Hi,
I don't even know if I have python 2.
It is ended in January of 2020.
I guess I have to get the binaries then...
Thank you.
Scott
--
Please read https://www.wxwidgets.org/support/mlhowto.htm before posting.
---
You received this message because you are subscribed to the Google Groups "wx-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wx-users+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wx-users/alpine.DEB.2.22.394.2109041737040.607950%40bear.techie.net.
Igor Korot
Sep 4, 2021, 9:57:28 PM9/4/21
to wx-u...@googlegroups.com
Hi,
On Sat, Sep 4, 2021 at 6:58 PM Igor Korot <ikor...@gmail.com> wrote:
>
> Hi,
>
>
>
> On Sat, Sep 4, 2021, 16:38 Scott Talbert <s...@techie.net> wrote:
>>
>> On Sat, 4 Sep 2021, Igor Korot wrote:
>>
>> > Vadim,
>> >
>> > On Sat, Sep 4, 2021, 16:17 Vadim Zeitlin <va...@wxwidgets.org> wrote:
>> > On Sat, 4 Sep 2021 13:42:33 -0500 Igor Korot wrote:
>> >
>> > IK> And then running configure I got the following:
>> > ...
>> > IK> checking for Python include path... File "<string>", line
>> > 1
>> > IK> from distutils import sysconfig; print
>> > sysconfig.get_python_inc()
>> > IK> ^
>> > IK> SyntaxError: invalid syntax
>> >
>> > You need to use Python 2 for bakefile.
>> >
>> >
>> > IIUC, this syntaxes is supported in both versions.
>>
>> Bakefile needs a lot more work than that to support Python 3. Believe me,
>> I tried. You need to use Python 2 unfortunately.
Looks like even on python 2 there is a problem:
[code]
igor@IgorReinCloud ~/bakefile $ git checkout legacy-0.2-branch
Branch 'legacy-0.2-branch' set up to track remote branch
'legacy-0.2-branch' from 'origin'.
Switched to a new branch 'legacy-0.2-branch'
igor@IgorReinCloud ~/bakefile $ ./bootstrap
igor@IgorReinCloud ~/bakefile $ ./configure && make
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib64/python2.7/site-packages
checking for Python include path... /usr/include/python2.7
igor@IgorReinCloud ~/bakefile $ python
Python 2.7.18 (default, Apr 18 2021, 17:03:09)
[GCC 7.3.0] on linux2
[/code]
Thank you.
On Sat, Sep 4, 2021 at 6:58 PM Igor Korot <ikor...@gmail.com> wrote:
>
> Hi,
>
>
>
> On Sat, Sep 4, 2021, 16:38 Scott Talbert <s...@techie.net> wrote:
>>
>> On Sat, 4 Sep 2021, Igor Korot wrote:
>>
>> > Vadim,
>> >
>> > On Sat, Sep 4, 2021, 16:17 Vadim Zeitlin <va...@wxwidgets.org> wrote:
>> > On Sat, 4 Sep 2021 13:42:33 -0500 Igor Korot wrote:
>> >
>> > IK> And then running configure I got the following:
>> > ...
>> > IK> checking for Python include path... File "<string>", line
>> > 1
>> > IK> from distutils import sysconfig; print
>> > sysconfig.get_python_inc()
>> > IK> ^
>> > IK> SyntaxError: invalid syntax
>> >
>> > You need to use Python 2 for bakefile.
>> >
>> >
>> > IIUC, this syntaxes is supported in both versions.
>>
>> Bakefile needs a lot more work than that to support Python 3. Believe me,
>> I tried. You need to use Python 2 unfortunately.
[code]
igor@IgorReinCloud ~/bakefile $ git checkout legacy-0.2-branch
Branch 'legacy-0.2-branch' set up to track remote branch
'legacy-0.2-branch' from 'origin'.
Switched to a new branch 'legacy-0.2-branch'
igor@IgorReinCloud ~/bakefile $ ./bootstrap
checking for python platform... linux2
checking for python script directory... ${prefix}/lib64/python2.7/site-packages
checking for python extension module directory...
${exec_prefix}/lib64/python2.7/site-packages
checking for Python include path... /usr/include/python2.7
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
Making all in doc
make[1]: Entering directory '/home/igor/bakefile/doc'
make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'. Stop.
make[1]: Leaving directory '/home/igor/bakefile/doc'
make: *** [Makefile:1016: all-recursive] Error 1
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
Making all in doc
make[1]: Entering directory '/home/igor/bakefile/doc'
make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'. Stop.
make[1]: Leaving directory '/home/igor/bakefile/doc'
igor@IgorReinCloud ~/bakefile $ python
Python 2.7.18 (default, Apr 18 2021, 17:03:09)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> quit()
[/code]
Thank you.
Igor Korot
Sep 5, 2021, 1:49:48 AM9/5/21
to wx-u...@googlegroups.com
And I do have the required packages installed:
[code]
IgorReinCloud /home/igor # emerge -pv libxslt
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-libs/libxslt-1.1.34-r1::gentoo USE="crypt -debug
-examples -static-libs -verify-sig%" ABI_X86="(64) -32 (-x32)" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
IgorReinCloud /home/igor # emerge -pv docbook-xsl-stylesheets
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] app-text/docbook-xsl-stylesheets-1.79.1-r2::gentoo
USE="-ruby" 21,454 KiB
Total: 1 package (1 reinstall), Size of downloads: 21,454 KiB
* IMPORTANT: 4 news items need reading for repository 'gentoo'.
[/code]
Thank you.
[code]
IgorReinCloud /home/igor # emerge -pv libxslt
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-libs/libxslt-1.1.34-r1::gentoo USE="crypt -debug
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
These are the packages that would be merged, in order:
Calculating dependencies... done!
USE="-ruby" 21,454 KiB
Total: 1 package (1 reinstall), Size of downloads: 21,454 KiB
* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
IgorReinCloud /home/igor #
[/code]
Thank you.
Vadim Zeitlin
Sep 5, 2021, 6:33:02 AM9/5/21
to wx-u...@googlegroups.com
On Sat, 4 Sep 2021 21:02:27 -0500 Igor Korot wrote:
IK> Looks like even on python 2 there is a problem:
[...]
IK> Making all in doc
IK> make[1]: Entering directory '/home/igor/bakefile/doc'
IK> make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'. Stop.
I don't know what's going on here, normally this file should be generated
by xsltproc (maybe you don't have it), but you can comment out "SUBDIRS =
doc" line in the top-level Makefile.am to skip building the docs entirely.
IK> Looks like even on python 2 there is a problem:
[...]
IK> Making all in doc
IK> make[1]: Entering directory '/home/igor/bakefile/doc'
IK> make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'. Stop.
I don't know what's going on here, normally this file should be generated
by xsltproc (maybe you don't have it), but you can comment out "SUBDIRS =
doc" line in the top-level Makefile.am to skip building the docs entirely.
Igor Korot
Sep 5, 2021, 11:48:31 AM9/5/21
to wx-u...@googlegroups.com
Vadim,
On Sun, Sep 5, 2021 at 5:33 AM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Sat, 4 Sep 2021 21:02:27 -0500 Igor Korot wrote:
>
> IK> Looks like even on python 2 there is a problem:
> [...]
> IK> Making all in doc
> IK> make[1]: Entering directory '/home/igor/bakefile/doc'
> IK> make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'. Stop.
>
> I don't know what's going on here, normally this file should be generated
> by xsltproc (maybe you don't have it)...
[code]
igor@IgorReinCloud ~ $ which xsltproc
/usr/bin/xsltproc
[/code]
I'm also attaching the Makefile from the bakefile/doc directory.
>..., but you can comment out "SUBDIRS =
Sorry I'm just not familiar with the Linux build system...
Thank you.
On Sun, Sep 5, 2021 at 5:33 AM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Sat, 4 Sep 2021 21:02:27 -0500 Igor Korot wrote:
>
> IK> Looks like even on python 2 there is a problem:
> [...]
> IK> Making all in doc
> IK> make[1]: Entering directory '/home/igor/bakefile/doc'
> IK> make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'. Stop.
>
> I don't know what's going on here, normally this file should be generated
[code]
igor@IgorReinCloud ~ $ which xsltproc
/usr/bin/xsltproc
[/code]
I'm also attaching the Makefile from the bakefile/doc directory.
>..., but you can comment out "SUBDIRS =
> doc" line in the top-level Makefile.am to skip building the docs entirely.
If I do that - should I re-run "configure"?
Sorry I'm just not familiar with the Linux build system...
Thank you.
Vadim Zeitlin
Sep 5, 2021, 11:53:52 AM9/5/21
to wx-u...@googlegroups.com
On Sun, 5 Sep 2021 10:53:30 -0500 Igor Korot wrote:
IK> >..., but you can comment out "SUBDIRS =
IK> > doc" line in the top-level Makefile.am to skip building the docs entirely.
IK>
IK> If I do that - should I re-run "configure"?
Rerunning make will do it for you, but you don't lose anything by
rerunning it manually neither and it actually takes less time than a
round-trip to the mailing list...
IK> >..., but you can comment out "SUBDIRS =
IK> > doc" line in the top-level Makefile.am to skip building the docs entirely.
IK>
IK> If I do that - should I re-run "configure"?
Rerunning make will do it for you, but you don't lose anything by
rerunning it manually neither and it actually takes less time than a
round-trip to the mailing list...
Igor Korot
Sep 5, 2021, 12:32:45 PM9/5/21
to wx-u...@googlegroups.com
Vadim,
On Sun, Sep 5, 2021 at 10:53 AM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Sun, 5 Sep 2021 10:53:30 -0500 Igor Korot wrote:
>
> IK> >..., but you can comment out "SUBDIRS =
> IK> > doc" line in the top-level Makefile.am to skip building the docs entirely.
> IK>
> IK> If I do that - should I re-run "configure"?
>
> Rerunning make will do it for you, but you don't lose anything by
> rerunning it manually neither and it actually takes less time than a
> round-trip to the mailing list...
I re-run "./bootstrap", because I had couple of warnings. Here they are:
[code]
igor@IgorReinCloud ~/bakefile $ ./bootstrap
igor@IgorReinCloud ~/bakefile $
[/code]
On Sun, Sep 5, 2021 at 10:53 AM Vadim Zeitlin <va...@wxwidgets.org> wrote:
>
> On Sun, 5 Sep 2021 10:53:30 -0500 Igor Korot wrote:
>
> IK> >..., but you can comment out "SUBDIRS =
> IK> > doc" line in the top-level Makefile.am to skip building the docs entirely.
> IK>
> IK> If I do that - should I re-run "configure"?
>
> Rerunning make will do it for you, but you don't lose anything by
> rerunning it manually neither and it actually takes less time than a
> round-trip to the mailing list...
[code]
igor@IgorReinCloud ~/bakefile $ ./bootstrap
[/code]
Igor Korot
Sep 5, 2021, 12:43:14 PM9/5/21
to wx-u...@googlegroups.com
Vadim,
The README says:
[quote]
Building from Subversion repository
-------------------------------------
(Note: this does _not_ apply to downloaded tarballs, only to code fetched
from SourceForge Subversion repository.)
Run bootstrap script and then proceed as when building from tarball. In order
to run bootstrap successfully, you need the following packages: SWIG 1.3.x
(http://www.swig.org), Automake >= 1.6, Autoconf >= 2.53, libtool, libxslt
(including xsltproc program) and DocBook XSL stylesheets (last two are needed
only to build HTML documentation).
On Windows, you need SWIG to build Bakefile from Subversion sources.
[/quote]
However, I have automake -1.16.
Could this be a problem?
Thank you.
[quote]
Building from Subversion repository
-------------------------------------
(Note: this does _not_ apply to downloaded tarballs, only to code fetched
from SourceForge Subversion repository.)
Run bootstrap script and then proceed as when building from tarball. In order
to run bootstrap successfully, you need the following packages: SWIG 1.3.x
(http://www.swig.org), Automake >= 1.6, Autoconf >= 2.53, libtool, libxslt
(including xsltproc program) and DocBook XSL stylesheets (last two are needed
only to build HTML documentation).
On Windows, you need SWIG to build Bakefile from Subversion sources.
[/quote]
However, I have automake -1.16.
Could this be a problem?
Thank you.
Vadim Zeitlin
Sep 5, 2021, 12:47:41 PM9/5/21
to wx-u...@googlegroups.com
On Sun, 5 Sep 2021 11:48:12 -0500 Igor Korot wrote:
IK> The README says:
IK>
IK> [quote]
IK> Building from Subversion repository
IK> -------------------------------------
IK>
IK> (Note: this does not apply to downloaded tarballs, only to code fetched
IK> from SourceForge Subversion repository.)
IK> Run bootstrap script and then proceed as when building from tarball. In order
IK> to run bootstrap successfully, you need the following packages: SWIG 1.3.x
IK> (http://www.swig.org), Automake >= 1.6, Autoconf >= 2.53, libtool, libxslt
IK> (including xsltproc program) and DocBook XSL stylesheets (last two are needed
IK> only to build HTML documentation).
IK> On Windows, you need SWIG to build Bakefile from Subversion sources.
IK> [/quote]
IK>
IK> However, I have automake -1.16.
IK>
IK> Could this be a problem?
Sorry, I have no idea what your problem is. If you've removed doc from the
subdirectories list you shouldn't have the only real problem that you've
shown any longer. All the rest are warnings that you really shouldn't care
about, as I already said we're not going to do anything about fixing
anything in bakefile because we'll stop using it soon.
Please try to formulate better what you're asking.
IK> The README says:
IK>
IK> [quote]
IK> Building from Subversion repository
IK> -------------------------------------
IK>
IK> (Note: this does not apply to downloaded tarballs, only to code fetched
IK> from SourceForge Subversion repository.)
IK> Run bootstrap script and then proceed as when building from tarball. In order
IK> to run bootstrap successfully, you need the following packages: SWIG 1.3.x
IK> (http://www.swig.org), Automake >= 1.6, Autoconf >= 2.53, libtool, libxslt
IK> (including xsltproc program) and DocBook XSL stylesheets (last two are needed
IK> only to build HTML documentation).
IK> On Windows, you need SWIG to build Bakefile from Subversion sources.
IK> [/quote]
IK>
IK> However, I have automake -1.16.
IK>
IK> Could this be a problem?
Sorry, I have no idea what your problem is. If you've removed doc from the
subdirectories list you shouldn't have the only real problem that you've
shown any longer. All the rest are warnings that you really shouldn't care
about, as I already said we're not going to do anything about fixing
anything in bakefile because we'll stop using it soon.
Please try to formulate better what you're asking.
Reply all
Reply to author
Forward
0 new messages