X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Received: by 2002:ac8:39c2:: with SMTP id v60mr26364448qte.384.1588048798157; Mon, 27 Apr 2020 21:39:58 -0700 (PDT) X-Received: by 2002:a25:8105:: with SMTP id o5mr42702766ybk.32.1588048797764; Mon, 27 Apr 2020 21:39:57 -0700 (PDT) Newsgroups: comp.os.msdos.djgpp Date: Mon, 27 Apr 2020 21:39:57 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse AT google DOT com Injection-Info: google-groups.googlegroups.com; posting-host=2607:fea8:a480:1b4:594d:db9e:36d8:171e; posting-account=DTw6mgoAAABVKmwnaJ8FE6P8zb_HY_u- NNTP-Posting-Host: 2607:fea8:a480:1b4:594d:db9e:36d8:171e References: <8af0ebdd-acea-a7be-3388-d295af50bfc7 AT gmail DOT com> <708c79a5-c5f4-4144-8d02-0f2a0497c441 AT googlegroups DOT com> <6431e105-dfc5-440b-8aa5-382bab083466 AT googlegroups DOT com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Issues using DJGPP with Rust From: "noname422 AT gmail DOT com [via djgpp AT delorie DOT com]" Injection-Date: Tue, 28 Apr 2020 04:39:58 +0000 Content-Type: text/plain; charset="UTF-8" Bytes: 3729 Lines: 69 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 03S4jIpP026085 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Monday, April 27, 2020 at 6:18:11 PM UTC-4, Sébastien GUILLAUME wrote: > Le lundi 27 avril 2020 21:02:22 UTC+2, nona DOT DOT DOT AT gmail DOT com a écrit : > > On Monday, April 27, 2020 at 1:33:59 PM UTC-4, Sébastien GUILLAUME wrote: > > > Hi, nice idea. > > > I have read your conversation in github. > > > Can you post here the result of the file command applied to files you try to link? > > > Remember that djgpp use coff format, which is different from PE for Windows and different to elf to. > > > PE is descendent of coff, they have some common parts. Weird functions address can come from here. > > > > I ran it on one of the object files for my program and this is what I got. > > > > dos32-dcb1f62a4632e187.dos32.frqh9yy0-cgu.0.rcgu.o: Intel 80386 COFF object file, > > not stripped, 4 sections, symbol offset=0x234, 15 symbols > > wich compiler made this files ? > > I don't know how to switch to nightly rust, gentoo doesn't give rustup package, so I can't build the rust part. > > This is what I gave when I try to compile startup.c with this command line : > $ i586-pc-msdosdjgpp-gcc -c startup.c -o startup.o > $ file startup.o > startup.o: Intel 80386 COFF object file, no line number info, not stripped, 5 sections, symbol offset=0x19c, 16 symbols > $ i586-pc-msdosdjgpp-strings -tx startup.o > 14 .text > 3c .data > 64 .bss > 8c .comment > 11c GCC: (GNU) 7.2.0 > 19c .file > 1ae startup.c > 1c0 .text > 1e4 .data > 208 .bss > 22c .comment > 274 _main > 298 _exit > 2c0 .eh_frame > 2ca .eh_frame > 2d4 ___djgpp_nearptr_enable > 2ec _rust_main > > We can see that we have different number of section and symbols. It can be something interesting. > > What do you have with your tools? > > To realise my test, I used : > - GNU Binutils 2.29 > - GCC 7.2.0 > - file-5.37 > - rustc 1.41.1 > - cargo 1.41.0 I'm using a nightly build of Rust and Cargo. GCC and binutils are from DJGPP built and gotten from here: https://github.com/andrewwutw/build-djgpp It's the GCC 7.2.0 version.