IRC channel logs
2025-04-05.log
back to list of logs
<almuhs>I'm compiling with gcc -g caesar_trans.c -o caesar_trans -ltrivfs -lports <almuhs>/usr/bin/ld: /tmp/ccn1nwJU.o: undefined reference to symbol '__assert_perror_fail_backtrace' <almuhs>/usr/bin/ld: /lib/i386-gnu/libshouldbeinlibc.so.0.3: error adding symbols: DSO missing from command line <almuhs>collect2: error: ld returned 1 exit status <almuhs>gcc -g caesar_trans.c -o caesar_trans -ltrivfs -lports -lshouldbeinlibc <damo22>almuhs: rot26, twice as strong as rot13 <almuhs>pruebas@debian-hurd:~$ settrans -gac /tmp/c caesar_trans example_file <almuhs>pruebas@debian-hurd:~$ cat /tmp/c <almuhs>i'm trying a translator example written by Sergey some months ago <almuhs>kern_return_t trivfs_S_io_write (struct trivfs_protid *cred, mach_port_t reply, mach_msg_type_name_t replytype, data_t data, mach_msg_type_number_t datalen, loff_t offs, mach_msg_type_number_t *amout) <almuhs>kern_return_t trivfs_S_io_write (struct trivfs_protid *cred, mach_port_t reply, mach_msg_type_name_t replytype, const char* data, mach_msg_type <damo22>almuhs: nonsense output is probably correct, its supposed to be a poor form of encryption <almuhs>this latest example is not the caesar <almuhs>this include a translator example using libtrivfs <almuhs>now it prints 11111... correctly <Pellescours>according to the comment it is only required for i386, so 64 bit mode should also be excluded <Pellescours>I think it should be updated to #if __i366__ && !(__i486__ ...) <azeem>you didn't mention a line number <youpi>oh sure, please send a patch <youpi>and also a bit above the call in trap.c <Pellescours>I won't be able to do it until tomorrow, so if someone want/have time, feel free. Otherwise I'll do it tomorrow :D <hakanrw_>hello! is gnu mach currently able to do SMP on x86_64 at all, or is it limited to i386? <AlmuHS>hakanrv_ : the SMP is limited to i386. Currently we're trying to fix some race conditions