Experimental Physics and Industrial Control System
|
Hallo Vijay,
I still have to ask a question ;-)
When building EPICS, we distinguish legacy stack or libbsd with the help of
the target.cfg file. (e.g. powerpc-rtems6/beatnik/make/target.cfg).
Earlier in it was
RTEMS_HAS_NETWORKING = yes (for legacy stack) and no (for new bsd stack).
Now this flag will no be set with the waf build in your extra net-legacy repo.
How should we now find out if the target was built with legacyStack or with libbsd?
Eventually RTEMS itself won't have this at all. It will always have no networking and you have to add a stack.
This may be something that needs addressing. Not sure.
--joel
Danke Heinz
.
> On 3. Mar 2021, at 21:03, Vijay Kumar Banerjee <vijay at rtems.org> wrote:
>
> On Wed, Mar 3, 2021 at 12:37 PM junkes <junkes at fhi-berlin.mpg.de> wrote:
>>
>> Hi Vijay,
>> I tried it again:
>>
> Hi Heinz,
>
> I'm really sorry that the build crashed again. I missed the telnetd.h
> file probably because it was somewhere in my build prefix from one of
> the rtems builds. I have pushed a fix on the rtems repo and the
> rtems-net-legacy repo. This time I was more thorough and used a new
> prefix location, I believe it won't break this time.
>
> Thank you for helping with the testing. I really appreciate it.
>
>
> Best regards,
> Vijay
>
>> # building kernel
>> #git clone git://git.rtems.org/rtems.git kernel
>> git clone git://git.rtems.org/vijay/rtems.git kernel
>> cd kernel
>> git checkout devel-no-libnet
>>
>> # build and install bsp
>> # 1. Test with waf
>> #-e "s|RTEMS_NETWORKING = False|RTEMS_NETWORKING = True|" \
>> ./waf bsp_defaults --rtems-bsps=powerpc/beatnik > config.ini
>> sed -i \
>> -e "s|RTEMS_POSIX_API = False|RTEMS_POSIX_API = True|" \
>> -e "s|BUILD_TESTS = False|BUILD_TESTS = True|" \
>> config.ini
>> ./waf configure --prefix=/home/junkes/MVME6100_testing/rtems/6
>> ./waf
>> ./waf install
>>
>> cd ..
>>
>> # building extra legacy net
>> git clone git://git.rtems.org/vijay/rtems-net-legacy.git legacyNet
>> cd legacyNet
>> git submodule init
>> git submodule update
>>
>> ./waf configure --prefix=/home/junkes/MVME6100_testing/rtems/6
>>
>> ./waf build --rtems-archs=powerpc --rtems-bsps=beatnik
>>
>>
>> Much better, but still a missing file?
>>
>> [125/235] Compiling libc/res_mkquery.c
>> [126/235] Compiling libc/inet_lnaof.c
>> [127/235] Compiling librpc/src/xdr/xdr_array.c
>> ../../telnetd/check_passwd.c:70:10: fatal error: rtems/telnetd.h: No
>> such file or directory
>> 70 | #include <rtems/telnetd.h>
>> | ^~~~~~~~~~~~~~~~~
>> compilation terminated.
>>
>> ../../telnetd/telnetd.c:57:10: fatal error: rtems/telnetd.h: No such
>> file or directory
>> 57 | #include <rtems/telnetd.h>
>> | ^~~~~~~~~~~~~~~~~
>> compilation terminated.
>>
>> Waf: Leaving directory
>> `/home/junkes/MVME6100_testing/legacyNet/build/powerpc-rtems6-beatnik'
>> Build failed
>> -> task in 'network_objects' failed with exit status 1 (run with -v to
>> display more information)
>> -> task in 'network_objects' failed with exit status 1 (run with -v to
>> display more information)
>>
>> Heinz
- Replies:
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
- References:
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Joel Sherrill via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Heinz Junkes via Core-talk
- Navigate by Date:
- Prev:
Re: ANN: RTEMS libnetworking relocation Michael Davidsaver via Core-talk
- Next:
Re: ANN: RTEMS libnetworking relocation Vijay Kumar Banerjee via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Heinz Junkes via Core-talk
- Next:
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
|
ANJ, 03 Mar 2021 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|