[sane-devel] Compiling sane-backends on FC8 64bit

[Chris]

Success!

As I thought, it was picking up /usr/lib/libieee1284.so instead of 
/usr/lib64/libieee1284.so

I had to do some dirty-hacks of the library paths to make it compile 
sane-backends (I guess these should be picked up properly by the 
configure script?), but sane now detects my scanner and it seems to work 
properly.

Here's what I had to do to successfully compile the 64bit sane-backends 
on f8:

1) Installed libieee1284-devel x86_64
2) Symlinked usr/lib64/libusb.so -> /usr/lib64/libusb-0.1.so.4.4.4
3) ./configure
4) Edited the various sane-backends Makefile(s) and changed the 
BACKENDLIBS to use a hard-coded "/usr/lib64/libieee1284.so" instead of 
-lieee1284
5) make

Maybe this will help someone else. If there is anything amiss here that 
should be passed on to the fedora development team then please let me know.

Thanks to all
Chris

Chris wrote:
> Thank you Mattias - we're getting somewhere now. Still got problems though:
>
> I installed libieee1284-devel x86_64 and then noticed that config.log 
> was showing it couldn't find "libusb.so" so I have symlinked 
> /usr/lib64/libusb.so -> /usr/lib64/libusb-0.1.so.4.4.4 and that error is 
> now gone. I trust this was the correct thing to do?
>
> It now fails later on:
>
> /usr/lib/libieee1284.so: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
> make[1]: *** [libsane-hp3900.la] Error 1
> make[1]: Leaving directory 
> `/home/cnolan/Download/sane-backends-1.0.18/backend'
> make: *** [all-recursive] Error 1
>
> I've seen an error like this before, and I am *guessing* that it is now 
> looking in /usr/lib/ when it should be using files from /usr/lib64/ - 
> does this sound correct?
>
> For completeness, the latest config.log is here: http://dpaste.com/31215/
>
> Any ideas?
>
> Mattias Ellert wrote:
>   
>> ons 2008-01-16 klockan 08:01 +0000 skrev Chris:
>>   
>>     
>>> Hi Allan.
>>>
>>> I'm not too sure. I found the following line?
>>>
>>> ac_cv_func_getenv=no
>>>
>>> But there are also a few other lines referring to getenv. I've pasted it 
>>> up at http://dpaste.com/31205/ to avoid a large post here.
>>>
>>> Any ideas?
>>> Chris
>>>     
>>>       
>> From the log it looks like you are missing the 64 bit version of
>> libieee1284-devel. So linking fails, and all tests fails - including the
>> getenv test.
>>
>> 	Mattias
>>
>>   
>>     
>
>
>