On 02/09/14 20:16, Earl Ramirez wrote:
> On Tue, 2014-09-02 at 09:47 -0400, Lamar Owen wrote:
>> On 09/01/2014 05:37 PM, ToddAndMargo wrote:
>>>
>>>
>>> An RPM [of autoscan-network] yet to try?
>>>
>>>
>>
>> In my own quick build attempts, I was not successful in building a 
>> running binary from source.  Also, the binary tarball didn't run, 
>> either.  But I'm running 64-bit and the tarball is 32-bit, and there are 
>> a few indications that it might not build properly as 64-bit.
>>
>> But it wasn't high on my priority list, either, so I only put half an 
>> hour or so into seeing just how easy or difficult it would be to build.  
>> I did track down dependencies as they were declared, and the binary 
>> built, but it would not actually run as built.  So I've put it on the 
>> back burner here, since, as I say, it's not a terribly high priority to 
>> me at the moment.  If you need it, you can use a BackTrack/Kali live 
>> disk which as far as I know still includes autoscan-network.
> I have stumble upon the source RPM for it and I am also in the process
> of getting it to work on el6 (for now, will be another story for el7).
> 
> I thinking about moving the install directory from /usr/share/apps
> to /opt/* directory, thoughts are welcome. I am doing the build on a
> vanilla el6 install and below are the build dependencies, which I plan
> to sort out within a few days if time permits.
> 
> rpmbuild -ba rpmbuild/SPECS/autoscan.spec
> error: Failed build dependencies:
> 	gnomeui2-devel is needed by autoscan-1.50-1.el6.x86_64
> 	libao-devel is needed by autoscan-1.50-1.el6.x86_64
> 	libvorbis-devel is needed by autoscan-1.50-1.el6.x86_64
> 	net-snmp-devel is needed by autoscan-1.50-1.el6.x86_64
> 	gtk+2-devel is needed by autoscan-1.50-1.el6.x86_64
> 	libgtk-vnc-devel is needed by autoscan-1.50-1.el6.x86_64
> 	libgnome-keyring-devel is needed by autoscan-1.50-1.el6.x86_64
> 	vte-devel is needed by autoscan-1.50-1.el6.x86_64
> 	pcap-devel is needed by autoscan-1.50-1.el6.x86_64
> 
> This is my hobby and if there anyone with extensive experience I am
> happy to get some little tips.
> 

I'd recommend you to install mock and build it via mock.  Your user
account must be member of the mock group to function.

Mock builds pulls down the needed packages for the distribution you
build your packages for, unpacks them in a chroot and does the complete
build process inside that chroot.  On success, you'll get RPMs and on
failures you'll get a lot of log files to study :)

As I have my own mock configurations, I don't remember the exact syntax
... but it's something like this:

   $ mock -r epel-6-x86_64 --rebuild autoscan-1.50-1.el6.src.rpm

Sit down and wait for a while, and the results can be found in the
/var/lib/mock/epel-6-x86_64/results directory.

Using this approach, the same computer can build packages for a vast
majority of Fedora and EPEL packages, on several CPU architectures.
Look in /etc/mock to see all the available configurations
out-of-the-box.  Adopting for specific SL builds isn't that hard to
accomplish either.

Mock is one of the building-blocks koji (the Fedora build system) uses.


-- 
kind regards,

David Sommerseth