Bug 440798 - FTBFS unixODBC-2.2.12-6.fc9
Summary: FTBFS unixODBC-2.2.12-6.fc9
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: unixODBC
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Tom Lane
QA Contact: Fedora Extras Quality Assurance
URL: http://linux.dell.com/files/fedora/Fi...
Whiteboard:
Depends On:
Blocks: FTBFS
TreeView+ depends on / blocked
 
Reported: 2008-04-04 16:00 UTC by FTBFS
Modified: 2013-07-03 03:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-04 17:35:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
root.log.bz2 (3.42 KB, application/x-bzip2)
2008-04-04 16:00 UTC, FTBFS
no flags Details
build.log.bz2 (1.28 KB, application/x-bzip2)
2008-04-04 16:00 UTC, FTBFS
no flags Details
root.log.bz2 (3.42 KB, application/x-bzip2)
2008-04-04 16:00 UTC, FTBFS
no flags Details
build.log.bz2 (1.27 KB, application/x-bzip2)
2008-04-04 16:00 UTC, FTBFS
no flags Details

Description FTBFS 2008-04-04 16:00:46 UTC
unixODBC-2.2.12-6.fc9.src.rpm Failed To Build From Source

Comment 1 FTBFS 2008-04-04 16:00:50 UTC
Created attachment 300772 [details]
root.log.bz2

root.log for i386

Comment 2 FTBFS 2008-04-04 16:00:51 UTC
Created attachment 300773 [details]
build.log.bz2

build.log for i386

Comment 3 FTBFS 2008-04-04 16:00:53 UTC
Created attachment 300774 [details]
root.log.bz2

root.log for x86_64

Comment 4 FTBFS 2008-04-04 16:00:54 UTC
Created attachment 300775 [details]
build.log.bz2

build.log for x86_64

Comment 5 Tom Lane 2008-04-04 16:35:08 UTC
Hey Kevin, this seems to be a consequence of qt having been changed from qt3 to qt4 in rawhide.  Can 
you give me some advice what to do about it?  The immediate problem is that /etc/profile.d/qt.sh has 
disappeared, but I wonder how many other incompatibilities might exist between 3 and 4.

Comment 6 Kevin Kofler 2008-04-04 16:37:18 UTC
Just BR qt3-devel instead of qt-devel.

Comment 7 Tom Lane 2008-04-04 16:38:25 UTC
Okay, thanks.


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