Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

To downgrade the human mind is bad theology. -- C. K. Chesterton


devel / comp.lang.mumps / Re: Many notices and warnings with compiling YottaDB 1.32 from sources

SubjectAuthor
* Many notices and warnings with compiling YottaDB 1.32 from sourcesСергей Каменев
`* Re: Many notices and warnings with compiling YottaDB 1.32 from sourcesK.S. Bhaskar
 `* Re: Many notices and warnings with compiling YottaDB 1.32 from sourcesK.S. Bhaskar
  `* Re: Many notices and warnings with compiling YottaDB 1.32 from sourcesСергей Каменев
   `* Re: Many notices and warnings with compiling YottaDB 1.32 from sourcesСергей Каменев
    `- Re: Many notices and warnings with compiling YottaDB 1.32 from sourcesK.S. Bhaskar

1
Many notices and warnings with compiling YottaDB 1.32 from sources

<63c0af09-5427-477c-9f6b-ccae7288b41cn@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=176&group=comp.lang.mumps#176

  copy link   Newsgroups: comp.lang.mumps
X-Received: by 2002:ac8:4e36:: with SMTP id d22mr3896329qtw.9.1633186346275;
Sat, 02 Oct 2021 07:52:26 -0700 (PDT)
X-Received: by 2002:a37:a60f:: with SMTP id p15mr2782524qke.114.1633186345895;
Sat, 02 Oct 2021 07:52:25 -0700 (PDT)
Path: i2pn2.org!rocksolid2!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.mumps
Date: Sat, 2 Oct 2021 07:52:25 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=193.107.193.43; posting-account=eaShnQoAAABLy95ZTEb7H0YHkVXcD4qO
NNTP-Posting-Host: 193.107.193.43
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <63c0af09-5427-477c-9f6b-ccae7288b41cn@googlegroups.com>
Subject: Many notices and warnings with compiling YottaDB 1.32 from sources
From: sukamenev@gmail.com (Сергей Каменев)
Injection-Date: Sat, 02 Oct 2021 14:52:26 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 72
 by: Сергей Кам - Sat, 2 Oct 2021 14:52 UTC

Hi!
Is that how it should be? Is this normal or am I doing something wrong?
gcc 10.3.0

....
[ 89%] Building C object CMakeFiles/libyottadb.dir/sr_unix/ftok_main.c.o
[ 89%] Linking C shared module libyottadb.so
/tmp/tmp/YDB/sr_port/gdsfhead.h:1101:21: warning: type of ‘pin_fail_bt’ does not match original declaration [-Wlto-type-mismatch]
1101 | GBLREF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
| ^
/tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: ‘pin_fail_bt’ was previously declared here
891 | GBLDEF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
| ^
/tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
/tmp/tmp/YDB/sr_port/gdsfhead.h:1102:16: warning: type of ‘pin_fail_bt_contents’ does not match original declaration [-Wlto-type-mismatch]
1102 | GBLREF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
| ^
/tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: ‘pin_fail_bt_contents’ was previously declared here
892 | GBLDEF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
| ^
/tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
/tmp/tmp/YDB/sr_port/dm_setup.c:20:18: warning: type of ‘gtm_err_dev’ does not match original declaration [-Wlto-type-mismatch]
20 | GBLREF io_desc *gtm_err_dev;
| ^
/tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: ‘gtm_err_dev’ was previously declared here
412 | GBLDEF io_desc *gtm_err_dev;
| ^
/tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
/tmp/tmp/YDB/sr_port/m_zwrite.c:47:25: warning: type of ‘svn_data’ does not match original declaration [-Wlto-type-mismatch]
47 | LITREF svn_data_type svn_data[];
| ^
/tmp/tmp/YDB/sr_port/expritem.c:147:22: note: ‘svn_data’ was previously declared here
147 | LITDEF svn_data_type svn_data[] | ^
/tmp/tmp/YDB/sr_port/op_close.c:27:18: warning: type of ‘active_device’ does not match original declaration [-Wlto-type-mismatch]
27 | GBLREF io_desc *active_device;
| ^
/tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: ‘active_device’ was previously declared here
161 | GBLDEF io_desc *active_device;
| ^
/tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
[ 89%] Built target libyottadb
Scanning dependencies of target dse
Scanning dependencies of target gtcm_pkdisp
Scanning dependencies of target yottadb
Scanning dependencies of target dbcertify
Scanning dependencies of target lke
Scanning dependencies of target mupip
Scanning dependencies of target gtmsecshr_real
[ 89%] Building C object CMakeFiles/dse.dir/sr_unix/dse.c.o
[ 89%] Building C object CMakeFiles/semstat2.dir/sr_unix/semstat2.c.o
[ 89%] Building C object CMakeFiles/gtcm_pkdisp.dir/sr_unix_cm/gtcm_pkdisp.c.o
....

Re: Many notices and warnings with compiling YottaDB 1.32 from sources

<f610f3e6-ad8e-40a9-849d-3e611189c07bn@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=177&group=comp.lang.mumps#177

  copy link   Newsgroups: comp.lang.mumps
X-Received: by 2002:a37:6215:: with SMTP id w21mr11637600qkb.354.1633374798283;
Mon, 04 Oct 2021 12:13:18 -0700 (PDT)
X-Received: by 2002:ac8:4588:: with SMTP id l8mr14935494qtn.207.1633374798059;
Mon, 04 Oct 2021 12:13:18 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.mumps
Date: Mon, 4 Oct 2021 12:13:17 -0700 (PDT)
In-Reply-To: <63c0af09-5427-477c-9f6b-ccae7288b41cn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=108.52.84.50; posting-account=zTPg1AoAAABx_LtAQ3dW6FBnU1dwmSvl
NNTP-Posting-Host: 108.52.84.50
References: <63c0af09-5427-477c-9f6b-ccae7288b41cn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f610f3e6-ad8e-40a9-849d-3e611189c07bn@googlegroups.com>
Subject: Re: Many notices and warnings with compiling YottaDB 1.32 from sources
From: ksbhaskar@gmail.com (K.S. Bhaskar)
Injection-Date: Mon, 04 Oct 2021 19:13:18 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 82
 by: K.S. Bhaskar - Mon, 4 Oct 2021 19:13 UTC

On Saturday, October 2, 2021 at 10:52:26 AM UTC-4, suka...@gmail.com wrote:
> Hi!
> Is that how it should be? Is this normal or am I doing something wrong?
> gcc 10.3.0
>
> ...
> [ 89%] Building C object CMakeFiles/libyottadb.dir/sr_unix/ftok_main.c.o
> [ 89%] Linking C shared module libyottadb.so
> /tmp/tmp/YDB/sr_port/gdsfhead.h:1101:21: warning: type of ‘pin_fail_bt’ does not match original declaration [-Wlto-type-mismatch]
> 1101 | GBLREF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> | ^
> /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: ‘pin_fail_bt’ was previously declared here
> 891 | GBLDEF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> | ^
> /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> /tmp/tmp/YDB/sr_port/gdsfhead.h:1102:16: warning: type of ‘pin_fail_bt_contents’ does not match original declaration [-Wlto-type-mismatch]
> 1102 | GBLREF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> | ^
> /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: ‘pin_fail_bt_contents’ was previously declared here
> 892 | GBLDEF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> | ^
> /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> /tmp/tmp/YDB/sr_port/dm_setup.c:20:18: warning: type of ‘gtm_err_dev’ does not match original declaration [-Wlto-type-mismatch]
> 20 | GBLREF io_desc *gtm_err_dev;
> | ^
> /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: ‘gtm_err_dev’ was previously declared here
> 412 | GBLDEF io_desc *gtm_err_dev;
> | ^
> /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> /tmp/tmp/YDB/sr_port/m_zwrite.c:47:25: warning: type of ‘svn_data’ does not match original declaration [-Wlto-type-mismatch]
> 47 | LITREF svn_data_type svn_data[];
> | ^
> /tmp/tmp/YDB/sr_port/expritem.c:147:22: note: ‘svn_data’ was previously declared here
> 147 | LITDEF svn_data_type svn_data[] =
> | ^
> /tmp/tmp/YDB/sr_port/op_close.c:27:18: warning: type of ‘active_device’ does not match original declaration [-Wlto-type-mismatch]
> 27 | GBLREF io_desc *active_device;
> | ^
> /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: ‘active_device’ was previously declared here
> 161 | GBLDEF io_desc *active_device;
> | ^
> /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> [ 89%] Built target libyottadb
> Scanning dependencies of target dse
> Scanning dependencies of target gtcm_pkdisp
> Scanning dependencies of target yottadb
> Scanning dependencies of target dbcertify
> Scanning dependencies of target lke
> Scanning dependencies of target mupip
> Scanning dependencies of target gtmsecshr_real
> [ 89%] Building C object CMakeFiles/dse.dir/sr_unix/dse.c.o
> [ 89%] Building C object CMakeFiles/semstat2.dir/sr_unix/semstat2.c.o
> [ 89%] Building C object CMakeFiles/gtcm_pkdisp.dir/sr_unix_cm/gtcm_pkdisp.c.o
> ...

Are you following the instructions in the README, or are you trying to compile it yourself with your own gcc flags? gcc flags do matter. Also, which Linux distribution/version are you using? Thank you.

Regards
– Bhaskar

Re: Many notices and warnings with compiling YottaDB 1.32 from sources

<136014a0-80cc-4c7d-8acf-30ba27c6ac6an@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=179&group=comp.lang.mumps#179

  copy link   Newsgroups: comp.lang.mumps
X-Received: by 2002:a37:a095:: with SMTP id j143mr15519053qke.277.1633447810885;
Tue, 05 Oct 2021 08:30:10 -0700 (PDT)
X-Received: by 2002:ac8:4291:: with SMTP id o17mr20506115qtl.147.1633447810581;
Tue, 05 Oct 2021 08:30:10 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.mumps
Date: Tue, 5 Oct 2021 08:30:10 -0700 (PDT)
In-Reply-To: <f610f3e6-ad8e-40a9-849d-3e611189c07bn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=108.52.84.50; posting-account=zTPg1AoAAABx_LtAQ3dW6FBnU1dwmSvl
NNTP-Posting-Host: 108.52.84.50
References: <63c0af09-5427-477c-9f6b-ccae7288b41cn@googlegroups.com> <f610f3e6-ad8e-40a9-849d-3e611189c07bn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <136014a0-80cc-4c7d-8acf-30ba27c6ac6an@googlegroups.com>
Subject: Re: Many notices and warnings with compiling YottaDB 1.32 from sources
From: ksbhaskar@gmail.com (K.S. Bhaskar)
Injection-Date: Tue, 05 Oct 2021 15:30:10 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 100
 by: K.S. Bhaskar - Tue, 5 Oct 2021 15:30 UTC

On Monday, October 4, 2021 at 3:13:18 PM UTC-4, K.S. Bhaskar wrote:
> On Saturday, October 2, 2021 at 10:52:26 AM UTC-4, suka...@gmail.com wrote:
> > Hi!
> > Is that how it should be? Is this normal or am I doing something wrong?
> > gcc 10.3.0
> >
> > ...
> > [ 89%] Building C object CMakeFiles/libyottadb.dir/sr_unix/ftok_main.c.o
> > [ 89%] Linking C shared module libyottadb.so
> > /tmp/tmp/YDB/sr_port/gdsfhead.h:1101:21: warning: type of ‘pin_fail_bt’ does not match original declaration [-Wlto-type-mismatch]
> > 1101 | GBLREF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> > | ^
> > /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: ‘pin_fail_bt’ was previously declared here
> > 891 | GBLDEF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> > | ^
> > /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > /tmp/tmp/YDB/sr_port/gdsfhead.h:1102:16: warning: type of ‘pin_fail_bt_contents’ does not match original declaration [-Wlto-type-mismatch]
> > 1102 | GBLREF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> > | ^
> > /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: ‘pin_fail_bt_contents’ was previously declared here
> > 892 | GBLDEF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> > | ^
> > /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > /tmp/tmp/YDB/sr_port/dm_setup.c:20:18: warning: type of ‘gtm_err_dev’ does not match original declaration [-Wlto-type-mismatch]
> > 20 | GBLREF io_desc *gtm_err_dev;
> > | ^
> > /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: ‘gtm_err_dev’ was previously declared here
> > 412 | GBLDEF io_desc *gtm_err_dev;
> > | ^
> > /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > /tmp/tmp/YDB/sr_port/m_zwrite.c:47:25: warning: type of ‘svn_data’ does not match original declaration [-Wlto-type-mismatch]
> > 47 | LITREF svn_data_type svn_data[];
> > | ^
> > /tmp/tmp/YDB/sr_port/expritem.c:147:22: note: ‘svn_data’ was previously declared here
> > 147 | LITDEF svn_data_type svn_data[] =
> > | ^
> > /tmp/tmp/YDB/sr_port/op_close.c:27:18: warning: type of ‘active_device’ does not match original declaration [-Wlto-type-mismatch]
> > 27 | GBLREF io_desc *active_device;
> > | ^
> > /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: ‘active_device’ was previously declared here
> > 161 | GBLDEF io_desc *active_device;
> > | ^
> > /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > [ 89%] Built target libyottadb
> > Scanning dependencies of target dse
> > Scanning dependencies of target gtcm_pkdisp
> > Scanning dependencies of target yottadb
> > Scanning dependencies of target dbcertify
> > Scanning dependencies of target lke
> > Scanning dependencies of target mupip
> > Scanning dependencies of target gtmsecshr_real
> > [ 89%] Building C object CMakeFiles/dse.dir/sr_unix/dse.c.o
> > [ 89%] Building C object CMakeFiles/semstat2.dir/sr_unix/semstat2.c.o
> > [ 89%] Building C object CMakeFiles/gtcm_pkdisp.dir/sr_unix_cm/gtcm_pkdisp.c.o
> > ...
> Are you following the instructions in the README, or are you trying to compile it yourself with your own gcc flags? gcc flags do matter. Also, which Linux distribution/version are you using? Thank you.
>
> Regards
> – Bhaskar

Thank you for reporting this. For some reason, the great G is not showing your later post that you are compiling on Gentoo.

I just tried building r1.32 on Debian 11, one of the Supported platforms with gcc version 10.2.1 and it compiled without any warnings. There are many Linux distributions, many versions of gcc, and a plethora of compilation flags that control warnings. As newer versions of gcc generate more warnings, part of our development activity is to check those warnings, determine which are legitimate (and should be addressed) vs. those which are “check this out” (and should be suppressed with flags).

Regards
– Bhaskar

Re: Many notices and warnings with compiling YottaDB 1.32 from sources

<2d9471cc-8da7-419d-aec5-1f80d922c877n@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=180&group=comp.lang.mumps#180

  copy link   Newsgroups: comp.lang.mumps
X-Received: by 2002:ac8:4312:: with SMTP id z18mr24821087qtm.208.1633514663406;
Wed, 06 Oct 2021 03:04:23 -0700 (PDT)
X-Received: by 2002:a05:6214:1705:: with SMTP id db5mr3044087qvb.51.1633514663187;
Wed, 06 Oct 2021 03:04:23 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.mumps
Date: Wed, 6 Oct 2021 03:04:22 -0700 (PDT)
In-Reply-To: <136014a0-80cc-4c7d-8acf-30ba27c6ac6an@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=193.107.193.43; posting-account=eaShnQoAAABLy95ZTEb7H0YHkVXcD4qO
NNTP-Posting-Host: 193.107.193.43
References: <63c0af09-5427-477c-9f6b-ccae7288b41cn@googlegroups.com>
<f610f3e6-ad8e-40a9-849d-3e611189c07bn@googlegroups.com> <136014a0-80cc-4c7d-8acf-30ba27c6ac6an@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <2d9471cc-8da7-419d-aec5-1f80d922c877n@googlegroups.com>
Subject: Re: Many notices and warnings with compiling YottaDB 1.32 from sources
From: sukamenev@gmail.com (Сергей Каменев)
Injection-Date: Wed, 06 Oct 2021 10:04:23 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 109
 by: Сергей Кам - Wed, 6 Oct 2021 10:04 UTC

I incorrectly sent the answer to the mailing list from another email, so you did not see it.

Yes I followed instructions for gcc from README.
I'm using Calculate Linux Desktop (Gentoo based distro).
Kernel 5.10.32

As far as I remember, when compiling with an early version gcc 10.2.? (may be 10.2.1), there were also problems.

Sergey.

> > > Hi!
> > > Is that how it should be? Is this normal or am I doing something wrong?
> > > gcc 10.3.0
> > >
> > > ...
> > > [ 89%] Building C object CMakeFiles/libyottadb.dir/sr_unix/ftok_main.c.o
> > > [ 89%] Linking C shared module libyottadb.so
> > > /tmp/tmp/YDB/sr_port/gdsfhead.h:1101:21: warning: type of ‘pin_fail_bt’ does not match original declaration [-Wlto-type-mismatch]
> > > 1101 | GBLREF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> > > | ^
> > > /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: ‘pin_fail_bt’ was previously declared here
> > > 891 | GBLDEF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> > > | ^
> > > /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > /tmp/tmp/YDB/sr_port/gdsfhead.h:1102:16: warning: type of ‘pin_fail_bt_contents’ does not match original declaration [-Wlto-type-mismatch]
> > > 1102 | GBLREF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> > > | ^
> > > /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: ‘pin_fail_bt_contents’ was previously declared here
> > > 892 | GBLDEF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> > > | ^
> > > /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > /tmp/tmp/YDB/sr_port/dm_setup.c:20:18: warning: type of ‘gtm_err_dev’ does not match original declaration [-Wlto-type-mismatch]
> > > 20 | GBLREF io_desc *gtm_err_dev;
> > > | ^
> > > /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: ‘gtm_err_dev’ was previously declared here
> > > 412 | GBLDEF io_desc *gtm_err_dev;
> > > | ^
> > > /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > /tmp/tmp/YDB/sr_port/m_zwrite.c:47:25: warning: type of ‘svn_data’ does not match original declaration [-Wlto-type-mismatch]
> > > 47 | LITREF svn_data_type svn_data[];
> > > | ^
> > > /tmp/tmp/YDB/sr_port/expritem.c:147:22: note: ‘svn_data’ was previously declared here
> > > 147 | LITDEF svn_data_type svn_data[] =
> > > | ^
> > > /tmp/tmp/YDB/sr_port/op_close.c:27:18: warning: type of ‘active_device’ does not match original declaration [-Wlto-type-mismatch]
> > > 27 | GBLREF io_desc *active_device;
> > > | ^
> > > /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: ‘active_device’ was previously declared here
> > > 161 | GBLDEF io_desc *active_device;
> > > | ^
> > > /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > [ 89%] Built target libyottadb
> > > Scanning dependencies of target dse
> > > Scanning dependencies of target gtcm_pkdisp
> > > Scanning dependencies of target yottadb
> > > Scanning dependencies of target dbcertify
> > > Scanning dependencies of target lke
> > > Scanning dependencies of target mupip
> > > Scanning dependencies of target gtmsecshr_real
> > > [ 89%] Building C object CMakeFiles/dse.dir/sr_unix/dse.c.o
> > > [ 89%] Building C object CMakeFiles/semstat2.dir/sr_unix/semstat2.c.o
> > > [ 89%] Building C object CMakeFiles/gtcm_pkdisp.dir/sr_unix_cm/gtcm_pkdisp.c.o
> > > ...
> > Are you following the instructions in the README, or are you trying to compile it yourself with your own gcc flags? gcc flags do matter. Also, which Linux distribution/version are you using? Thank you.
> >
> > Regards
> > – Bhaskar
> Thank you for reporting this. For some reason, the great G is not showing your later post that you are compiling on Gentoo.
>
> I just tried building r1.32 on Debian 11, one of the Supported platforms with gcc version 10.2.1 and it compiled without any warnings. There are many Linux distributions, many versions of gcc, and a plethora of compilation flags that control warnings. As newer versions of gcc generate more warnings, part of our development activity is to check those warnings, determine which are legitimate (and should be addressed) vs. those which are “check this out” (and should be suppressed with flags).
>
> Regards
> – Bhaskar

Re: Many notices and warnings with compiling YottaDB 1.32 from sources

<7ef0408a-e09b-4d8f-a416-3f12c7e50fd2n@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=181&group=comp.lang.mumps#181

  copy link   Newsgroups: comp.lang.mumps
X-Received: by 2002:a37:bd7:: with SMTP id 206mr2157925qkl.297.1633628086136;
Thu, 07 Oct 2021 10:34:46 -0700 (PDT)
X-Received: by 2002:ac8:4588:: with SMTP id l8mr6330331qtn.207.1633628085806;
Thu, 07 Oct 2021 10:34:45 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.mumps
Date: Thu, 7 Oct 2021 10:34:45 -0700 (PDT)
In-Reply-To: <2d9471cc-8da7-419d-aec5-1f80d922c877n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=46.39.45.29; posting-account=1pvfEQoAAABUWQwCLA_Z1nQSdt2-s6sR
NNTP-Posting-Host: 46.39.45.29
References: <63c0af09-5427-477c-9f6b-ccae7288b41cn@googlegroups.com>
<f610f3e6-ad8e-40a9-849d-3e611189c07bn@googlegroups.com> <136014a0-80cc-4c7d-8acf-30ba27c6ac6an@googlegroups.com>
<2d9471cc-8da7-419d-aec5-1f80d922c877n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <7ef0408a-e09b-4d8f-a416-3f12c7e50fd2n@googlegroups.com>
Subject: Re: Many notices and warnings with compiling YottaDB 1.32 from sources
From: google15@inetstar.ru (Сергей Каменев)
Injection-Date: Thu, 07 Oct 2021 17:34:46 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 171
 by: Сергей Кам - Thu, 7 Oct 2021 17:34 UTC

> I incorrectly sent the answer to the mailing list from another email, so you did not see it.
>
> Yes I followed instructions for gcc from README.
> I'm using Calculate Linux Desktop (Gentoo based distro).
> Kernel 5.10.32
>
> As far as I remember, when compiling with an early version gcc 10.2.? (may be 10.2.1), there were also problems.
>
> Sergey.
> > > > Hi!
> > > > Is that how it should be? Is this normal or am I doing something wrong?
> > > > gcc 10.3.0
> > > >
> > > > ...
> > > > [ 89%] Building C object CMakeFiles/libyottadb.dir/sr_unix/ftok_main.c.o
> > > > [ 89%] Linking C shared module libyottadb.so
> > > > /tmp/tmp/YDB/sr_port/gdsfhead.h:1101:21: warning: type of ‘pin_fail_bt’ does not match original declaration [-Wlto-type-mismatch]
> > > > 1101 | GBLREF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: ‘pin_fail_bt’ was previously declared here
> > > > 891 | GBLDEF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > > /tmp/tmp/YDB/sr_port/gdsfhead.h:1102:16: warning: type of ‘pin_fail_bt_contents’ does not match original declaration [-Wlto-type-mismatch]
> > > > 1102 | GBLREF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: ‘pin_fail_bt_contents’ was previously declared here
> > > > 892 | GBLDEF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > > /tmp/tmp/YDB/sr_port/dm_setup.c:20:18: warning: type of ‘gtm_err_dev’ does not match original declaration [-Wlto-type-mismatch]
> > > > 20 | GBLREF io_desc *gtm_err_dev;
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: ‘gtm_err_dev’ was previously declared here
> > > > 412 | GBLDEF io_desc *gtm_err_dev;
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > > /tmp/tmp/YDB/sr_port/m_zwrite.c:47:25: warning: type of ‘svn_data’ does not match original declaration [-Wlto-type-mismatch]
> > > > 47 | LITREF svn_data_type svn_data[];
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/expritem.c:147:22: note: ‘svn_data’ was previously declared here
> > > > 147 | LITDEF svn_data_type svn_data[] =
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/op_close.c:27:18: warning: type of ‘active_device’ does not match original declaration [-Wlto-type-mismatch]
> > > > 27 | GBLREF io_desc *active_device;
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: ‘active_device’ was previously declared here
> > > > 161 | GBLDEF io_desc *active_device;
> > > > | ^
> > > > /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > > [ 89%] Built target libyottadb
> > > > Scanning dependencies of target dse
> > > > Scanning dependencies of target gtcm_pkdisp
> > > > Scanning dependencies of target yottadb
> > > > Scanning dependencies of target dbcertify
> > > > Scanning dependencies of target lke
> > > > Scanning dependencies of target mupip
> > > > Scanning dependencies of target gtmsecshr_real
> > > > [ 89%] Building C object CMakeFiles/dse.dir/sr_unix/dse.c.o
> > > > [ 89%] Building C object CMakeFiles/semstat2.dir/sr_unix/semstat2.c..o
> > > > [ 89%] Building C object CMakeFiles/gtcm_pkdisp.dir/sr_unix_cm/gtcm_pkdisp.c.o
> > > > ...
> > > Are you following the instructions in the README, or are you trying to compile it yourself with your own gcc flags? gcc flags do matter. Also, which Linux distribution/version are you using? Thank you.
> > >
> > > Regards
> > > – Bhaskar
> > Thank you for reporting this. For some reason, the great G is not showing your later post that you are compiling on Gentoo.
> >
> > I just tried building r1.32 on Debian 11, one of the Supported platforms with gcc version 10.2.1 and it compiled without any warnings. There are many Linux distributions, many versions of gcc, and a plethora of compilation flags that control warnings. As newer versions of gcc generate more warnings, part of our development activity is to check those warnings, determine which are legitimate (and should be addressed) vs. those which are “check this out” (and should be suppressed with flags).
> >
> > Regards
> > – Bhaskar

I tested compilation with gcc 10.2.0-r5. Same 10 warnings and notices.

[ 89%] Building C object CMakeFiles/libyottadb.dir/sr_unix/ftok_main.c.o
[ 89%] Linking C shared module libyottadb.so
/tmp/YDB/sr_port/gdsfhead.h:1101:21: warning: type of ‘pin_fail_bt’ does not match original declaration [-Wlto-type-mismatch]
1101 | GBLREF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
| ^
/tmp/YDB/sr_port/gbldefs.c:891:21: note: ‘pin_fail_bt’ was previously declared here
891 | GBLDEF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
| ^
/tmp/YDB/sr_port/gbldefs.c:891:21: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
/tmp/YDB/sr_port/gdsfhead.h:1102:16: warning: type of ‘pin_fail_bt_contents’ does not match original declaration [-Wlto-type-mismatch]
1102 | GBLREF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
| ^
/tmp/YDB/sr_port/gbldefs.c:892:16: note: ‘pin_fail_bt_contents’ was previously declared here
892 | GBLDEF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
| ^
/tmp/YDB/sr_port/gbldefs.c:892:16: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
/tmp/YDB/sr_port/dm_setup.c:20:18: warning: type of ‘gtm_err_dev’ does not match original declaration [-Wlto-type-mismatch]
20 | GBLREF io_desc *gtm_err_dev;
| ^
/tmp/YDB/sr_port/gbldefs.c:412:19: note: ‘gtm_err_dev’ was previously declared here
412 | GBLDEF io_desc *gtm_err_dev;
| ^
/tmp/YDB/sr_port/gbldefs.c:412:19: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
/tmp/YDB/sr_port/m_zwrite.c:47:25: warning: type of ‘svn_data’ does not match original declaration [-Wlto-type-mismatch]
47 | LITREF svn_data_type svn_data[];
| ^
/tmp/YDB/sr_port/expritem.c:147:22: note: ‘svn_data’ was previously declared here
147 | LITDEF svn_data_type svn_data[] | ^
/tmp/YDB/sr_port/op_close.c:27:18: warning: type of ‘active_device’ does not match original declaration [-Wlto-type-mismatch]
27 | GBLREF io_desc *active_device;
| ^
/tmp/YDB/sr_port/gbldefs.c:161:18: note: ‘active_device’ was previously declared here
161 | GBLDEF io_desc *active_device;
| ^
/tmp/YDB/sr_port/gbldefs.c:161:18: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
[ 89%] Built target libyottadb
Scanning dependencies of target dbcertify
Scanning dependencies of target dse
Scanning dependencies of target mupip

Re: Many notices and warnings with compiling YottaDB 1.32 from sources

<8aa66ba8-f664-4aa7-a291-eac3bbad5ecen@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=185&group=comp.lang.mumps#185

  copy link   Newsgroups: comp.lang.mumps
X-Received: by 2002:a0c:becf:: with SMTP id f15mr17380840qvj.51.1633966422311;
Mon, 11 Oct 2021 08:33:42 -0700 (PDT)
X-Received: by 2002:a0c:f249:: with SMTP id z9mr24577085qvl.61.1633966422093;
Mon, 11 Oct 2021 08:33:42 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.mumps
Date: Mon, 11 Oct 2021 08:33:41 -0700 (PDT)
In-Reply-To: <7ef0408a-e09b-4d8f-a416-3f12c7e50fd2n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=108.52.84.50; posting-account=zTPg1AoAAABx_LtAQ3dW6FBnU1dwmSvl
NNTP-Posting-Host: 108.52.84.50
References: <63c0af09-5427-477c-9f6b-ccae7288b41cn@googlegroups.com>
<f610f3e6-ad8e-40a9-849d-3e611189c07bn@googlegroups.com> <136014a0-80cc-4c7d-8acf-30ba27c6ac6an@googlegroups.com>
<2d9471cc-8da7-419d-aec5-1f80d922c877n@googlegroups.com> <7ef0408a-e09b-4d8f-a416-3f12c7e50fd2n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <8aa66ba8-f664-4aa7-a291-eac3bbad5ecen@googlegroups.com>
Subject: Re: Many notices and warnings with compiling YottaDB 1.32 from sources
From: ksbhaskar@gmail.com (K.S. Bhaskar)
Injection-Date: Mon, 11 Oct 2021 15:33:42 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 189
 by: K.S. Bhaskar - Mon, 11 Oct 2021 15:33 UTC

On Thursday, October 7, 2021 at 1:34:46 PM UTC-4, Сергей Каменев wrote:
> > I incorrectly sent the answer to the mailing list from another email, so you did not see it.
> >
> > Yes I followed instructions for gcc from README.
> > I'm using Calculate Linux Desktop (Gentoo based distro).
> > Kernel 5.10.32
> >
> > As far as I remember, when compiling with an early version gcc 10.2.? (may be 10.2.1), there were also problems.
> >
> > Sergey.
> > > > > Hi!
> > > > > Is that how it should be? Is this normal or am I doing something wrong?
> > > > > gcc 10.3.0
> > > > >
> > > > > ...
> > > > > [ 89%] Building C object CMakeFiles/libyottadb.dir/sr_unix/ftok_main.c.o
> > > > > [ 89%] Linking C shared module libyottadb.so
> > > > > /tmp/tmp/YDB/sr_port/gdsfhead.h:1101:21: warning: type of ‘pin_fail_bt’ does not match original declaration [-Wlto-type-mismatch]
> > > > > 1101 | GBLREF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: ‘pin_fail_bt’ was previously declared here
> > > > > 891 | GBLDEF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/gbldefs.c:891:21: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > > > /tmp/tmp/YDB/sr_port/gdsfhead.h:1102:16: warning: type of ‘pin_fail_bt_contents’ does not match original declaration [-Wlto-type-mismatch]
> > > > > 1102 | GBLREF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: ‘pin_fail_bt_contents’ was previously declared here
> > > > > 892 | GBLDEF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/gbldefs.c:892:16: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > > > /tmp/tmp/YDB/sr_port/dm_setup.c:20:18: warning: type of ‘gtm_err_dev’ does not match original declaration [-Wlto-type-mismatch]
> > > > > 20 | GBLREF io_desc *gtm_err_dev;
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: ‘gtm_err_dev’ was previously declared here
> > > > > 412 | GBLDEF io_desc *gtm_err_dev;
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/gbldefs.c:412:19: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > > > /tmp/tmp/YDB/sr_port/m_zwrite.c:47:25: warning: type of ‘svn_data’ does not match original declaration [-Wlto-type-mismatch]
> > > > > 47 | LITREF svn_data_type svn_data[];
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/expritem.c:147:22: note: ‘svn_data’ was previously declared here
> > > > > 147 | LITDEF svn_data_type svn_data[] =
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/op_close.c:27:18: warning: type of ‘active_device’ does not match original declaration [-Wlto-type-mismatch]
> > > > > 27 | GBLREF io_desc *active_device;
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: ‘active_device’ was previously declared here
> > > > > 161 | GBLDEF io_desc *active_device;
> > > > > | ^
> > > > > /tmp/tmp/YDB/sr_port/gbldefs.c:161:18: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> > > > > [ 89%] Built target libyottadb
> > > > > Scanning dependencies of target dse
> > > > > Scanning dependencies of target gtcm_pkdisp
> > > > > Scanning dependencies of target yottadb
> > > > > Scanning dependencies of target dbcertify
> > > > > Scanning dependencies of target lke
> > > > > Scanning dependencies of target mupip
> > > > > Scanning dependencies of target gtmsecshr_real
> > > > > [ 89%] Building C object CMakeFiles/dse.dir/sr_unix/dse.c.o
> > > > > [ 89%] Building C object CMakeFiles/semstat2.dir/sr_unix/semstat2..c.o
> > > > > [ 89%] Building C object CMakeFiles/gtcm_pkdisp.dir/sr_unix_cm/gtcm_pkdisp.c.o
> > > > > ...
> > > > Are you following the instructions in the README, or are you trying to compile it yourself with your own gcc flags? gcc flags do matter. Also, which Linux distribution/version are you using? Thank you.
> > > >
> > > > Regards
> > > > – Bhaskar
> > > Thank you for reporting this. For some reason, the great G is not showing your later post that you are compiling on Gentoo.
> > >
> > > I just tried building r1.32 on Debian 11, one of the Supported platforms with gcc version 10.2.1 and it compiled without any warnings. There are many Linux distributions, many versions of gcc, and a plethora of compilation flags that control warnings. As newer versions of gcc generate more warnings, part of our development activity is to check those warnings, determine which are legitimate (and should be addressed) vs. those which are “check this out” (and should be suppressed with flags).
> > >
> > > Regards
> > > – Bhaskar
> I tested compilation with gcc 10.2.0-r5. Same 10 warnings and notices.
> [ 89%] Building C object CMakeFiles/libyottadb.dir/sr_unix/ftok_main.c.o
> [ 89%] Linking C shared module libyottadb.so
> /tmp/YDB/sr_port/gdsfhead.h:1101:21: warning: type of ‘pin_fail_bt’ does not match original declaration [-Wlto-type-mismatch]
> 1101 | GBLREF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> | ^
> /tmp/YDB/sr_port/gbldefs.c:891:21: note: ‘pin_fail_bt’ was previously declared here
> 891 | GBLDEF bt_rec_ptr_t pin_fail_bt; /* Pointer to bt of the cache-record that we failed to pin */
> | ^
> /tmp/YDB/sr_port/gbldefs.c:891:21: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> /tmp/YDB/sr_port/gdsfhead.h:1102:16: warning: type of ‘pin_fail_bt_contents’ does not match original declaration [-Wlto-type-mismatch]
> 1102 | GBLREF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> | ^
> /tmp/YDB/sr_port/gbldefs.c:892:16: note: ‘pin_fail_bt_contents’ was previously declared here
> 892 | GBLDEF bt_rec pin_fail_bt_contents; /* Contents of bt of the cache-record that we failed to pin */
> | ^
> /tmp/YDB/sr_port/gbldefs.c:892:16: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> /tmp/YDB/sr_port/dm_setup.c:20:18: warning: type of ‘gtm_err_dev’ does not match original declaration [-Wlto-type-mismatch]
> 20 | GBLREF io_desc *gtm_err_dev;
> | ^
> /tmp/YDB/sr_port/gbldefs.c:412:19: note: ‘gtm_err_dev’ was previously declared here
> 412 | GBLDEF io_desc *gtm_err_dev;
> | ^
> /tmp/YDB/sr_port/gbldefs.c:412:19: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> /tmp/YDB/sr_port/m_zwrite.c:47:25: warning: type of ‘svn_data’ does not match original declaration [-Wlto-type-mismatch]
> 47 | LITREF svn_data_type svn_data[];
> | ^
> /tmp/YDB/sr_port/expritem.c:147:22: note: ‘svn_data’ was previously declared here
> 147 | LITDEF svn_data_type svn_data[] =
> | ^
> /tmp/YDB/sr_port/op_close.c:27:18: warning: type of ‘active_device’ does not match original declaration [-Wlto-type-mismatch]
> 27 | GBLREF io_desc *active_device;
> | ^
> /tmp/YDB/sr_port/gbldefs.c:161:18: note: ‘active_device’ was previously declared here
> 161 | GBLDEF io_desc *active_device;
> | ^
> /tmp/YDB/sr_port/gbldefs.c:161:18: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
> [ 89%] Built target libyottadb
> Scanning dependencies of target dbcertify
> Scanning dependencies of target dse
> Scanning dependencies of target mupip

Different versions of compilers or even the same version of a compiler on different Linux distributions may generate different warnings for the same code. In some cases the warnings are correct and we take remedial action, and in some cases the warnings are not because there are reasons for the code being the way it is, and we have to add compiler flags to turn off a specific warning (and in some cases, if the flag is not available in an earlier version of a compiler, we may opt to not add the flag). This is an ongoing process that never stops.

What I would ask is that when you see a warning, please do investigate whether it appears legitimate. If it does, please submit a merge request on GitLab with a fix, and if it does not and there is a compiler flag to turn if off, please submit a merge request with the updated flag. Thank you.


Click here to read the complete article
1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor