Legacy Networking | Legacy network build failed for spar/erc32 (#24)

[Vijay Banerjee (@vijay)]

Vijay Banerjee created an issue: https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy/-/issues/24



## Summary
Recently, in !447, the `set_vector` was removed from multiple architectures, including `sparc`. Some legacy network drivers still use the `set_vector` function, which breaks the legacy network build.
 
## Steps to reproduce

In net-legacy, a normal build process using
```
./waf configure prefix=$RTEMS_PREFIX --rtems-bsps=sparc/erc32
./waf
```


The issue can be resolved by replacing the set_vector call with `rtems_interrupt_handler_install` as done in the following commit https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/447/diffs?commit_id=a899cdd57d132f17d05c52b5de9a842690e1ce11#70f8a217ec9526398c222fd80cc4c3840f0c1393

### Pre-set options

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy/-/issues/24
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20251006/41adb4b4/attachment.htm>