New: libMonoPosixHelper.so wrong link reference in buildroot image

https://bugs.busybox.net/show_bug.cgi?id=8651

Bug ID: 8651
Summary: libMonoPosixHelper.so wrong link reference in
buildroot image
Product: buildroot
Version: 2015.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: Markus.Egle at Qiagen.com
CC: buildroot at uclibc.org
Target Milestone: ---

With the current buildroot 2015.11.1 (initially seen with 2015.05) configured to use mono, the libMonoPosixHelper.so will be searched in the /home/userX/buildroot/output/host/usr/lib/ path. This path and file may exist on my building machine, but not on the target.

I have a working workaround with creating this folder and copy libMonoPosixHelper.so from /usr/lib at startup in the ram disk.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

Markus Egle <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Target|                            |Intel Atom PC104
               Host|                            |Ubuntu 15.10

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #1 from Angelo <[email protected]> --- Dear Markus Egle,

It is probably reletad to this bug:

https://bugzilla.xamarin.com/show_bug.cgi?id=24131

Try that workaround and report your results here. I'll look at this ASAP.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #2 from Markus Egle <[email protected]> ---
Till now I'm not really familiar with the config/make procedure. So I don't know if I have to change the Makefile.in or the config.in or both.

Found four possible locations to make the testing changes.

...> find /home/eglem/buildroot -name "*.in"|grep mono|awk '{print "grep -Hn libMonoPosixHelper " $1}'|sh|grep target

/home/eglem/buildroot/output/build/host-mono-4.0.2.5/runtime/Makefile.in:629:
sed 's,target="$(prefix)/$(reloc_libdir)/libMonoPosixHelper$(libsuffix)",target="'$$d'/libMonoPosixHelper.la",' ../data/config > $@t /home/eglem/buildroot/output/build/host-mono-4.0.2.5/data/config.in:13: <dllmap dll="MonoPosixHelper"
target="@prefix@/@reloc_libdir@/libMonoPosixHelper@libsuffix@" os="!windows" /> /home/eglem/buildroot/output/build/mono-4.0.2.5/runtime/Makefile.in:629:
sed 's,target="$(prefix)/$(reloc_libdir)/libMonoPosixHelper$(libsuffix)",target="'$$d'/libMonoPosixHelper.la",' ../data/config > $@t
/home/eglem/buildroot/output/build/mono-4.0.2.5/data/config.in:13: <dllmap
dll="MonoPosixHelper"
target="@prefix@/@reloc_libdir@/libMonoPosixHelper@libsuffix@" os="!windows" />

Then I just remove the prefix?

You are receiving this mail because:
You are on the CC list for the bug.

Dear Markus Egle,

Could you try to have a look at file /etc/mono/config in your generated image?

2016-02-04 15:24 GMT+01:00 <[email protected]>:

Profile: http://it.linkedin.com/in/compagnucciangelo

Dear Angelo Compagnucci,

You should reply in the bug tracker. I am not sure Markus is a subscriber of the Buildroot mailing list, and I'm not sure sending e-mails to bugzilla at busybox.net works.

Otherwise, thanks a lot for taking care of this Mono bug report. It is good to see additional users testing this functionality, as it will test it in different conditions.

Thanks!

Thomas

Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #3 from Angelo <[email protected]> --- Dear Markus Egle,

Could you try to have a look at file /etc/mono/config in your generated image?

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #4 from Markus Egle <[email protected]> --- The config file on the target shows this wrong path to the lib.

grep home /etc/mono/config
<dllmap dll="MonoPosixHelper"
target="/home/userX/buildroot/output/host/usr/lib/libMonoPosixHelper.so" os="!windows" />

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #5 from Angelo <[email protected]> --- Great!

Change that line and it should work. Now we should understand where that file is generated that way ...

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #6 from Markus Egle <[email protected]> --- Crosschecked it...

- corrected ./buildroot/output/target/etc/mono/config

- removed the libMonoPosixHelper.so copy to home folder... at startup

And it works. Thanks.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #7 from Angelo <[email protected]> --- Dear Markus Egle,

Could you send a minimal example that triggers the bug?

Thank you!

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #8 from Markus Egle <[email protected]> --- Created attachment 6331
--> https://bugs.busybox.net/attachment.cgi?id=6331&action=edit
Archive with SimpleSerialPortOpen.exe

            SerialPort sp = new SerialPort("/dev/ttyS0", 19200);
            try
            {
                sp.Open();
            }
            catch (Exception ex)
            {
                Console.WriteLine(ex.Message);
            }

creates the error that libMonoPosixHelper.so couldn't be found.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #9 from Angelo <[email protected]> --- Created attachment 6336
--> https://bugs.busybox.net/attachment.cgi?id=6336&action=edit
libmonoposixhelper location patch

Dear Markus Egle,

Could you try the attached patch?

Simply drop it into package/mono folder and rebuild mono.

Thanks!

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

Markus Egle <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #10 from Markus Egle <[email protected]> --- Fixed.

Applied patch with copying to buildroot/package/mono After

buildroot/output/target/etc/mono/config shows the correct path for libMonoPosixHelper.so without any prefix and accordingly bzImage works as expected.

Thanks
Markus

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #11 from Thomas Petazzoni <[email protected]> --- Reopening the bug, since the patch proposed by Angelo has not been submitted/applied in Buildroot. Angelo, can you submit your patch?

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

--- Comment #12 from Angelo <[email protected]> --- (In reply to Thomas Petazzoni from comment #11)

Of Course, I'll submit a patch soon.

Sincerely, angelo

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8651

Arnout Vandecappelle <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |2016.02

--- Comment #13 from Arnout Vandecappelle <[email protected]> --- 9cc9c224f9675d1e724974a0915093e55519db8b has been committed.

You are receiving this mail because:
You are on the CC list for the bug.