From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] regression linking against libcgi after fixing patches in a53b663
Date: Thu, 01 Nov 2012 13:06:03 +0100 [thread overview]
Message-ID: <5e8b11e21ed88fe79b70649f39f5e52e@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20121028170915.GC22246@pengutronix.de>
Hei hei,
Am 2012-10-28 18:09, schrieb Michael Olbrich:
>> 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.
Works now. File is libcgi.so.0 and symlink is libcgi.so pointing to the
file.
> 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.
Okay I'll try to get a release out, we'll see.
> [1] http://0pointer.de/blog/projects/libabc.html
I will have a look at this, thank you. (Had already forgotten I
stumbled over libabc a long while ago.)
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-11-01 12:06 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
2012-11-01 12:06 ` Alexander Dahl [this message]
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=5e8b11e21ed88fe79b70649f39f5e52e@idefix.lespocky.dyndns.org \
--to=post@lespocky.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