Bug 1317553 - Unexpected parsing errors on ppc64
Summary: Unexpected parsing errors on ppc64
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: swig
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-14 14:21 UTC by Miloslav Trmač
Modified: 2017-08-08 13:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 13:07:34 UTC
Type: Bug


Attachments (Terms of Use)

Description Miloslav Trmač 2016-03-14 14:21:08 UTC
Description of problem:
Per http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=3213812 , building m2crypto-0.23.0-1 fails:
> swig -python -D__ppc64le__ -I/usr/include/python2.7 -I/usr/include -I/usr/include/openssl -includeall -modern -builtin -outdir build/lib.linux-ppc64le-2.7/M2Crypto -o SWIG/_m2crypto_wrap.c SWIG/_m2crypto.i
> /usr/include/sys/cdefs.h:150: Warning 305: Bad constant value (ignored).
> /usr/include/bits/byteswap.h:43: Error: Syntax error in input(1).
> error: command 'swig' failed with exit status 1
> error: Bad exit status from /var/tmp/rpm-tmp.3aeOFp (%build)

Version-Release number of selected component (if applicable):
glibc-2.22.90-33.fc24.ppc64
swig-3.0.8-2.fc24.ppc64
and the same for .ppc64le

Additional info:

Note: Do not test with m2crypto-0.23.0-2, which  contains a workaround.

The relevant lines are:
sys/cdefs.h:150:
> # define __flexarr      []

bits/byteswap.h:43
> static __inline unsigned int

Both of these lines exist in earlier versions, like F22. A build on x86_64 (glibc-2.23.90-4.fc25.x86_64, swig-3.0.8-6.fc25.x86_64) also finishes fine.

So, this seems specific to ppc64, though at a first glance it is not obvious to me whether this is a bug in swig or something ppc64-specific elsewhere in the header files.a

Comment 1 Fedora End Of Life 2017-07-25 20:19:33 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 2017-08-08 13:07:34 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.