By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1171

Summary:	Build issue: k9copy FTBFS without HAL
Product:	TDE	Reporter:	Darrell <darrella>
Component:	non-core programs	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	major	CC:	bugwatch, darrella, kb9vqf
Priority:	P1
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Other
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Darrell 2012-08-15 13:41:26 CDT

The error:

configure: error: libhal may be missing

Newer versions of k9copy for KDE4 appears to have a --disable-hal configure option. According to the k9copy 2.3.7 change log, udisks may be used in place of HAL, which implies some kind of hardware detection is still required.

Possibly those 2.3.7 code snippets can be ported to the TDE version of k9copy, but the TDE version should also look for the built-in TDE hardware libs support.

Notice that k9copy is no longer supported or maintained upstream:

http://k9copy.sourceforge.net/web/index.php/en/news

Comment 1 Darrell 2012-08-26 15:31:58 CDT

Seems there is a work-around that is not immediately obvious. Use the --enable-k3bdevices configure option to build without HAL support.

Using that option I built k9copy without HAL being installed.

I have not yet performed any usability testing.

Because there is a work-around I'm bumping to Major.

Because k9copy probably should be patched to work with TDEHWLIB, I'm leaving this bug report open.

Comment 2 Darrell 2013-04-04 16:23:48 CDT

Is this bug report resolved by commit 5f815c54, 2013-03-31?

Comment 3 Timothy Pearson 2013-04-04 16:41:57 CDT

Yes, this bug report is resolved; kcopy now compiles without HAL.

Comment 4 Darrell 2013-04-10 16:31:48 CDT

I just tried building and received the same build failure.

I remain unable to build k9copy unless I use the --enable-k3bdevices configure option. Is --enable-k3bdevices still required despite the recent patching to use tdehardware libs?

Comment 5 Timothy Pearson 2013-04-10 16:35:05 CDT

(In reply to comment #4)
> I just tried building and received the same build failure.
> 
> I remain unable to build k9copy unless I use the --enable-k3bdevices configure
> option. Is --enable-k3bdevices still required despite the recent patching to
> use tdehardware libs?

Actually, this software package does not use the TDE hardware library, as I don't see any reason to do so when the k3bdevices support works perfectly fine.  The only thing that might be useful is to automatically set enable-k3bdevices if HAL is not found.

Comment 6 Darrell 2013-04-10 16:47:42 CDT

Okay. What then was commit 5f815c54 all about?

Comment 7 Timothy Pearson 2013-04-10 16:50:39 CDT

(In reply to comment #6)
> Okay. What then was commit 5f815c54 all about?

Fixing compilation when --enable-k3bdevices was passed. :-)

As an aside, technically k9copy *does* use the TDE hardware library when --enable-k3bdevices is used, it just uses libk3bdevices as a proxy to it.  k9copy is complex enough that making it directly access the TDE hardware library would be an irritating chore.