Having some issues with symbol visibility. I don't know, if there is a bug in there, but code seems to need -fvisibility=hidden, which seems odd.
Q: What does 'Ndx' in readelf output stand for, and why does the runtime linker deliberately choose the first instance (the upper line) of the symbol over the second, when it should in a perfect world choose the lower?
Num: Value Size Type Bind Vis Ndx Name
686: 00000000 0 OBJECT GLOBAL DEFAULT UND _ZN10QArrayData11shared_nullE
53: 00000004 32 OBJECT GLOBAL DEFAULT 23 _ZN10QArrayData11shared_nullE
(NB: They are from two different objects; an executable and a shared object.)
To answer my own question: Ndx means the section, where the symbol is found. 'UND' means undefined, in which case the linker (in this case elf.library) should look elsewhere for the value of the symbol.
When executing the app, QArrayData::shared_null will come out as 0x0. The only explanation seems to be, that it has been linked to the first 'UND' version of the symbol.
In other words: This looks like a bug in the runtime linker. Aggree? ----
When executing the app, QArrayData::shared_null will come out as 0x0. The only explanation seems to be, that it has been linked to the first 'UND' version of the symbol.
Does that happen all the time? Or just at random? I've seen something vaguely similar with a python module (__ssl.so from os4depot ) occasionally crashing due to a symbol being NULL.
The odd things is it works mosts times.
The really odd thing is that it only crashes for me shortly after running Odyssey.
BTW I would think it more likely that the undefined symbol is the one that hasn't been linked, hence the NULL when accessed. (Unless there's a third reference to it that you haven't quoted to get mislinked to the first)
It appears to allow line continuation, but the second line is not added to the command.
[edit]
Found the RUN doc it does work here for 'run', not for ordinary commands inline
12.AmigaOS4:> echo "this doesn't work" + echo "see?" this doesn't work 12.AmigaOS4:> run echo "but this does" + echo "needs space before the + though" but this does [CLI 9] needs space before the + though 12.AmigaOS4:>
I am trying to commit my codebase to github using sgit.
I have checked out my master branch sucessfully. Then I have copied all files from my work directory (which is different - yes I know it is silly).
Then I try sgit commit -m "blabla" and sgit push origin master. None of these do anything. Sgit status gives a list of the files I changed with a note saying 'changes not staged for commit'.
You have to stage files first for commit by using the "git add" command.
If you just want to commit all changes it's easiest to just run "git add ." in the root of the git repository to add all files. If there are files you don't want to commit in there you should create ".gitignore" file first.
For instance for SRec I have the following in its .gitignore: Quote:
I was thinking... because of all these issues, I might want to switch to a cross compiler. Is there an 'easy' way to connect my MacMini to the X1000, so I get access to the Amiga's file system from the Mac? I would love to be able to do something like
make install INSTALL_ROOT=/Volumes/AmigaOS-HD/path
@alfkil Cross compiler are right way 100%. Easy and fast :)
Dunno about macos, but on windows i always use samba to share stuff between amiga/windows. I do not remember through if i mount amiga partitions on windows or another way, but one of them works for sure.
Also you can install mui's ftpd (RC-FTPd) on x1000 (that one easy to setup, and that one i used much and it prove to be working without crashes), and just use it from your mac. On windows there is some tools which allow you to mount as one more partition your ftp access, so it looks like usuall partition (probably that what you need). But dunno if there is any for macos.
Samba on the Mac OS side refuses to connect because 'server' is not running a supported version of the network software. On the Amiga side it just says 'Connection refused' for unknown reasons.
I think I will give up and try ftp instead. Any hints will be cherised.