Bug 185465 - synce-devel puts headers in wrong directory
Summary: synce-devel puts headers in wrong directory
Keywords:
Status: CLOSED DUPLICATE of bug 171011
Alias: None
Product: Fedora
Classification: Fedora
Component: synce
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-14 22:49 UTC by Kristo Kriechbaum
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-15 08:53:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kristo Kriechbaum 2006-03-14 22:49:29 UTC
Description of problem:

The synce-devel package installs the headers directly into /usr/include, as
opposed to /usr/include/rra.  This causes problems when trying to install
synce-kde (which provides kde integration with synce) because synce-kde expects
certain header files (syncmgr.h for example) to be in /usr/include/rra.

Version-Release number of selected component (if applicable):
synce-devel-0.9.1-5.fc4

How reproducible:
Always

Steps to Reproduce:
1. Install synce-devel package
2. download synce-kde-0.9.1.tar.gz from
http://sourceforge.net/project/showfiles.php?group_id=30550
3. Unzip and run ./configure

Actual results:
Observe error message about syncmgr.h:
  configure: error: Can't find rra/syncmgr.h
  
Expected results:
rra/syncmgr.h is found.

Additional info:
A developer for synce said that placing all of the synce headers in /usr/include
could cause problems.  For example he said that synce has a timezone.h, but
other things like kde also have a timezone.h.  That is why the synce headers
need to be in /usr/include/rra

Comment 1 Andreas Bierfert 2006-03-15 08:53:05 UTC
I have synce-kde in the pipe if you want I can put it up for review... other
then that see #171011

*** This bug has been marked as a duplicate of 171011 ***


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