| 00:13.57 | *** join/#oe troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 00:39.04 | *** join/#oe troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 03:04.31 | *** join/#oe yann (~yann@91-170-159-152.subs.proxad.net) |
| 03:21.02 | *** join/#oe davidlt (~davidlt@78-63-27-146.static.zebra.lt) |
| 04:25.52 | *** join/#oe davidlt (~davidlt@78-63-27-146.static.zebra.lt) |
| 04:52.38 | *** join/#oe florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 06:21.17 | *** join/#oe AndersD (~AndersD@h83-209-96-136.cust.a3fiber.se) |
| 06:23.01 | *** join/#oe AndersD_ (~AndersD@195-67-57-138.customer.telia.com) |
| 07:09.45 | *** join/#oe kroon (~kroon@213.185.29.22) |
| 07:14.50 | *** join/#oe tgamblin_ (~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com) |
| 07:16.14 | *** join/#oe vesper (~ves@37.120.213.8) |
| 07:20.33 | *** join/#oe sstiller (~sstiller@p200300F07F08D20131B7C19EEB89D61B.dip0.t-ipconnect.de) |
| 14:01.41 | *** join/#oe infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 14:01.41 | *** topic/#oe is OpenEmbedded Developer Lounge | Web: http://openembedded.org | Repositories: http://git.openembedded.org/ | Primary Repo Mirrors: https://github.com/openembedded | This is not a distro or machine support channel |
| 15:47.07 | *** join/#oe adelcast (~adelcast@cpe-68-203-3-226.austin.res.rr.com) |
| 15:48.44 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 15:57.09 | *** join/#oe adelcast (~adelcast@cpe-68-203-3-226.austin.res.rr.com) |
| 16:27.39 | *** join/#oe florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 16:57.38 | *** join/#oe jpuhlman (~jpuhlman@45.19.219.178) |
| 17:13.24 | *** join/#oe nerdboy (~sarnold@gentoo/developer/nerdboy) |
| 18:18.20 | *** join/#oe cpriouzeau (~cpriouzea@164.129.115.76) |
| 18:35.23 | *** join/#oe ao2 (~ao2@87.18.228.219) |
| 18:56.54 | *** join/#oe florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 19:47.35 | *** join/#oe berton_ (~berton@181.220.114.167) |
| 20:12.40 | *** join/#oe infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 20:12.40 | *** topic/#oe is OpenEmbedded Developer Lounge | Web: http://openembedded.org | Repositories: http://git.openembedded.org/ | Primary Repo Mirrors: https://github.com/openembedded | This is not a distro or machine support channel |
| 20:12.44 | fray | assuming you have the baremetal configured properly -- it works fine.. (at least for newlib and libgloss) |
| 20:14.00 | Jin^eLD | hmm. I can't get pass "c compiler cant create executables" so I am clearly doing something wrong then |
| 20:14.21 | fray | are you using newlib/libgloss or something as as your compiler's C library? |
| 20:14.42 | fray | easiest thing to do though is look at the config.log file, and see what the actual C compiler error was.. it may be obvious from there |
| 20:15.02 | fray | (NOT the temp/log.do_configure, but the actualy config.log from the build directory) |
| 20:15.25 | Jin^eLD | well, I did look at that and its complaining about undefined reference to _exit |
| 20:15.46 | Jin^eLD | as for newlib: I am trying out the arm-none-eabi compiler that comes on fedora, it does use newlib |
| 20:15.47 | fray | depending on the newlib configuration, libgloss and/or the linker script provides the _exit |
| 20:16.11 | fray | the newlib (and libgloss) combo built in can generate a working baremetal for arm |
| 20:16.30 | fray | but it's definitely more configure heavy then other parts.. :P |
| 20:17.13 | Jin^eLD | so what do you pass to configure? do you have a line that you use for me to compare? |
| 20:17.34 | Jin^eLD | I am trying to build for cortex m4 btw |
| 20:17.39 | fray | sec |
| 20:18.22 | fray | What I'm passing: |
| 20:18.23 | fray | TCLIBC = "newlib" |
| 20:18.23 | fray | TCLIBCAPPEND ="" |
| 20:18.30 | fray | LIBC_DEPENDENCIES_append = " newlib-staticdev libgloss-staticdev" |
| 20:18.43 | fray | DISTRO_FEATURES_BACKFILL_xilinx-standalone = "" |
| 20:18.43 | fray | VIRTUAL-RUNTIME_init_manager_xilinx-standalone = "" |
| 20:18.43 | fray | PREFERRED_PROVIDER_virtual/kernel = "linux-dummy" |
| 20:18.58 | fray | TOOLCHAIN_NEED_CONFIGSITE_CACHE = "" |
| 20:19.03 | fray | thats the distro file |
| 20:19.20 | Jin^eLD | wait, you're building baremetal stuff with yocto? wow, I did not know that was possible |
| 20:19.32 | fray | for cortex r5 (similar to m) should be something like this: |
| 20:19.43 | fray | (tune file) |
| 20:19.44 | fray | require conf/machine/include/arm/arch-armv8a.inc |
| 20:19.50 | fray | TUNEVALID[armrm] = "Enable ARM Cortex-R/M Family" |
| 20:19.51 | fray | MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armrm', 'armrm:', '' ,d)}" |
| 20:19.57 | fray | TUNEVALID[cortexr5] = "Enable Cortex-r5 specific processor optimizations" |
| 20:19.57 | fray | TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexr5', ' -mcpu=cortex-r5', '', d)}" |
| 20:19.57 | fray | AVAILTUNES += "cortexr5" |
| 20:19.57 | fray | ARMPKGARCH_tune-cortexr5 = "cortexr5" |
| 20:20.02 | fray | TUNE_FEATURES_tune-cortexr5 = "armrm cortexr5" |
| 20:20.02 | fray | PACKAGE_EXTRA_ARCHS_tune-cortexr5 = "${TUNE_PKGARCH}" |
| 20:20.02 | fray | AVAILTUNES += "cortexr5f" |
| 20:20.02 | fray | ARMPKGARCH_tune-cortexr5f = "cortexr5f" |
| 20:20.11 | fray | TUNE_FEATURES_tune-cortexr5f = "armrm cortexr5 vfpv3d16 callconvention-hard" |
| 20:20.11 | fray | PACKAGE_EXTRA_ARCHS_tune-cortexr5f = "${TUNE_PKGARCH}" |
| 20:20.20 | fray | You should be able to add a similar entry for cortex m |
| 20:20.42 | Jin^eLD | well, actually that is a bit too far in the sense that I am trying to set up an autotools based project for some M4 code that I have here |
| 20:20.52 | fray | I also have defined a bare bones 'machine' called cortexr5-generic that includes the tune and sets the defaulttune to cortexr5f |
| 20:20.58 | Jin^eLD | so you are already several steps ahead :) |
| 20:21.17 | Jin^eLD | could you please paste me the beginning of your log.do_configure where it passes all the parameters to the configure script? |
| 20:21.18 | fray | You can use the Yocto Project to build the newlib and the toolchain (meta-toolchain build)... that is where we started |
| 20:21.26 | fray | the distro/machine/tune are still needed for that |
| 20:21.37 | Jin^eLD | this is actaully pretty cool |
| 20:21.39 | fray | let me see, I may not have a recent build |
| 20:22.54 | fray | newlib-3.1.0/configure --build=x86_64-linux --target=aarch64-xilinx-elf --host=aarch64-xilinx-elf --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --libdir=/usr/lib --includedir=/usr/include --enable-languages=c --with-newlib --with-gnu-as --with-gnu-ld --disable-multilib |
| 20:23.10 | fray | ewlib-io-c99-formats --enable-newlib-io-long-long --enable-newlib-io-float --enable-newlib-io-long-double --disable-newlib-supplied-syscalls |
| 20:23.48 | fray | (the reason I'm doing this is you can, with a multiconfig build, build both the Linxu side and any baremetal stuff.. cortexr5 or other controllers for firmware you may have in a single build.. we're still very much prototyping that, but expect to start using it within a year |
| 20:23.52 | Jin^eLD | but whats the use case of building a "distro" for baremetal? mostly in the meta-toolchain, i.e. building a toolchain for baremetal, right? because if I understasnd correctly - you can only have exactly one binary loaded there and thats it? |
| 20:24.12 | fray | two use-cases.. first is simply to build the toolchain.. that is the most immediate.. |
| 20:24.19 | Jin^eLD | I thought you could build that in a single build already? |
| 20:24.30 | Jin^eLD | well, by having a recipe that downloads the toolchain |
| 20:24.35 | Jin^eLD | and then setting CC in the recipe |
| 20:24.37 | Jin^eLD | but I guess thats hacky |
| 20:24.40 | fray | the second is for use to built either cortex r5 and microblaze control software.. so it can be included as firmware |
| 20:24.47 | Jin^eLD | aha |
| 20:24.49 | fray | exactly.. we want to get rid of the hacky |
| 20:24.55 | Jin^eLD | nice! |
| 20:25.12 | fray | IMHO, eventually u-boot, and other baremetal stuff should be built using this apporch and NOT hacky build scripts in the linux side of the cross build.. |
| 20:25.17 | Jin^eLD | thanks for the paste, let me see if I find out what I am missing compared to yours, actually I am trying it by hand in the console now |
| 20:25.28 | fray | (eventually may be a while in the furture to be honest) |
| 20:26.22 | fray | I've completely replaced the ARM and Linaro supplied toolchains at this point with Yocto Project derived toolchains.. lets us have a single common source code base for all of the supported target architectures (not just arm) |
| 20:26.39 | Jin^eLD | that'd be super cool |
| 20:26.43 | fray | (At Xilinx we have arm, arm64 and microblaze we have to support.. both baremetal and linux) |
| 20:28.00 | Jin^eLD | does make sense to get rid of the "hacky" indeed then... |
| 20:28.16 | Jin^eLD | I generally am always cautions towards anything that comes in as "precompiled binaries" |
| 20:28.21 | Jin^eLD | *cautious |
| 20:28.49 | fray | same.. thus the move to YP derived.. I can do a custom build and product the necessary baremetal or target (linux) toolchains... |
| 20:29.06 | fray | the other tricky bit, is I had an ask to duplicate the insanity that is the ARM baremetal toolchain.. |
| 20:30.13 | fray | that meant enabling the -21- ARM multilibs in a single configuration |
| 20:30.34 | fray | the system takes about 10 minuts just to parse so it can build and construct meta-toolchain target |
| 20:30.51 | fray | doing it the crosstool-ng way would have been faster, but then it's "yet another tool to support" |
| 20:30.53 | Jin^eLD | heh |
| 20:33.22 | Jin^eLD | if I look at newlibs configure.ac I think I know why mine won't work... tons of special stuff in there |
| 20:33.45 | Jin^eLD | I guess autoconf does not support baremetal "out of the box" unless I am not seeing something obvious |
| 20:33.51 | fray | newlib, like glibc, does a LOT of stuff to setup expecting a mostly not working compilier |
| 20:34.15 | Jin^eLD | hm |
| 20:34.31 | Jin^eLD | well in theory just passing --build and --host should be enough |
| 20:35.03 | Jin^eLD | but that does not work for me |
| 20:44.43 | *** join/#oe rcw (~rcw@45.72.242.250) |
| 21:19.21 | Jin^eLD | fray: -nostdlib in CFLAGS made the configure.ac to actually not do the compiler test |