Bug 241284 - libtasn fails to build on ppc64
Summary: libtasn fails to build on ppc64
Alias: None
Product: Fedora
Classification: Fedora
Component: libtasn1
Version: rawhide
Hardware: ppc64
OS: Linux
Target Milestone: ---
Assignee: Enrico Scholz
QA Contact: Fedora Extras Quality Assurance
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-24 20:28 UTC by Ruben Kerkhof
Modified: 2008-04-05 12:54 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2008-04-05 12:54:46 UTC

Attachments (Terms of Use)

Description Ruben Kerkhof 2007-05-24 20:28:47 UTC
Description of problem:
libtasn fails to build on ppc64
libtasn-devel is a dependency of my package csync2

Version-Release number of selected component (if applicable):


Additional info:
Buildlogs are here:

Mailing list thread: https://www.redhat.com/archives/fedora-maintainers/2007-May/msg00935.html

Comment 1 David Woodhouse 2007-05-31 18:50:25 UTC
--12346-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting

Is there a valgrind bug filed? Is it reported to valgrind upstream?

Comment 2 Bug Zapper 2008-04-04 00:53:59 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 3 Ruben Kerkhof 2008-04-05 12:54:46 UTC
Package seems to build fine now.

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