Bug 196616 - allegro-devel missing alld and allp libs
Summary: allegro-devel missing alld and allp libs
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: allegro
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-26 01:02 UTC by Need Real Name
Modified: 2013-07-02 23:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-06-26 11:25:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2006-06-26 01:02:27 UTC
Description of problem:

The allegro-devel component only includes the allegro "release" libs to link
against.  The "debug" and "profile" libs are not present.  Is it possible to add
the debug and profile libs to the allgro-devel component?

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

4.2.0-12.fc5.i386

How reproducible:

every time

Steps to Reproduce:
1. This fails => g++ -o foo foo.o `allegro-config --libs debug`
/usr/bin/ld: cannot find -lalld-4.2.0

2. This fails => g++ -o foo foo.o `allegro-config --libs profile`
/usr/bin/ld: cannot find -lallp-4.2.0

3. This works => g++ -o foo foo.o `allegro-config --libs release`
  
Actual results:


Expected results:


Additional info:

Comment 1 Jindrich Novy 2006-06-26 11:25:18 UTC
Ok, debug and profiling libraries are now added to allegro-devel subpackage. Thanks.

Comment 2 Hans de Goede 2006-06-26 12:33:09 UTC
Hmm,

Strange I didn't get added to the CC-list for this even though I'm in the
initial CC list in owners.list . 

Jindirch, any clues, or shall I discuss this on f-e-l?




Comment 3 Jindrich Novy 2006-06-26 12:36:34 UTC
Hans, it happened about year ago when some bugzilla tweaks were done, I don't
know anything about this one.

Comment 4 Need Real Name 2006-06-27 23:48:02 UTC
Wow!  Thanks for the quick response.


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