Re: Who is responsible for Newlib/vbcc ?
Posted: Mon May 23, 2016 6:50 pm
For my case, I still use gcc, no vbcc
Support Forum
https://forum.hyperion-entertainment.com/
https://forum.hyperion-entertainment.com/viewtopic.php?f=27&t=3424
I should have directed my comment to phx since he was the one compiling with vbcc.zzd10h wrote:For my case, I still use gcc, no vbcc
Actually, I was the person compiling with VBCC and reported this elf message. Phx is the person updating the VBCC. If I understood correctly, Frank has located the problem to newlib (for example, launching AmiPDF generates this error message and also the message above indicates this is not a problem only for users of VBCC).xenic wrote:I should have directed my comment to phx since he was the one compiling with vbcc.zzd10h wrote:For my case, I still use gcc, no vbcc
Pardon my confusion over who is who here. However, I tried running AmiPDF with Sashimi running and didn't see any messages. I even switched to the debug kernal, performed a cold reboot and still don't see any message in Sashimi when starting AmiPDF. Others have reported that they don't see the message either, so there must be something different about your system setup.blmara wrote:Actually, I was the person compiling with VBCC and reported this elf message. Phx is the person updating the VBCC. If I understood correctly, Frank has located the problem to newlib (for example, launching AmiPDF generates this error message and also the message above indicates this is not a problem only for users of VBCC).xenic wrote:I should have directed my comment to phx since he was the one compiling with vbcc.zzd10h wrote:For my case, I still use gcc, no vbcc
Marko
The AmigaOS development team looks after all the components as a collective. There are various members that specialize in pieces of the OS but everyone is welcome and able to work on any component. There is not one person who is the newlib maintainer.blmara wrote:Really, are there people developing newlib.library?
Great to hear both that the reason for this issues was found and it wasn't actually harmful. Thanks!salass00 wrote:The issue with the startup.o file used by vbcc has just been fixed in the latest newlib beta version with some help from Frank Wille (AKA phx) who is the maintainer of the AmigaOS vbcc ports.
As said before the issue wasn't harmful in any way and only showed itself when debuglevel was set higher than zero, which it really it shouldn't be for most people. The pretty much only reason to have a debug level higher than zero is if you are debugging the kernel or some other system component which is affected by this setting. If you are not using it to debug system components then you're just making the OS slower for no real reason.
So, "SERIAL MUNGE DEBUGLEVEL=5" does not help debugging problems in programs but only helps debugging stuff in OS components and kernel?salass00 wrote:The issue with the startup.o file used by vbcc has just been fixed in the latest newlib beta version with some help from Frank Wille (AKA phx) who is the maintainer of the AmigaOS vbcc ports.
As said before the issue wasn't harmful in any way and only showed itself when debuglevel was set higher than zero, which it really it shouldn't be for most people. The pretty much only reason to have a debug level higher than zero is if you are debugging the kernel or some other system component which is affected by this setting. If you are not using it to debug system components then you're just making the OS slower for no real reason.
Yes, I know and I am happy that you have helped to solve the issue even if the compiler is not the official one.ssolie wrote:...
In this case, vbcc is a 3rd party compiler and we do not test with it. If something happens to break with vbcc for some reason we will try to work it out but it is not the officially supported compiler. GCC is the officially supported compiler and we always test with that one.
Certainly not! Using the "debug" kernel is essential if you are doing any sort of program debugging - OS components or otherwise."SERIAL MUNGE DEBUGLEVEL=5" does not help debugging problems in programs but only helps debugging stuff in OS components and kernel?