9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ryan Gonzalez <rymg19@gmail.com>
To: Vasudev Kamath <vasudev@copyninja.info>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Compiling ken-cc on Linux
Date: Sun, 29 Nov 2015 08:38:44 -0600	[thread overview]
Message-ID: <40956B2C-0BF4-4787-AA5C-69D76694D608@gmail.com> (raw)
In-Reply-To: <87k2p1w3ae.fsf@rudra.copyninja.info>



On November 29, 2015 3:41:45 AM CST, Vasudev Kamath <vasudev@copyninja.info> wrote:
>Ryan Gonzalez <rymg19@gmail.com> writes:
>
>>>That took compilation further but now it breaks at point 4 in your
>>>issue. I hope I won't encounter more new issues :-).
>>>
>>
>> Ah, yes, I completely forgot about that part. :/ Good luck with the
>> rest of the compilation! You'll need it!
>
>Yes indeed. Now I'm having following error, after applying patch you
>mentioned in the comment.
>
>cc -m32  -o o.out y.tab.o lex.o
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libcc.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libbio.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/lib9.a
>
>(cd 6c; mk  all)
>mk: no recipe to make 'div.o'
>
>So there is no div.c under src/cmd/6c. I see that old mkfile mkfile_o
>has div.c but I don't know where original source file went. Removing
>div.$O\ from mkfile gives the following error.
>
>cc -m32  -o o.out cgen.o enam.o list.o mul.o peep.o reg.o sgen.o swt.o
>txt.o pswt.o pgen.o
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libcc.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libbio.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/lib9.a
>
>cgen.o: In function `cgen':
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:320:
>undefined reference to `sdiv2'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:323:
>undefined reference to `smod2'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:425:
>undefined reference to `sdivgen'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:427:
>undefined reference to `udivgen'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:632:
>undefined reference to `sdiv2'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:635:
>undefined reference to `smod2'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:759:
>undefined reference to `sdivgen'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:762:
>undefined reference to `udivgen'
>collect2: error: ld returned 1 exit status
>mk: cc -m32  ...  : exit status=exit(1)
>mk: for j in ...  : exit status=exit(1)
>mk: for j in ...  : exit status=exit(1)
>
>In both case I'm hitting dead end. Any hints for going forward?.

Well, the 6* compilers don't work ATM anyway, so I think you can just comment out the relevant lines in src/cmd/mkfile.
-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.



  reply	other threads:[~2015-11-29 14:38 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 17:10 Vasudev Kamath
2015-11-25 17:15 ` Ryan Gonzalez
2015-11-25 17:24   ` Vasudev Kamath
2015-11-26 12:08     ` Charles Forsyth
2015-11-27 16:50   ` Vasudev Kamath
2015-11-27 16:59     ` Ryan Gonzalez
2015-11-27 17:16       ` Vasudev Kamath
2015-11-27 18:24         ` Ryan Gonzalez
2015-11-29  9:41           ` Vasudev Kamath
2015-11-29 14:38             ` Ryan Gonzalez [this message]
2015-11-27 18:11   ` trebol
2015-11-26 12:10 ` Charles Forsyth
2015-11-26 12:18   ` David du Colombier
2015-11-26 18:15   ` Ryan Gonzalez
2015-11-26 21:31     ` Charles Forsyth
2015-11-26 21:49       ` Ryan Gonzalez
2015-11-26 21:51         ` Charles Forsyth
2015-11-26 21:56           ` Charles Forsyth
2015-11-26 22:02             ` Ryan Gonzalez
2015-11-26 22:08               ` Charles Forsyth
2015-11-26 22:30                 ` David du Colombier
2015-11-26 23:08                   ` Ryan Gonzalez
2015-11-26 23:21                     ` Charles Forsyth
2015-11-26 23:41                       ` Ryan Gonzalez
2015-11-27  0:02                       ` Brantley Coile
2015-11-27  8:13                       ` Giacomo Tesio
2015-11-27  8:56                         ` arnold
2015-11-27 13:33                           ` Steffen Nurpmeso
2015-11-28  0:55                             ` erik quanstrom
2015-11-30 15:46                               ` Steffen Nurpmeso
2015-11-27 12:42                         ` tlaronde
2015-11-27 14:07                           ` Giacomo Tesio
2015-11-27 14:34                             ` tlaronde
2015-11-28  1:01                             ` erik quanstrom
2015-11-27 12:05                       ` Steffen Nurpmeso
2015-11-27 12:32       ` lucio
2015-11-26 21:40     ` Andrew Simmons
2015-11-28  6:42 da Tyga
2015-11-28  7:40 ` Brantley Coile
2015-11-28 20:31   ` Anthony Sorace
2015-11-28 23:33     ` Brantley Coile
2015-11-29  6:12       ` lucio
2015-11-28 20:13 ` Ryan Gonzalez
2015-11-29  5:57   ` lucio
2015-11-29 16:17     ` tlaronde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40956B2C-0BF4-4787-AA5C-69D76694D608@gmail.com \
    --to=rymg19@gmail.com \
    --cc=9fans@9fans.net \
    --cc=vasudev@copyninja.info \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).