Who's Online |
21 user(s) are online ( 13 user(s) are browsing Forums)
Members: 0
Guests: 21
more...
|
|
|
|
Re: continue.dev package for AmigaOS dev?
|
Posted on: 6/22 10:42
#221
|
Not too shy to talk 
|
Well i think the point would be to have a bundle that allows for LLM's to have a reference for things they do not 'know' from their training, avoiding hallucination of APIs that don't exist, and knowledge of new APIs for which there wasn't much training material to work from or for third party APIs to be more readily in scope of the LLM. For example Claude knows AmigaOS 3.1 very well and 4 quite well. But does it know anything about additions in OS3.2, or how to use AmiSSL? No it does not. Using continue.dev should fix that. and it needs to be constantly reminded to use latin1, C89 etc and not veer off into assuming POSIX and more is acceptable.
|
|
|
|
Re: How to use clib4 (natively)?
|
Posted on: 6/22 9:55
#222
|
Home away from home 
|
@Chris Quote: libnix is more sane but IIRC is missing quite a bit of stuff.
clib2 is preferable to both, especially as it's not trying to be UNIX. Gunther's libnix doesn't try to be UNIX/POSIX compatible either. Only ixemul did try that, incl. functions like (ix_)vfork(|2|_setup_child)(), etc. A vfork() implementation is partially possible on AmigaOS, with several restrictions, but implementing a fork() function is impossible on any version of AmigaOS. libnix is a very simple and limited C library, enough for most native AmigaOS software, but not usable for porting UNIX software to AmigaOS.
|
|
|
|
Re: How to use clib4 (natively)?
|
Posted on: 6/22 9:17
#223
|
Home away from home 
|
@kas1e If you insist on using a crap single-system C library instead of something much better and multi-platform (doesn't have to be newlib, there are others, but less advanced ones, as well) at least merge clib4 with the AROS C library to get a few more developers on board. Just browsed the clib4 sources a bit, and there is still a lot, way too much, crap from clib2 remaining. Very simple example: https://github.com/AmigaLabs/clib4/blob/master/library/stdio/lock.cJust replacing the old, and probably only used for the AmigaOS 1.x-3.x compatibility of clib2, semaphores (based on Forbid()/Permit()!) by OS4 mutexes (based on atomic increment/decrement instructions) should result in a noticeable speed improvement.
|
|
|
|
Re: continue.dev package for AmigaOS dev?
|
Posted on: 6/22 9:09
#224
|
Site Builder 
|
That is interesting. What would it mean to have that working out of development and cost?
|
|
|
|
Re: Updating system
|
Posted on: 6/22 8:59
#225
|
Quite a regular 
|
Hanging on a white screen is what happens when you are using a card that needs the more recent radeon drivers, but the flash drive only has the older one or limited one.
You either have to 1. put the more recent driver on the flash drive or 2. ensure you have an older gfx card.
No one should have to go through this, but it is what it is.
A serial cable is also important since we could confirm that all of this started because of the modification to the kicklayout. It would then also have confirmed that your new issue is the issue with the gfx driver.
Regardless, you will need to boot into the flash drive and so it would be important to know which card you have.
|
If liberty means anything at all, it means the right to tell people what they do not want to hear. George Orwell.
|
|
|
Re: need clarify about libdl and all dlopen/dlclose calls
|
Posted on: 6/22 8:43
#226
|
Home away from home 
|
@Hans Quote: EDIT: And the libdl.a on os4depot causes missing IElf symbol errors. Non-functional... If elf.library support isn't included in libauto simply open it and the IElf interface yourself. libdl.a is probably simply redirecting the functions to IElf->DLOpen(), DLSym() and DLClose(). But as I wrote it can only work for very simple shared objects/plugins which don't need to call functions from the statically linked main executable nor from statically linked libraries.
|
|
|
|
Re: How to use clib4 (natively)?
|
Posted on: 6/22 3:26
#227
|
Home away from home 
|
@joerg Quote: Re-implementing an AmigaOS 4.x port of newlib: Not possible for me because of my contract and NDA with Hyperion.
clib2/clib4: Doesn't make any sense for me, clib2 was completely replaced by newlib (or at least should have been, according to my newlib contract). Fixing the most serious bugs in clib2 and adding missing features, instead of porting newlib, would have been an option about 20 years ago, but the developer of clib2 rejected any improvements I suggested. In the end I never used clib2 for any of my AmigaOS 4.x software, but ported and used libnix instead for all of my early AmigaOS 4.x software, before I did the newlib port.
As we already in situation where we are, at least your valuable knowledge may help us to improve clib4, even if you at least will point out us what and how to change to make be more or less on good. Currently all we need is to deal with slow console IO, slow file IO and slow formatting strings. Maybe you can remember your ideas what you point out on clbi2 back them and which were rejected, etc. Any help need it. Just starting now to replace everything in core of clib4 on newlib's code will be too much for Andrea's wish and time that for sure.
|
|
|
|
Re: How to use clib4 (natively)?
|
Posted on: 6/21 22:57
#228
|
Amigans Defender 
|
@joergQuote: joerg wrote:@Chris Quote:I use it for the OS3 port of NetSurf. The alternatives would never have worked. Using ixemul should still work, even if the last working m68k versions (47.x/48.x) are more than 25 years old by now. Just don't try to use the newer versions from Bernd Rösch, they are broken in several ways. I used ixemul for my AmigaOS 3.9/m68k port of OWB. Yes, it quite possibly would have done, but that's a horrid horrid piece of software I'd rather not touch with a barge pole. libnix is more sane but IIRC is missing quite a bit of stuff. clib2 is preferable to both, especially as it's not trying to be UNIX.
|
|
|
|
Re: Updating system
|
Posted on: 6/21 21:59
#229
|
Not too shy to talk 
|
duplicate post
|
|
|
|
Re: Updating system
|
Posted on: 6/21 21:59
#230
|
Not too shy to talk 
|
@SteffJay
Which SPECIFIC graphics card is this Asus Radeon? Could it be that the new USB stick lacks the necessary driver for a newish graphics card? We have a chicken and eggs situation going on with these systems sometimes.
|
|
|
|
Re: need clarify about libdl and all dlopen/dlclose calls
|
Posted on: 6/21 19:20
#231
|
Home away from home 
|
@Hans Quote: Removing libdl.a was a mistake. No. While it still might be possible to use dlopen(), etc. from libdl.a (or more directly IElf->DLOpen(), DLSysm(), DLClose() from elf.library) to load .so plugins, it's impossible for such .so plugins to call functions in the main executable on AmigaOS if the main executable wasn't build with -use-dynld. For example the audio, video, PDF, etc. plugins of my AmigaOS 4.x port of OWB, only theoretically supported since nobody ever implemented those plugins, depend on back-calls of functions in the main executable.
|
|
|
|
Re: Updating system
|
Posted on: 6/21 18:39
#232
|
Just popping in 
|
@rjd324 Its a ASUS Radeon one.
|
|
|
|
Re: Updating system
|
Posted on: 6/21 17:51
#233
|
Quite a regular 
|
Which gfx card? Could it be that the thumb drive is not using the radeon drivers that support your graphics card?
|
If liberty means anything at all, it means the right to tell people what they do not want to hear. George Orwell.
|
|
|
Re: How to use clib4 (natively)?
|
Posted on: 6/21 17:45
#234
|
Home away from home 
|
@flash Quote: The question is.. you have great skills and deep knowledge of AmigaOS internals, so I wonder why you don't join Andrea and others developers to build an open source alternative to all this mess? Re-implementing an AmigaOS 4.x port of newlib: Not possible for me because of my contract and NDA with Hyperion. clib2/clib4: Doesn't make any sense for me, clib2 was completely replaced by newlib (or at least should have been, according to my newlib contract). Fixing the most serious bugs in clib2 and adding missing features, instead of porting newlib, would have been an option about 20 years ago, but the developer of clib2 rejected any improvements I suggested. In the end I never used clib2 for any of my AmigaOS 4.x software, but ported and used libnix instead for all of my early AmigaOS 4.x software, before I did the newlib port.
|
|
|
|
Re: How to use clib4 (natively)?
|
Posted on: 6/21 17:28
#235
|
Just popping in 
|
@joerg
The question is.. you have great skills and deep knowledge of AmigaOS internals, so I wonder why you don't join Andrea and others developers to build an open source alternative to all this mess?
|
Memento audere semper!
|
|
|
Re: How to use clib4 (natively)?
|
Posted on: 6/21 17:01
#236
|
Home away from home 
|
@balaton Quote: Why does it need to be reimplemented? Couldn't you just release it under a similar licence as the rest of newlib then others could update it without having to start from scratch. My AmigaOS 4.x port of newlib was contract work for Hyperion, and the only one I was payed for completely. Hyperion has an exclusive licence for my AmigaOS 4.x parts of newlib. Hyperion could release it as open source, unfortunately I can't. The benefits of using a portable multi-platform C library like newlib, in which at least 99% of the code is system independent and worked on by developers of other systems as well, compared to AmigaOS-only C libraries like clib2 or clib4 with only a single developer working on it should be obvious.
|
|
|
|
Re: How to use clib4 (natively)?
|
Posted on: 6/21 16:06
#237
|
Home away from home 
|
@Chris Quote: I use it for the OS3 port of NetSurf. The alternatives would never have worked. Using ixemul should still work, even if the last working m68k versions (47.x/48.x) are more than 25 years old by now. Just don't try to use the newer versions from Bernd Rösch, they are broken in several ways. I used ixemul for my AmigaOS 3.9/m68k port of OWB.
|
|
|
|
Re: How to use clib4 (natively)?
|
Posted on: 6/21 11:14
#239
|
Home away from home 
|
@flash Quote: ..Waiting for new SDK release, tnx Walkero! The SDK addon is out now. See this threadHans
|
|
|
|
Re: SDK addon package
|
Posted on: 6/21 10:58
#240
|
Just can't stay away 
|
@walkero tested with a simple reaction gui and wotks finer using clib4.
#gcc -Wall -N testreaction3.c -o TestReAction3 -lauto -mcrt=clib4 -v
Using built-in specs.
COLLECT_GCC=/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/gcc
COLLECT_LTO_WRAPPER=/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../libexec/gcc/ppc-amigaos/11.3.0/lto-wrapper
Target: ppc-amigaos
Configured with: /opt/adtools/gcc/repo/configure --with-bugurl=https://github.com/sba1/adtools/issues --with-pkgversion='adtools build 11.3.0' --host=ppc-amigaos --target=ppc-amigaos --disable-nls --prefix=/gcc --with-gmp=/opt/adtools/native-build/root-cross --with-mpfr=/opt/adtools/native-build/root-cross --with-mpc=/opt/adtools/native-build/root-cross --program-prefix=ppc-amigaos- --program-suffix=-11 --libexecdir=/gcc/libexec --enable-languages=c,c++ --enable-haifa --enable-sjlj-exceptions --disable-libstdcxx-pch --disable-tls --enable-threads=amigaos --enable-lto --disable-c++tools
Thread model: amigaos
Supported LTO compression algorithms: zlib
gcc version 11.3.0 (adtools build 11.3.0)
COLLECT_GCC_OPTIONS='-Wall' '-N' '-o' 'TestReAction3' '-mcrt=clib4' '-v' '-dumpdir' 'TestReAction3-'
/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../libexec/gcc/ppc-amigaos/11.3.0/cc1 -quiet -v -imultilib clib4 -iprefix /Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/ -idirafter /SDK/clib4/include -idirafter /SDK/local/clib4/include -idirafter /SDK/include/include_h -idirafter /SDK/include/netinclude -idirafter /SDK/local/common/include testreaction3.c -quiet -dumpdir TestReAction3- -dumpbase testreaction3.c -dumpbase-ext .c -mcrt=clib4 -Wall -version -o /tmp/ccJ7IQ3Z.s
GNU C17 (adtools build 11.3.0) version 11.3.0 (ppc-amigaos)
compiled by GNU C version 11.3.0, GMP version 5.1.3, MPFR version 3.1.6, MPC version 1.0.3, isl version none
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
ignoring nonexistent directory "/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/../../../../ppc-amigaos/include"
ignoring duplicate directory "/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../lib/gcc/ppc-amigaos/11.3.0/include"
ignoring duplicate directory "/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../lib/gcc/ppc-amigaos/11.3.0/include-fixed"
ignoring nonexistent directory "/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../lib/gcc/ppc-amigaos/11.3.0/../../../../ppc-amigaos/include"
ignoring nonexistent directory "/SDK/local/clib4/include"
#include "..." search starts here:
#include <...> search starts here:
/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/include
/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/include-fixed
/gcc/include
/SDK/clib4/include
/SDK/include/include_h
/SDK/include/netinclude
/SDK/local/common/include
End of search list.
GNU C17 (adtools build 11.3.0) version 11.3.0 (ppc-amigaos)
compiled by GNU C version 11.3.0, GMP version 5.1.3, MPFR version 3.1.6, MPC version 1.0.3, isl version none
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: e410ff90f92477c41a505851d1540446
testreaction3.c: In function 'Process_GUI':
testreaction3.c:225:16: warning: unused variable 'res_value' [-Wunused-variable]
225 | res_value = 0;
| ^~~~~~~~~
COLLECT_GCC_OPTIONS='-Wall' '-N' '-o' 'TestReAction3' '-mcrt=clib4' '-v' '-dumpdir' 'TestReAction3-'
as -mppc -many -mbig -o /tmp/ccN5YX1d.o /tmp/ccJ7IQ3Z.s
COMPILER_PATH=/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../libexec/gcc/ppc-amigaos/11.3.0/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../libexec/gcc/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../libexec/gcc/ppc-amigaos/11.3.0/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../libexec/gcc/ppc-amigaos/11.3.0/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/../../libexec/gcc/
LIBRARY_PATH=/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/clib4/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/clib4/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/clib4/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/../../../:/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/../../../
COLLECT_GCC_OPTIONS='-Wall' '-N' '-o' 'TestReAction3' '-mcrt=clib4' '-v' '-dumpdir' 'TestReAction3.'
ld --defsym __amigaos4__=1 -Bstatic -q -d -V -Qy -L/SDK/clib4/lib -L/GCC/lib/gcc/ppc-amigaos/11.3.0/clib4/lib -L/SDK/local/clib4/lib -L/SDK/local/common/lib -o TestReAction3 -N /SDK/clib4/lib/crtbegin.o /SDK/clib4/lib/crt0.o -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/clib4 -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/clib4 -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/clib4 -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0 -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0 -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0 -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/../../.. -L/Devel/SDK/gcc/ppc-amigaos/bin/11.3.0/../lib/gcc/ppc-amigaos/11.3.0/../../.. /tmp/ccN5YX1d.o -lauto -lgcc -lgcc_eh --start-group -lc --end-group -lgcc -lgcc_eh /SDK/clib4/lib/crtend.o
GNU ld (GNU Binutils) 2.23.2
Supported emulations:
amigaos
elf32ppc
COLLECT_GCC_OPTIONS='-Wall' '-N' '-o' 'TestReAction3' '-mcrt=clib4' '-v' '-dumpdir' 'TestReAction3.'
#gcc -Wall -N testreaction3.c -o TestReAction3 -lauto -mcrt=clib4
testreaction3.c: In function 'Process_GUI':
testreaction3.c:225:16: warning: unused variable 'res_value' [-Wunused-variable]
225 | res_value = 0;
| ^~~~~~~~~
|
|
|
|