public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Paterson <dnpaterson@gmail.com>
To: Me Myself and I <stargate7thsymbol@live.co.uk>
Cc: gcc-help@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: GCJ building
Date: Tue, 13 Mar 2012 12:26:00 -0000	[thread overview]
Message-ID: <CAM1kHc3XOYtDA5eSa3xkk7j3=QR3khNgHOsjuFUBCgnytdkRBw@mail.gmail.com> (raw)
In-Reply-To: <BAY147-W656DE7DA526DB6357B08AFD0580@phx.gbl>

On 13 March 2012 03:17, Me Myself and I <stargate7thsymbol@live.co.uk> wrote:
>
> But the thing is that I havn't, my objdir exists one cd ..
> step back, outside my gcc-4.6.2 directory, despite what this error message says.

OK, against my better judgement, I'll try one more time.

You're either copying messages from older posts, thinking the say the
same as you see on your screen, or you're not typing the commands you
should be (and think you are).

"Feel free to follow along with my simple step-by-step instructions. I
make building FUN!!"
"To begin draw an S, for snake. or GCC. Er, whatever."

Erm, sorry :-)

Anyway, try the following commands :-

    $ cd ~

You should now be in your home directory...

    $ mkdir alice

    $ cd alice

    $ pwd
    /home/davidp/alice

OK - now unpack GCC into this directory.  DO NOT COPY from your old
build attempts - unpack / unzip the original download.
If you copy the old source tree you will probably get errors again, as
it's probably corrupt.

    $ ls
    gcc-4.6.2

Get the other bits you want to build

    $ cd gcc-4.6.2
    $ ./contrib/download_prerequisites

Return to the previous directory

    $ cd ..
    $ pwd
    /home/davidp/alice

NOTE - if you are not in directory "alice" then the following steps
will not work, and you will likely get the same errors as before

Now create a directory to build in

    $ mkdir bob
    $ cd bob
    $ pwd
    /home/davidp/alice/bob

    $ ls
    bob  gcc-4.6.2

NOTE - double check the directory you're now in.  It should NOT be
anywhere under gcc-4.6.2.

Now we can build...

    $ ../gcc-4.6.2/configure

followed by

    $ make

Follow these steps, and if the build doesn't work (again) then copy
the error messages from your console window, not from previous emails.

With these steps there should NOT be any occurence of "objdir"
anywhere in the source or object trees.

Regards,

David P.

  reply	other threads:[~2012-03-13 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09  2:38 GCJ gen-fib information Me Myself and I
     [not found] ` <CAM1kHc1PkRUCkgFOpgcNhAXau36uC5E1q9cvHA4ZC5JuV-wFWg@mail.gmail.com>
2012-03-11 23:51   ` GCJ building Me Myself and I
2012-03-12 10:41     ` David Paterson
2012-03-12 21:30       ` Me Myself and I
     [not found]         ` <4F5E7971.4050408@digium.com>
2012-03-13  3:17           ` Me Myself and I
2012-03-13 12:26             ` David Paterson [this message]
2012-03-14  0:13               ` Me Myself and I
2012-03-14  1:44                 ` Ian Lance Taylor
     [not found]                 ` <CAH6eHdSbP4q8-y7q5=b2R3Szr0RHfxfP2rRWqYCTRV5FsiDxCA@mail.gmail.com>
2012-03-14  4:34                   ` Me Myself and I
2012-03-14  9:14                 ` David Paterson
2012-03-14 12:40                   ` Chris Burdess

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='CAM1kHc3XOYtDA5eSa3xkk7j3=QR3khNgHOsjuFUBCgnytdkRBw@mail.gmail.com' \
    --to=dnpaterson@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    --cc=stargate7thsymbol@live.co.uk \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).