I am using a similar configuration to ‘bsps/pc’ to build with source builder. During the compilation of libbsd I see undefined references to the following 12 variables:
e1000_acquire_phy_base
e1000_init_hw_base
e1000_power_down_phy_copper_base
e1000_release_phy_base
e1000_rx_fifo_flush_base
hpts_that_need_softclock
pci_cfgregread_domain
pci_cfgregwrite_domain
pfil_mem_in
resource_init_map_request_impl
resource_validate_map_request
tcp_hpts_softclock
Could you please offer advice on how to get these variables defined?
Thanks,
Ben.
Might it be possible to get libbsd to not use those symbols? For what purpose is the bsp/pc package bringing those symbols in?
Which branch are you using? I recall a recent problem where this was missing on a branch. I
Thanks Joel.
I was using the main branch. Yesterday, I downloaded RTEMS source builder 6.1, which appears to be the most recent release and it worked perfectly. Is it ridiculous to just use a release rather than the git repo?
I suspect this question might be caused by not understanding the release process very well. I noticed when using main, that it had referenced ‘7’ many times like in rtems/config/tools/rtems-kernel-7.cfg. In the 6.1 source it referenced ‘6’ in the same areas and then for both the rtems source builder versions seem to not coincide to an rtems kernel source version, rather the kernel source has a hash for the version number. Could you help me understand the releases a little better?
You almost certainly do not want to be on main. This is the repo description:
FreeBSD on RTEMS - Networking, USB, Filesystems, Media. Branches for versions of RTEMS: 6 uses 6-freebsd-12, 7 uses 7-freebsd-14
The branch names reflect the FreeBSD and RTEMS version combination. 7-freebsd-14 should work. Main tracks FreeBSD development and appears to be missing those files.
1 Like