Re: libasn?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for your reply.  In the meantime (over the weekend or on Friday)
what I did was to do this in iteration (pseudocode):

Comment out everything under %files
FOUND=0
while FOUND==0
      rpmbuild -ba 2>&1  |  grep libasn 
      if grep succesful
          FOUND=1
      else
          uncomment one file from %files section (and remember which it is)
      fi
DONE

then if FOUND was 1, I would check the last file I uncommented and do an ldd on it.
This took quite some time, but finally the ldd showed
    ldd lininexe002802004 | grep found
            libasn1code.so => not found
            libosstoed.so => not found

I asked for verification from some people, but it turns out this file is probably not needed, so I can probably
just remove it.  I guess rpmbuild is pretty intelligent and scans everything under %files to be sure everything
is included.  (Or at least to know, so it can check on the install machine).
     

-----Original Message-----
From: Hiren Patel [mailto:patelhn@xxxxxxxxxxxx]
Sent: Monday, June 11, 2007 02:26 AM
To: 'RPM Package Manager'
Subject: Re: libasn?


yes using -nodeps is not a good idea at all.
there is nothing wrong with the rpm build process, during the build rpm
figures out what the program needs to run, and make those 'requires' for
that binary rpm installation.

the most i can think of, is to try and see if those libraries are
installed on the machine you are building the rpms on, see what packages
they belong to, and install those packages elsewhere, where your program
is going to be installed.

on the build machine:

slocate libasn1code.so
slocate libosstoed.so

if you get any output, check the packages they belong to by using,

rpm -qf </path/to/the/library>

On Fri, 2007-06-08 at 19:30 +0000, tony.chamberlain@xxxxxxxxx wrote:
> I am writing some RPMS. Started a few weeks ago. I started from
> scratch and have learned a lot in the
> last few weeks.
>
> Until now, things have been working pretty well (except some
> frustration with macros). But now just today I ran into a
> problem. Maybe it was a problem before but I never ran into it.
>
> I try to do an rpm -Uvh on the rpm I create and I get the following:
>
> error: Failed dependencies:
> libasn1code.so is needed by tdapi-is41-1.0.0-0.i386
> libosstoed.so is needed by tdapi-is41-1.0.0-0.i386
>
> google search of libasn list maybe 5 sites, most of which are Samba.
> Looking for libosstoed doesn't list any documents.
>
> Anyone know how to find these? The only thing I am doing differently
> from before is using the
> %package directive in the specfile.
>
> Sure when I do --nodeps it work, but that defeats the purpose of RPM's
> "requires" directive.
>
> Thanks
>
>
>
>
> _______________________________________________
> Rpm-list mailing list
> Rpm-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/rpm-list
--
Hiren Patel

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail and its contents are subject to the Telkom SA Limited
e-mail legal notice available at
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux