[Fedora-haskell-list] [Bug 580480] Review Request: ghc-type-level - A type-level library for Haskell
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=580480
Shakthi Kannan <shakthimaan(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fedora-haskell-list@redhat.
| |com
--- Comment #1 from Shakthi Kannan <shakthimaan(a)gmail.com> 2010-04-08 07:34:08 EDT
---
$ rpmlint -iv ghc-type-level.spec ../SRPMS/ghc-type-level-0.2.4-1.fc12.src.rpm
../RPMS/i686/ghc-type-level-*
ghc-type-level.src: I: checking
ghc-type-level.i686: I: checking
ghc-type-level.i686: W: unstripped-binary-or-object
/usr/lib/ghc-6.12.1/type-level-0.2.4/libHStype-level-0.2.4-ghc6.12.1.so
ghc-type-level.i686: W: executable-stack
/usr/lib/ghc-6.12.1/type-level-0.2.4/libHStype-level-0.2.4-ghc6.12.1.so
The binary declares the stack as executable. Executable stack is usually an
error as it is only needed if the code contains GCC trampolines or similar
constructs which uses code on the stack. One common source for needlessly
executable stack cases are object files built from assembler files which don't
define a proper .note.GNU-stack section.
ghc-type-level-devel.i686: I: checking
ghc-type-level-devel.i686: W: no-documentation
The package contains no documentation (README, doc, etc). You have to include
documentation files.
ghc-type-level-doc.i686: I: checking
ghc-type-level-prof.i686: I: checking
ghc-type-level-prof.i686: E: devel-dependency ghc-type-level-devel
Your package has a dependency on a devel package but it's not a devel package
itself.
ghc-type-level-prof.i686: W: no-documentation
The package contains no documentation (README, doc, etc). You have to include
documentation files.
ghc-type-level-prof.i686: W: devel-file-in-non-devel-package
/usr/lib/ghc-6.12.1/type-level-0.2.4/libHStype-level-0.2.4_p.a
A development file (usually source code) is located in a non-devel package. If
you want to include source code in your package, be sure to create a
development package.
5 packages and 1 specfiles checked; 1 errors, 5 warnings.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.