If linking libopkg against a project where a symbol called conf is used the linker complains multiple definition of conf

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Link libopkg against a projekt where a symbol conf is used

I would expect no error, but I get conf is allready defined.

I am using svn trunk

This is caused due to namespace conflicts. libopkg debases the global namespace 
by exporting the global symbol conf.

I've fixed this by renaming the symbol conf to opkg_conf_ 

Original issue reported on code.google.com by rosa.gum...@gmail.com on 9 Sep 2012 at 6:17

Attachments:

• 0001-opkg-fixed-global-conf.diff

[GoogleCodeExporter]

Any comments on this? 
Is there any better way to solve this issue?
There is a interesting comment in libopkg/Makefile.am

# make sure we only export symbols that are for public use
#libopkg_la_LDFLAGS = -export-symbols-regex "^opkg_.*"

I am really interested to fix this issue.

Original comment by rosa.gum...@gmail.com on 3 Mar 2013 at 6:29

[GoogleCodeExporter]

I prefer the way this is fixed in the following repo: 
https://bitbucket.org/graugans/opkg

The variable is renamed to opkg_config.

I've also got a merge branch at 
https://bitbucket.org/betafive/opkg/commits/branch/pbarker%2Fmerge where I'm 
trying to test a few of these fixes together.

Original comment by paul.betafive on 24 Jul 2013 at 7:36

[GoogleCodeExporter]

Original comment by paul.betafive on 1 Aug 2013 at 10:04

[GoogleCodeExporter]

Original comment by paul.betafive on 1 Aug 2013 at 10:06

• Changed state: Accepted

[GoogleCodeExporter]

Fixed in r689.

Original comment by paul.betafive on 18 Sep 2013 at 1:02

• Changed state: Fixed