Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1060766 - piklab does not detect SDCC presence
Summary: piklab does not detect SDCC presence
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: piklab
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alain Portal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-03 14:41 UTC by Neil Darlow
Modified: 2014-02-05 09:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 09:00:15 UTC


Attachments (Terms of Use)

Description Neil Darlow 2014-02-03 14:41:34 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Neil Darlow 2014-02-03 14:46:33 UTC
Bummer. Tried to close list of suggested applicable bugs and it saved this one!

Anyhow:

The fedora SDCC package installs binaries with a "sdcc-" prefix which breaks piklab's detection mechanism (it does sdcc -v).

You can workaround this by symlinking /usr/bin/sdcc-sdcc to /usr/bin/sdcc but that is not a viable packaging solution.

piklab needs patching to that it adds the sdcc- prefix after of any user-specified program path.

Comment 2 Alain Portal 2014-02-05 09:00:15 UTC
Please, read the README.fedora file in sdcc:
"Many of the executables in SDCC have very generic names. Therefore the binaries
are installed into $PREFIX/libexec/sdcc/, and symlinks with prefix sdcc- are
created in $PREFIX/bin. If this is a problem for you, you can add
$PREFIX/libexec/sdcc/ to you path."


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