From: trebol <trebol@india.com >
To: 9fans@9fans.net
Subject: Re: [9fans] Compiling ken-cc on Linux
Date: Fri, 27 Nov 2015 18:11:14 +0000 [thread overview]
Message-ID: <56589cc2.LKJWOzoKCAdGPijl%trebol@india.com> (raw)
In-Reply-To: <CAO41-mPCSHYQagRRu9kcDFLtNzRWPbPK-qQnqmipGkgWwfCy8Q@mail.gmail.com>
Ryan Gonzalez <rymg19@gmail.com> wrote:
> See
> https://bitbucket.org/plan9-from-bell-labs/9-cc/issues/1/problems-building-under-x64-linux
> for some tips on fixing various errors you may encounter, including this
> one. (I opened that issue like 8 months ago...)
>
> On Wed, Nov 25, 2015 at 11:10 AM, Vasudev Kamath <vasudev@copyninja.info>
> wrote:
>
> >
> > Hi,
> >
> > I'm trying to compile ken-cc from ¹. Its giving me following error
> >
> > cc -c -m32 -g -O
> > -I/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/include
> > -I/home/vasudev/Documents/C_programming/compilers/9-cc/include -DLINUX_386
> > -I../cmd/ 9obj.c
> > In file included from
> > /home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/include/lib9.h:9:0,
> > from 9obj.c:5:
> > /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and
> > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> > # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
> > _DEFAULT_SOURCE"
> > ^
> > 9obj.c:8:22: fatal error: 9c/9.out.h: No such file or directory
> > compilation terminated.
> > mk: cc -c -m32 ... : exit status=exit(1)
> > mk: for j in ... : exit status=exit(1)
> >
> > I can't find 9c under src/cmd folder. Any hints on how to get it
> > compiled?.
> >
> > Cheers,
> >
> > ¹ https://bitbucket.org/plan9-from-bell-labs/9-cc/overview
> >
> >
>
>
> --
> Ryan
> [ERROR]: Your autotools build scripts are 200 lines longer than your
> program. Something’s wrong.
> http://kirbyfan64.github.io/
h+
h+
next prev parent reply other threads:[~2015-11-27 18:11 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
2015-11-27 18:11 ` trebol [this message]
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=56589cc2.LKJWOzoKCAdGPijl%trebol@india.com \
--to=trebol@india.com \
--cc=9fans@9fans.net \
/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).