<div dir="ltr">Thanks a lot. :) I2C framework uses IMFS that why I think this solution worked.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jul 24, 2016 at 11:52 PM, Ben Gras <span dir="ltr"><<a href="mailto:beng@shrike-systems.com" target="_blank">beng@shrike-systems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>All,</p>
<p>Aha, I see the problem indeed.<br>
</p>
From the output I conclude default-configuration.o is providing
symbols that conflict with your configuration symbols. This suggests
default-configuration.o is pulled in to satisfy some configuration
requirement. This suggests we should put more info in init.c.<br>
<br>
I found a small change from your init.c that seems to "fix" this
problem:<br>
<div><span dir="ltr">-#define CONFIGURE_USE_DEVFS_AS_BASE_FILESYSTEM<br>
+#define CONFIGURE_FILESYSTEM_IMFS</span></div>
<br>
I guess DEVFS is too limited to support the I2C subsystem but I
didn't go so deep as to find out what the ins and outs are once I
saw this does link :-)<div><div class="h5"><br>
<br>
<div>On 24-07-16 09:06, punit vara wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><a href="https://github.com/punitvara/rtems/tree/new" target="_blank">https://github.com/punitvara/rtems/tree/new</a><br>
<div><br>
</div>
<div>You can reproduce linking error from this new branch. </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Jul 23, 2016 at 11:57 PM, Ben
Gras <span dir="ltr"><<a href="mailto:beng@shrike-systems.com" target="_blank">beng@shrike-systems.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
<br>
I tried to reproduce this. The I2C branch of your repo
doesn't build<br>
because of struct i2c not being defined. So I #if 0'd out
all the<br>
function bodies in i2c.c, and then everything builds,
without linker errors.<br>
<br>
What is your state now? Are you blocked on this (or anything
else)<br>
still? If so, can you help me reproduce, e.g. by creating a
branch that<br>
definitely exhibits the problem?<br>
<br>
I did build from scratch, if you have linking problems it
may be an idea<br>
to rm -rf the beagle build dir and reconfigure and rebuild,
in case<br>
there is a library hanging around with an extra object file
it isn't<br>
supposed to have that the buildsystem isn't updating.<br>
<br>
Cheers,<br>
<br>
Ben<br>
<div>
<div><br>
<br>
On 22-07-16 14:26, punit vara wrote:<br>
>
/root/development/rtems/b-NEW/arm-rtems4.12/c/beagleboneblack/cpukit/libmisc/../../../../../../../../NEW/c/src/../../cpukit/libmisc/dummy/default-configuration.c:23:<br>
> multiple definition of<br>
>
`_Linker_set__Sysinit__RTEMS_tasks_Initialize_user_tasks_body'<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>