All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: "정재윤/Task Leader/SW Platform(연)선행Platform개발실 시스템SW Task"
	<jaeyoon.jung@lge.com>
Cc: "Florian Westphal" <fw@strlen.de>,
	"조홍식/책임연구원/SW Security개발실 SW Security TP" <hongsik.jo@lge.com>,
	"netfilter-devel@vger.kernel.org"
	<netfilter-devel@vger.kernel.org>,
	"손영섭/책임연구원/SW Security개발실 SW Security TP" <loth.son@lge.com>,
	"남정주/책임연구원/SW Security개발실 SW Security TP" <jungjoo.nahm@lge.com>
Subject: Re: Symbol Collision between ulogd and jansson
Date: Tue, 14 Jan 2025 14:32:06 +0100	[thread overview]
Message-ID: <20250114133206.GA5817@breakpoint.cc> (raw)
In-Reply-To: <PU4P216MB15179D0909B9BEB9770F24F09A182@PU4P216MB1517.KORP216.PROD.OUTLOOK.COM>

정재윤/Task Leader/SW Platform(연)선행Platform개발실 시스템SW Task <jaeyoon.jung@lge.com> wrote:
> Hi,
> 
> It's 2.14 being built with CMake.
> It looks like '-export-symbols-regex' isn't set with CMake.

Can you file a report with jansson? Libraries should not pollute
the namespace like this.  I can confirm that its fine with autotools
but cmake generated .so has everyting exported :-(

[ I also find it very questionable to have two build systems; it
makes these bugs harder to find for everyone, but thats a
different issue ].

  reply	other threads:[~2025-01-14 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13  6:41 Symbol Collision between ulogd and jansson 조홍식/책임연구원/SW Security개발실 SW Security TP
2025-01-13 22:23 ` Pablo Neira Ayuso
2025-01-14  5:00   ` 조홍식/책임연구원/SW Security개발실 SW Security TP
2025-01-14  5:02     ` 조홍식/책임연구원/SW Security개발실 SW Security TP
2025-01-14 10:41 ` Florian Westphal
2025-01-14 12:50   ` 정재윤/Task Leader/SW Platform(연)선행Platform개발실 시스템SW Task
2025-01-14 13:32     ` Florian Westphal [this message]
2025-01-15  8:08       ` 조홍식/책임연구원/SW Security개발실 SW Security TP
2025-01-15 12:29         ` Florian Westphal

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=20250114133206.GA5817@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=hongsik.jo@lge.com \
    --cc=jaeyoon.jung@lge.com \
    --cc=jungjoo.nahm@lge.com \
    --cc=loth.son@lge.com \
    --cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.