public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: stevepr@crt.com
To: gcc-help@gnu.org
Cc: lat@cns.vt.edu
Subject: RE: AIX, gcc-2.95.1, and alloca -buildm error
Date: Thu, 14 Oct 1999 08:53:00 -0000	[thread overview]
Message-ID: <F931488C3634D11180D700A02461E2450201C8BD@chitmd03.nt.il.nbgfn.com> (raw)

> Laruie,
>  I have gotten gcc to build and install on aix.
> 
>  cd into some dir
>  gunzip -c gcc-2.95.1.tar.gz | tar xvf -
>  mkdir aix-gcc
>  cd aix-gcc
>  export $MAKE={ path to gnu make, I used 3.78.1, gnu make may be required
> and
>  xlc will build it }
>  ../gcc-2.95.1/configure --enable-languages=c,c++
>  $MAKE bootstrape
>  $MAKE -k check
>  $MAKE info
>  $MAKE install
> 
>  This will also build the stdlibc++.a.2.10.0 which contains the stl for
> c++.
> 
>  Good luck.
> 
>  Steve Pribyl
> 
> 
> > > -----Original Message-----
> > > From: Laurie Zirkle [SMTP:lat@cns.vt.edu]
> > > Sent: Tuesday, October 05, 1999 1:32 PM
> > > To: stevepr@crt.com
> > > Subject: Re: Your message to gcc-help
> > >
> > > I went poking thru the AIX faq and found this tidbit; maybe it will
> help
> > > you
> > > (I don't have time to try again today).
> > >
> > >      Subject: 2.01: I cannot make alloca work
> > >
> > >      A famous routine, in particular in GNU context, is the allocation
> > >      routine alloca().  Alloca allocates memory in such a way that it
> is
> > >      automatically free'd when the block is exited.  Most
> implementations
> > >      does this by adjusting the stack pointer.  Since not all C
> > > environments
> > >      can support it, its use is discouraged, but it is included in the
> xlc
> > >      compiler.  In order to make the compiler aware that you intend to
> use
> > >      alloca, you must put the line
> > >
> > >      #pragma alloca
> > >
> > >      before any other statements in the C source module(s) where
> alloca
> is
> > >      called.  If you don't do this, xlc will not recognize alloca as
> > > anything
> > >      special, and you will get errors during linking.
> > >
> > >      For AIX 3.2, it may be easier to use the -ma flag.
> > >
> > >
> > >
> > > From the fingers of stevepr@crt.com:
> > > > Nope not yet.
> > > >
> > > > However I have found that there may be some issues with the native
> make
> > > > program.  I have tried the gnu make,  It seems to work better, still
> > > fails
> > > > but at a different point.
> > > >
> > > > I will be sure to post what ever answer I get.
> > > > Steve Pribyl
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Laurie Zirkle [SMTP:lat@cns.vt.edu]
> > > > > Sent: Tuesday, October 05, 1999 7:32 AM
> > > > > To: stevepr@crt.com
> > > > > Subject: Your message to gcc-help
> > > > >
> > > > > Have you received any responses yet?  I have the exact same
> problem
> > > trying
> > > > > to compile gcc under AIX 4.3.2 using cc.  I didn't see an answer
> to
> > > the
> > > > > list yet.
> > > > >
> > > > > --
> > > > > Laurie Zirkle, CSE         E-mail: lat@vt.edu      Pager:
> > > (540)953-3691
> > > > > Virginia Tech CNS          Voice: (540)231-6370    Fax: (540)
> 231-3928
> > > > > Blacksburg VA  24061-0506
> > >
> > > --
> > > Laurie
> >

WARNING: multiple messages have this Message-ID
From: stevepr@crt.com
To: gcc-help@gnu.org
Cc: lat@cns.vt.edu
Subject: RE: AIX, gcc-2.95.1, and alloca -buildm error
Date: Sun, 31 Oct 1999 13:57:00 -0000	[thread overview]
Message-ID: <F931488C3634D11180D700A02461E2450201C8BD@chitmd03.nt.il.nbgfn.com> (raw)
Message-ID: <19991031135700.E8i7zitYTVnDEoXL1Owwt2y9SUDHunzwJkqPEUUdnoA@z> (raw)

> Laruie,
>  I have gotten gcc to build and install on aix.
> 
>  cd into some dir
>  gunzip -c gcc-2.95.1.tar.gz | tar xvf -
>  mkdir aix-gcc
>  cd aix-gcc
>  export $MAKE={ path to gnu make, I used 3.78.1, gnu make may be required
> and
>  xlc will build it }
>  ../gcc-2.95.1/configure --enable-languages=c,c++
>  $MAKE bootstrape
>  $MAKE -k check
>  $MAKE info
>  $MAKE install
> 
>  This will also build the stdlibc++.a.2.10.0 which contains the stl for
> c++.
> 
>  Good luck.
> 
>  Steve Pribyl
> 
> 
> > > -----Original Message-----
> > > From: Laurie Zirkle [SMTP:lat@cns.vt.edu]
> > > Sent: Tuesday, October 05, 1999 1:32 PM
> > > To: stevepr@crt.com
> > > Subject: Re: Your message to gcc-help
> > >
> > > I went poking thru the AIX faq and found this tidbit; maybe it will
> help
> > > you
> > > (I don't have time to try again today).
> > >
> > >      Subject: 2.01: I cannot make alloca work
> > >
> > >      A famous routine, in particular in GNU context, is the allocation
> > >      routine alloca().  Alloca allocates memory in such a way that it
> is
> > >      automatically free'd when the block is exited.  Most
> implementations
> > >      does this by adjusting the stack pointer.  Since not all C
> > > environments
> > >      can support it, its use is discouraged, but it is included in the
> xlc
> > >      compiler.  In order to make the compiler aware that you intend to
> use
> > >      alloca, you must put the line
> > >
> > >      #pragma alloca
> > >
> > >      before any other statements in the C source module(s) where
> alloca
> is
> > >      called.  If you don't do this, xlc will not recognize alloca as
> > > anything
> > >      special, and you will get errors during linking.
> > >
> > >      For AIX 3.2, it may be easier to use the -ma flag.
> > >
> > >
> > >
> > > From the fingers of stevepr@crt.com:
> > > > Nope not yet.
> > > >
> > > > However I have found that there may be some issues with the native
> make
> > > > program.  I have tried the gnu make,  It seems to work better, still
> > > fails
> > > > but at a different point.
> > > >
> > > > I will be sure to post what ever answer I get.
> > > > Steve Pribyl
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Laurie Zirkle [SMTP:lat@cns.vt.edu]
> > > > > Sent: Tuesday, October 05, 1999 7:32 AM
> > > > > To: stevepr@crt.com
> > > > > Subject: Your message to gcc-help
> > > > >
> > > > > Have you received any responses yet?  I have the exact same
> problem
> > > trying
> > > > > to compile gcc under AIX 4.3.2 using cc.  I didn't see an answer
> to
> > > the
> > > > > list yet.
> > > > >
> > > > > --
> > > > > Laurie Zirkle, CSE         E-mail: lat@vt.edu      Pager:
> > > (540)953-3691
> > > > > Virginia Tech CNS          Voice: (540)231-6370    Fax: (540)
> 231-3928
> > > > > Blacksburg VA  24061-0506
> > >
> > > --
> > > Laurie
> >

             reply	other threads:[~1999-10-14  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-14  8:53 stevepr [this message]
1999-10-31 13:57 ` stevepr
  -- strict thread matches above, loose matches on Subject: below --
1999-10-18  6:42 stevepr
1999-10-31 13:57 ` stevepr
1999-10-04  9:22 stevepr
1999-10-31 13:57 ` stevepr

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=F931488C3634D11180D700A02461E2450201C8BD@chitmd03.nt.il.nbgfn.com \
    --to=stevepr@crt.com \
    --cc=gcc-help@gnu.org \
    --cc=lat@cns.vt.edu \
    /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).