From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] regression linking against libcgi after fixing patches in a53b663
Date: Sun, 28 Oct 2012 18:09:15 +0100 [thread overview]
Message-ID: <20121028170915.GC22246@pengutronix.de> (raw)
In-Reply-To: <5a9dfd144d5a6ea0605eb1762719b078@idefix.lespocky.dyndns.org>
Hi,
On Wed, Oct 24, 2012 at 11:05:16AM +0200, Alexander Dahl wrote:
> in commit a53b663 a typo in Makefile of LibCGI was fixed, actually in
> the patches fixing various things in LibCGI. This sets the soname of the
> library to libcgi.so.0 in the options passed to the linker. However this
> libcgi.so.0 is never installed but libcgi.so instead. This does work at
> build time when compiling and linking against libcgi but at runtime this
> fails because libcgi.so is installed in both install and targetinstall
> stage but there's no libcgi.so.0 present on the target.
>
> I'm not familiar with autotools to fix this myself. Expected behaviour
> would be some libcgi.so.x.y.z is installed and libcgi.so.x and libcgi.so
> are symlinks of which only libcgi.so.x is installed to the target. If I
> rename libcgi.so on my target to libcgi.so.0.0.0 and create a symlink
> libcgi.so.0 my cgis work again.
I think I fixed this now, but I can't test it. Please try.
> by the way: the author of the libcgi library moved the code from
> sourceforge to github [1] and kindly responses to mails, bug reports und
> pull requests. I'll ask him how he plans to proceed with this long dead
> project and I'll share the result here. He already integrated the
> changes and fixes of the patches ptxdist carries in the master branch (I
> integrated those in one single commit in my personal fork and made a
> pull request in the expectation nobody would care, so sorry if you're
> not getting your credits.) I'll come up with some other patches fixing
> some things in the lib. I would share these with ptxdist as well and
> hope we could work toward some bugfix release 1.x of the lib integrating
> all the current changes to get rid of the patches. What's your opinion
> about this?
That sounds good. Especially the part about a release. I always like it
when I can remove patches from ptxdist. If someone is actually working on
this, I really suggest cleaning up the build system. If you don't know
enough about this, then look at libabc[1]. This is a good place to get
started with this.
Michael
[1] http://0pointer.de/blog/projects/libabc.html
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-10-28 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 9:05 Alexander Dahl
2012-10-28 17:09 ` Michael Olbrich [this message]
2012-11-01 12:06 ` Alexander Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121028170915.GC22246@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox