GNU bug report logs -
#36150
ERROR: testsuite/inplace-selinux.sh
Previous Next
Reported by: Vineet Jain <vkjain <at> gmail.com>
Date: Sun, 9 Jun 2019 15:30:05 UTC
Severity: normal
Tags: moreinfo
Done: Jim Meyering <jim <at> meyering.net>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36150 in the body.
You can then email your comments to 36150 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-sed <at> gnu.org
:
bug#36150
; Package
sed
.
(Sun, 09 Jun 2019 15:30:05 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Vineet Jain <vkjain <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-sed <at> gnu.org
.
(Sun, 09 Jun 2019 15:30:05 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello
I was building sed from scratch. While running the tests I had this single
failure for testsuite/inplace-selinux.sh
It looks like following was the reason for error.
inplace-selinux.sh: set-up failure: CONFIG_HEADER not defined
Do let me know if you need any more information.
Regards
--
Vineet
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-sed <at> gnu.org
:
bug#36150
; Package
sed
.
(Sat, 29 Jun 2019 08:38:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 36150 <at> debbugs.gnu.org (full text, mbox):
tag 36150 moreinfo
stop
Hello,
On Sun, Jun 09, 2019 at 03:37:31PM +0530, Vineet Jain wrote:
> I was building sed from scratch. While running the tests I had this single
> failure for testsuite/inplace-selinux.sh
> It looks like following was the reason for error.
> inplace-selinux.sh: set-up failure: CONFIG_HEADER not defined
>
> Do let me know if you need any more information.
>
Thanks for the report.
Yes - more information is needed.
This error comes from 'init.cfg' in the 'require_selinux_' function.
It happens when the system supports SELinux (based on
/proc/filesystems), but during the './configure' step, somehow
the generated Makefile did not contain a 'CONFIG_HEADER = config.h'
statement (very strange).
Could you provide the exact commands you've used to build 'sed' ?
Also, are you building sed from latest 'git' repository or from
a released tarball ?
And, if possible, please attach the following files (but compress them
before attaching them):
config.log
config.status
config.h
Makefile
regards,
- assaf
Added tag(s) moreinfo.
Request was from
Assaf Gordon <assafgordon <at> gmail.com>
to
control <at> debbugs.gnu.org
.
(Sat, 29 Jun 2019 08:38:05 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-sed <at> gnu.org
:
bug#36150
; Package
sed
.
(Sun, 08 Dec 2019 02:42:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 36150 <at> debbugs.gnu.org (full text, mbox):
Hello,
Assaf Gordon <assafgordon <at> gmail.com> writes:
> On Sun, Jun 09, 2019 at 03:37:31PM +0530, Vineet Jain wrote:
>> I was building sed from scratch. While running the tests I had this single
>> failure for testsuite/inplace-selinux.sh
>> It looks like following was the reason for error.
>> inplace-selinux.sh: set-up failure: CONFIG_HEADER not defined
>>
>> Do let me know if you need any more information.
>>
>
> Thanks for the report.
>
> Yes - more information is needed.
>
> This error comes from 'init.cfg' in the 'require_selinux_' function.
> It happens when the system supports SELinux (based on
> /proc/filesystems), but during the './configure' step, somehow
> the generated Makefile did not contain a 'CONFIG_HEADER = config.h'
> statement (very strange).
I ran into this bug when building Sed via GNU Guix running on top of
Fedora 31. This means I was building Sed version 4.7 from the release
tarball.
The generated Makefile did set “CONFIG_HEADER”. However, I noticed that
“CONFIG_HEADER” was absent from the list of variables propagated into
the test environment (see the “TEST_ENVIRONMENT” variable in
“testsuite/local.mk”). Adding it there allowed the test to be skipped
rather than causing a hard error.
Hope that helps! Let me know if you need more information or anything,
as I should be able to reproduce this error easily.
-- Tim
Information forwarded
to
bug-sed <at> gnu.org
:
bug#36150
; Package
sed
.
(Sat, 30 May 2020 08:05:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 36150 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Timothy Sample <samplet <at> ngyro.com> writes:
> I ran into this bug when building Sed via GNU Guix running on top of
> Fedora 31. This means I was building Sed version 4.7 from the release
> tarball.
Me, too! I reported it here:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41498
> The generated Makefile did set “CONFIG_HEADER”. However, I noticed that
> “CONFIG_HEADER” was absent from the list of variables propagated into
> the test environment (see the “TEST_ENVIRONMENT” variable in
> “testsuite/local.mk”). Adding it there allowed the test to be skipped
> rather than causing a hard error.
Yes, this fixes the issue for me, too. I have attached a patch.
Assaf, how does this look?
--
Chris
[0001-tests-Export-CONFIG_HEADER-to-test-scripts.patch (text/x-patch, attachment)]
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-sed <at> gnu.org
:
bug#36150
; Package
sed
.
(Sat, 13 Feb 2021 18:13:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 36150 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Sun, Jun 09 2019, Vineet Jain wrote:
> I was building sed from scratch. While running the tests I had this single
> failure for testsuite/inplace-selinux.sh
> It looks like following was the reason for error.
> inplace-selinux.sh: set-up failure: CONFIG_HEADER not defined
I just ran into the same issue when building with Guix.
============================================================================
Testsuite summary for GNU sed 4.8
============================================================================
# TOTAL: 67
# PASS: 57
# SKIP: 9
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 1
============================================================================
See ./test-suite.log
Please report to bug-sed <at> gnu.org
============================================================================
make[4]: *** [Makefile:3221: test-suite.log] Error 1
make[4]: Leaving directory '/tmp/guix-build-sed-4.8.drv-0/sed-4.8'
make[3]: *** [Makefile:3329: check-TESTS] Error 2
make[3]: Leaving directory '/tmp/guix-build-sed-4.8.drv-0/sed-4.8'
make[2]: *** [Makefile:3576: check-am] Error 2
make[2]: Leaving directory '/tmp/guix-build-sed-4.8.drv-0/sed-4.8'
make[1]: *** [Makefile:3106: check-recursive] Error 1
make[1]: Leaving directory '/tmp/guix-build-sed-4.8.drv-0/sed-4.8'
make: *** [Makefile:3578: check] Error 2
Test suite failed, dumping logs.
--- ./test-suite.log --------------------------------------------------------
I have attached some files below
- Makefile
- config.h
- config.log
- config.status
--
Xinglu Chen
[Makefile.gz (application/octet-stream, attachment)]
[config.h.gz (application/octet-stream, attachment)]
[config.log.gz (application/octet-stream, attachment)]
[config.status.gz (application/octet-stream, attachment)]
Information forwarded
to
bug-sed <at> gnu.org
:
bug#36150
; Package
sed
.
(Tue, 10 Aug 2021 14:29:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 36150 <at> debbugs.gnu.org (full text, mbox):
This bug is still there after two years...
Is it possible to fix it in the next sed release?
--
Xi Ruoyao <xry111 <at> mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
Reply sent
to
Jim Meyering <jim <at> meyering.net>
:
You have taken responsibility.
(Sun, 13 Feb 2022 19:14:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Vineet Jain <vkjain <at> gmail.com>
:
bug acknowledged by developer.
(Sun, 13 Feb 2022 19:14:02 GMT)
Full text and
rfc822 format available.
Message #27 received at 36150-done <at> debbugs.gnu.org (full text, mbox):
On Sat, Feb 12, 2022 at 7:34 PM Timothy Sample <samplet <at> ngyro.com> wrote:
> > ERROR: testsuite/inplace-selinux
> > ================================
> >
> > inplace-selinux.sh: set-up failure: CONFIG_HEADER not defined
> > ERROR testsuite/inplace-selinux.sh (exit status: 99)
>
> This looks just like <https://bugs.gnu.org/36150>. There’s a patch, but
> no word from maintainers yet. If you’re still having trouble (I know
> it’s been awhile), you could give that patch a try.
Yikes. That patch was from May of 2020, and looks fine.
I've just pushed it. Sorry for the delay.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 14 Mar 2022 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 362 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.