[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: jabberd (1) deletion?
Frédéric Fauberteau <triaxx%triaxx.org@localhost> writes:
> Le 2019-10-05 15:53, Frédéric Fauberteau a écrit :
>> Le 2019-10-04 05:02, Greg Troxel a écrit :
>>> Great - I'm glad to hear that you are going to update it! Feel
>>> free to
>>> ask if any questions :-)
> I have a package that starts to install correctly now and pkglint has
> nothing to say. I still have some details to fix but it's on track.
> I used GITHUB_TAG= b2b871eaf3f6455d7d37113ce23d6bc59c8da70f to include
> all the recent updates of the maintainer and I set PKGNAME to
> jabberd-18.104.22.168 since NEWS file announces "Version 22.214.171.124 -
> 2007-07-22". Is it correct?
Please put this in wip, so it's easy to look at, if you don't feel
comfortable just updating.
> *** Warning: linker path does not have real file for library -lgcc.
> *** I have the capability to make that library automatically link in
> *** you link to this library. But I can only do this if you have a
> *** shared version of the library, which you do not appear to have
> *** because I did check the linker path looking for a file starting
> *** with libgcc and none of the candidates passed a file format test
> *** using a regex pattern. Last file checked: /usr/lib/libgcc.a
> *** Warning: libtool could not satisfy all declared inter-library
> *** dependencies of module libjabberdxdbsql. Therefore, libtool will
> *** a static module, that should work as long as the dlopening
> *** application is linked with the -dlopen flag.
That's a good question, and I'm not sure what's going on in this case.
There were some changes to how libgcc_s was handled, but this doesn't
seem obviously related to that.
Main Index |
Thread Index |