Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1183956 - Don't include config.h in regress.c
Summary: Don't include config.h in regress.c
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gobject-introspection
Version: 21
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2015-01-20 09:38 UTC by Jakub Čajka
Modified: 2015-12-02 17:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 07:40:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jakub Čajka 2015-01-20 09:38:55 UTC
Hello, 

looking in to lua-lgi I have encountered some problems. Its tests fail to compile with latest version(1.42.0) of gobject-introspection. It is caused by inclusion of config.h in regress.c


.
.
.
make[1]: Entering directory '/builddir/build/BUILD/lgi-0.8.0/tests'
pkg-config --exists 'gio-2.0 cairo cairo-gobject gobject-introspection-1.0 gmodule-2.0 libffi >= 0.10.8' --print-errors
touch .depcheck
cc -fPIC   -pthread -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/libpng16 -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include  -Wall -g -c -o regress.o /usr/share/gobject-introspection-1.0/tests/regress.c
/usr/share/gobject-introspection-1.0/tests/regress.c:2:20: fatal error: config.h: No such file or directory
 #include "config.h"
                    ^
compilation terminated.
.
.
.


This bug is fixed by upstream commit 
https://git.gnome.org/browse/gobject-introspection/commit/tests/scanner/regress.c?id=578eebd54bd9f2b1677922680701c454f489c895

Could you please include this patch.


Thanks,
Jakub

Comment 1 Fedora End Of Life 2015-11-04 13:57:02 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-12-02 07:40:16 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.