From: Seebs <seebs@seebs.net>
To: Mark Hatle <mark.hatle@kernel.crashing.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pseudo: Drop static linking to sqlite3
Date: Mon, 11 Nov 2019 10:34:38 -0600 [thread overview]
Message-ID: <20191111103438.4177e780@seebsdell> (raw)
In-Reply-To: <d9dedf00-f8f4-8bf6-5b94-81868de5dc31@kernel.crashing.org>
On Mon, 11 Nov 2019 08:17:30 -0600
Mark Hatle <mark.hatle@kernel.crashing.org> wrote:
> First (early) version of pseudo would fork for the server, there
> wasn't a seperate executed server and we had all sorts of problems
> with dynamic libraries being loaded and loaded from the correct paths
> (due to the LD_PRELOAD).
>
> Moving to two process spaces, LD_PRELOAD and the pseudo executable
> happened pretty early in development, but I suspect some of this is
> left over from that.
To be picky:
pseudo *still does this*. If it can't find the server, it clears the
environment and respawns it. There were problems with this for the
longest time, which turned out to be because I was calling setenv to
clean the environment, and bash *overrides setenv*, so if the program
spawning the pseudo server was bash, things went wrong. It should
actually be fixed now and work pretty well.
-s
prev parent reply other threads:[~2019-11-11 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 15:35 [PATCH] pseudo: Drop static linking to sqlite3 Richard Purdie
2019-11-09 16:07 ` Seebs
2019-11-09 16:30 ` Richard Purdie
2019-11-09 16:46 ` Seebs
2019-11-11 13:04 ` Andre McCurdy
2019-11-11 15:59 ` Khem Raj
2019-11-11 16:36 ` Adrian Bunk
2019-11-11 17:19 ` Khem Raj
2019-11-11 14:17 ` Mark Hatle
2019-11-11 16:34 ` Seebs [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=20191111103438.4177e780@seebsdell \
--to=seebs@seebs.net \
--cc=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
/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