All, Aha, I see the problem indeed.
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. I found a small change from your init.c that seems to "fix" this problem: -#define CONFIGURE_USE_DEVFS_AS_BASE_FILESYSTEM +#define CONFIGURE_FILESYSTEM_IMFS 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 :-) On 24-07-16 09:06, punit vara wrote: > https://github.com/punitvara/rtems/tree/new > > You can reproduce linking error from this new branch. > > On Sat, Jul 23, 2016 at 11:57 PM, Ben Gras <b...@shrike-systems.com > <mailto:b...@shrike-systems.com>> wrote: > > All, > > > I tried to reproduce this. The I2C branch of your repo doesn't build > because of struct i2c not being defined. So I #if 0'd out all the > function bodies in i2c.c, and then everything builds, without > linker errors. > > What is your state now? Are you blocked on this (or anything else) > still? If so, can you help me reproduce, e.g. by creating a branch > that > definitely exhibits the problem? > > I did build from scratch, if you have linking problems it may be > an idea > to rm -rf the beagle build dir and reconfigure and rebuild, in case > there is a library hanging around with an extra object file it isn't > supposed to have that the buildsystem isn't updating. > > Cheers, > > Ben > > > On 22-07-16 14:26, punit vara wrote: > > > > /root/development/rtems/b-NEW/arm-rtems4.12/c/beagleboneblack/cpukit/libmisc/../../../../../../../../NEW/c/src/../../cpukit/libmisc/dummy/default-configuration.c:23: > > multiple definition of > > `_Linker_set__Sysinit__RTEMS_tasks_Initialize_user_tasks_body' > >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
