* Re: problems with make...
[not found] <420931cd.73b89a7f.78a5.30baSMTPIN_ADDED@mx.gmail.com>
@ 2005-02-09 9:11 ` corey taylor
2005-02-09 14:18 ` AW: " Jupp Tscheak
` (2 more replies)
0 siblings, 3 replies; 15+ messages in thread
From: corey taylor @ 2005-02-09 9:11 UTC (permalink / raw)
To: Jupp Tscheak; +Cc: gcc-help
Jupp,
For what behavior are you looking?
corey
On Tue, 8 Feb 2005 22:40:45 +0100, Jupp Tscheak <jupp_tscheak@gmx.de> wrote:
> Hi,
>
> we're building our project with automatic generated Makefiles (using qt's
> .pro files, although
> some modules have nothing to do with qt!). The problem is that if a static
> linked library has changed,
> it says "nothing to be done for..." (binary file is older than static lib so
> it should be relinked).
> Does anyone know how to avoid this behavior (any flags for g++)?
>
> Thanks in advance
>
> Jupp Tscheak
>
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* AW: problems with make...
2005-02-09 9:11 ` problems with make corey taylor
@ 2005-02-09 14:18 ` Jupp Tscheak
2005-02-09 14:18 ` Jupp Tscheak
[not found] ` <42093505.69af1669.78a5.37f4SMTPIN_ADDED@mx.gmail.com>
2 siblings, 0 replies; 15+ messages in thread
From: Jupp Tscheak @ 2005-02-09 14:18 UTC (permalink / raw)
To: 'corey taylor'; +Cc: gcc-help
Hi corey,
if a static linked library has changed the whole binary
should be recomplied. If make notices that any of the sources
are newer than the binary it recompiles. This behaviour should
be the same if the static lib is newer than the binary.
That isn't the case. Can you explain this?
Jupp
-----Ursprüngliche Nachricht-----
Von: corey taylor [mailto:corey.taylor@gmail.com]
Gesendet: Dienstag, 8. Februar 2005 22:44
An: Jupp Tscheak
Cc: gcc-help@gcc.gnu.org
Betreff: Re: problems with make...
Jupp,
For what behavior are you looking?
corey
On Tue, 8 Feb 2005 22:40:45 +0100, Jupp Tscheak <jupp_tscheak@gmx.de> wrote:
> Hi,
>
> we're building our project with automatic generated Makefiles (using
> qt's .pro files, although some modules have nothing to do with qt!).
> The problem is that if a static linked library has changed, it says
> "nothing to be done for..." (binary file is older than static lib so
> it should be relinked).
> Does anyone know how to avoid this behavior (any flags for g++)?
>
> Thanks in advance
>
> Jupp Tscheak
>
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* AW: problems with make...
2005-02-09 9:11 ` problems with make corey taylor
2005-02-09 14:18 ` AW: " Jupp Tscheak
@ 2005-02-09 14:18 ` Jupp Tscheak
[not found] ` <42093505.69af1669.78a5.37f4SMTPIN_ADDED@mx.gmail.com>
2 siblings, 0 replies; 15+ messages in thread
From: Jupp Tscheak @ 2005-02-09 14:18 UTC (permalink / raw)
To: 'corey taylor'; +Cc: gcc-help
Hi corey,
if a static linked library has changed the whole binary
should be recomplied. If make notices that any of the sources
are newer than the binary it recompiles. This behaviour should
be the same if the static lib is newer than the binary.
That isn't the case. Can you explain this?
Jupp
-----Ursprüngliche Nachricht-----
Von: corey taylor [mailto:corey.taylor@gmail.com]
Gesendet: Dienstag, 8. Februar 2005 22:44
An: Jupp Tscheak
Cc: gcc-help@gcc.gnu.org
Betreff: Re: problems with make...
Jupp,
For what behavior are you looking?
corey
On Tue, 8 Feb 2005 22:40:45 +0100, Jupp Tscheak <jupp_tscheak@gmx.de> wrote:
> Hi,
>
> we're building our project with automatic generated Makefiles (using
> qt's .pro files, although some modules have nothing to do with qt!).
> The problem is that if a static linked library has changed, it says
> "nothing to be done for..." (binary file is older than static lib so
> it should be relinked).
> Does anyone know how to avoid this behavior (any flags for g++)?
>
> Thanks in advance
>
> Jupp Tscheak
>
>
^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <42093505.69af1669.78a5.37f4SMTPIN_ADDED@mx.gmail.com>]
* Re: AW: problems with make...
[not found] ` <42093505.69af1669.78a5.37f4SMTPIN_ADDED@mx.gmail.com>
@ 2005-02-09 15:06 ` corey taylor
2005-02-09 15:10 ` Tony Wetmore
0 siblings, 1 reply; 15+ messages in thread
From: corey taylor @ 2005-02-09 15:06 UTC (permalink / raw)
To: Jupp Tscheak; +Cc: gcc-help
Well, I don't exactly see why you would want that.
However, that's an automake, make issue. I'm not sure if you can
specify a binary in the dependency list though.
Corey
On Tue, 8 Feb 2005 22:54:42 +0100, Jupp Tscheak <jupp_tscheak@gmx.de> wrote:
> Hi corey,
>
> if a static linked library has changed the whole binary
> should be recomplied. If make notices that any of the sources
> are newer than the binary it recompiles. This behaviour should
> be the same if the static lib is newer than the binary.
> That isn't the case. Can you explain this?
>
> Jupp
>
> -----Ursprüngliche Nachricht-----
> Von: corey taylor [mailto:corey.taylor@gmail.com]
> Gesendet: Dienstag, 8. Februar 2005 22:44
> An: Jupp Tscheak
> Cc: gcc-help@gcc.gnu.org
> Betreff: Re: problems with make...
>
> Jupp,
>
> For what behavior are you looking?
>
> corey
>
> On Tue, 8 Feb 2005 22:40:45 +0100, Jupp Tscheak <jupp_tscheak@gmx.de> wrote:
> > Hi,
> >
> > we're building our project with automatic generated Makefiles (using
> > qt's .pro files, although some modules have nothing to do with qt!).
> > The problem is that if a static linked library has changed, it says
> > "nothing to be done for..." (binary file is older than static lib so
> > it should be relinked).
> > Does anyone know how to avoid this behavior (any flags for g++)?
> >
> > Thanks in advance
> >
> > Jupp Tscheak
> >
> >
>
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: AW: problems with make...
2005-02-09 15:06 ` corey taylor
@ 2005-02-09 15:10 ` Tony Wetmore
2005-02-09 16:01 ` corey taylor
0 siblings, 1 reply; 15+ messages in thread
From: Tony Wetmore @ 2005-02-09 15:10 UTC (permalink / raw)
To: gcc-help, 'corey taylor', 'Jupp Tscheak'
Jupp: This is definitely a question to be answered by a Qt mailing
list. It has nothing to do with gcc. Even make is not a part of gcc,
so that likely has its own mailing list as well.
Corey: If you are linking an executable against a static library, as
Jupp is doing, you must re-link the executable if the library changes,
otherwise your executable will NOT see the changes made in the library.
This is definitely something you would do in a Makefile for your
executable, probably something like this:
executable: main.o staticlibrary.a
LINK_COMMAND_HERE
That rule would trigger a re-link of the executable if either main.o or
staticlibrary.a were changed.
---
Tony Wetmore
Raytheon Solipsys
mailto:tony.wetmore@solipsys.com
http://www.solipsys.com
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of corey taylor
Sent: Tuesday, February 08, 2005 5:11 PM
To: Jupp Tscheak
Cc: gcc-help@gcc.gnu.org
Subject: Re: AW: problems with make...
Well, I don't exactly see why you would want that.
However, that's an automake, make issue. I'm not sure if you can
specify a binary in the dependency list though.
Corey
On Tue, 8 Feb 2005 22:54:42 +0100, Jupp Tscheak <jupp_tscheak@gmx.de>
wrote:
> Hi corey,
>
> if a static linked library has changed the whole binary should be
> recomplied. If make notices that any of the sources are newer than the
> binary it recompiles. This behaviour should be the same if the static
> lib is newer than the binary. That isn't the case. Can you explain
> this?
>
> Jupp
>
> -----Ursprüngliche Nachricht-----
> Von: corey taylor [mailto:corey.taylor@gmail.com]
> Gesendet: Dienstag, 8. Februar 2005 22:44
> An: Jupp Tscheak
> Cc: gcc-help@gcc.gnu.org
> Betreff: Re: problems with make...
>
> Jupp,
>
> For what behavior are you looking?
>
> corey
>
> On Tue, 8 Feb 2005 22:40:45 +0100, Jupp Tscheak <jupp_tscheak@gmx.de>
> wrote:
> > Hi,
> >
> > we're building our project with automatic generated Makefiles (using
> > qt's .pro files, although some modules have nothing to do with qt!).
> > The problem is that if a static linked library has changed, it says
> > "nothing to be done for..." (binary file is older than static lib so
> > it should be relinked). Does anyone know how to avoid this behavior
> > (any flags for g++)?
> >
> > Thanks in advance
> >
> > Jupp Tscheak
> >
> >
>
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: AW: problems with make...
2005-02-09 15:10 ` Tony Wetmore
@ 2005-02-09 16:01 ` corey taylor
2005-02-09 16:09 ` corey taylor
0 siblings, 1 reply; 15+ messages in thread
From: corey taylor @ 2005-02-09 16:01 UTC (permalink / raw)
To: Tony Wetmore; +Cc: gcc-help, Jupp Tscheak
I thought he was relinking. I was expecting that behavior.
He said that he wanted it to rebuild the source, which is what I
didn't understand.
I use Qt's make system and it works rather well. I'm fairly certain
however that it has no special rules for binary dependencies. I will
take another look.
corey
On Tue, 8 Feb 2005 18:06:12 -0500, Tony Wetmore
<tony.wetmore@solipsys.com> wrote:
>
> Jupp: This is definitely a question to be answered by a Qt mailing
> list. It has nothing to do with gcc. Even make is not a part of gcc,
> so that likely has its own mailing list as well.
>
> Corey: If you are linking an executable against a static library, as
> Jupp is doing, you must re-link the executable if the library changes,
> otherwise your executable will NOT see the changes made in the library.
> This is definitely something you would do in a Makefile for your
> executable, probably something like this:
>
> executable: main.o staticlibrary.a
> LINK_COMMAND_HERE
>
> That rule would trigger a re-link of the executable if either main.o or
> staticlibrary.a were changed.
>
> ---
> Tony Wetmore
> Raytheon Solipsys
> mailto:tony.wetmore@solipsys.com
> http://www.solipsys.com
>
>
> -----Original Message-----
> From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
> Behalf Of corey taylor
> Sent: Tuesday, February 08, 2005 5:11 PM
> To: Jupp Tscheak
> Cc: gcc-help@gcc.gnu.org
> Subject: Re: AW: problems with make...
>
> Well, I don't exactly see why you would want that.
>
> However, that's an automake, make issue. I'm not sure if you can
> specify a binary in the dependency list though.
>
> Corey
>
> On Tue, 8 Feb 2005 22:54:42 +0100, Jupp Tscheak <jupp_tscheak@gmx.de>
> wrote:
> > Hi corey,
> >
> > if a static linked library has changed the whole binary should be
> > recomplied. If make notices that any of the sources are newer than the
>
> > binary it recompiles. This behaviour should be the same if the static
> > lib is newer than the binary. That isn't the case. Can you explain
> > this?
> >
> > Jupp
> >
> > -----Ursprüngliche Nachricht-----
> > Von: corey taylor [mailto:corey.taylor@gmail.com]
> > Gesendet: Dienstag, 8. Februar 2005 22:44
> > An: Jupp Tscheak
> > Cc: gcc-help@gcc.gnu.org
> > Betreff: Re: problems with make...
> >
> > Jupp,
> >
> > For what behavior are you looking?
> >
> > corey
> >
> > On Tue, 8 Feb 2005 22:40:45 +0100, Jupp Tscheak <jupp_tscheak@gmx.de>
> > wrote:
> > > Hi,
> > >
> > > we're building our project with automatic generated Makefiles (using
>
> > > qt's .pro files, although some modules have nothing to do with qt!).
>
> > > The problem is that if a static linked library has changed, it says
> > > "nothing to be done for..." (binary file is older than static lib so
>
> > > it should be relinked). Does anyone know how to avoid this behavior
> > > (any flags for g++)?
> > >
> > > Thanks in advance
> > >
> > > Jupp Tscheak
> > >
> > >
> >
> >
>
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: AW: problems with make...
2005-02-09 16:01 ` corey taylor
@ 2005-02-09 16:09 ` corey taylor
0 siblings, 0 replies; 15+ messages in thread
From: corey taylor @ 2005-02-09 16:09 UTC (permalink / raw)
To: gcc-help, Jupp Tscheak
Jupp,
I was able to find something that might be useful. I have not used
this specific feature of qmake so I don't know expected behavior.
http://doc.trolltech.com/3.1/qmake-manual-7.html#Environment
There is a section titled "Library Dependencies". This shows how to
first *enable* and then list the mandatory library linkings. qmake
will generate a dependency list by going through the static libs
specified.
However, I do not know what kind of re-linking or re-building behavior
a changed library dependency will invoke.
corey
On Tue, 8 Feb 2005 17:15:47 -0600, corey taylor <corey.taylor@gmail.com> wrote:
> I thought he was relinking. I was expecting that behavior.
>
> He said that he wanted it to rebuild the source, which is what I
> didn't understand.
>
> I use Qt's make system and it works rather well. I'm fairly certain
> however that it has no special rules for binary dependencies. I will
> take another look.
>
> corey
>
> On Tue, 8 Feb 2005 18:06:12 -0500, Tony Wetmore
> <tony.wetmore@solipsys.com> wrote:
> >
> > Jupp: This is definitely a question to be answered by a Qt mailing
> > list. It has nothing to do with gcc. Even make is not a part of gcc,
> > so that likely has its own mailing list as well.
> >
> > Corey: If you are linking an executable against a static library, as
> > Jupp is doing, you must re-link the executable if the library changes,
> > otherwise your executable will NOT see the changes made in the library.
> > This is definitely something you would do in a Makefile for your
> > executable, probably something like this:
> >
> > executable: main.o staticlibrary.a
> > LINK_COMMAND_HERE
> >
> > That rule would trigger a re-link of the executable if either main.o or
> > staticlibrary.a were changed.
> >
> > ---
> > Tony Wetmore
> > Raytheon Solipsys
> > mailto:tony.wetmore@solipsys.com
> > http://www.solipsys.com
> >
> >
> > -----Original Message-----
> > From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
> > Behalf Of corey taylor
> > Sent: Tuesday, February 08, 2005 5:11 PM
> > To: Jupp Tscheak
> > Cc: gcc-help@gcc.gnu.org
> > Subject: Re: AW: problems with make...
> >
> > Well, I don't exactly see why you would want that.
> >
> > However, that's an automake, make issue. I'm not sure if you can
> > specify a binary in the dependency list though.
> >
> > Corey
> >
> > On Tue, 8 Feb 2005 22:54:42 +0100, Jupp Tscheak <jupp_tscheak@gmx.de>
> > wrote:
> > > Hi corey,
> > >
> > > if a static linked library has changed the whole binary should be
> > > recomplied. If make notices that any of the sources are newer than the
> >
> > > binary it recompiles. This behaviour should be the same if the static
> > > lib is newer than the binary. That isn't the case. Can you explain
> > > this?
> > >
> > > Jupp
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: corey taylor [mailto:corey.taylor@gmail.com]
> > > Gesendet: Dienstag, 8. Februar 2005 22:44
> > > An: Jupp Tscheak
> > > Cc: gcc-help@gcc.gnu.org
> > > Betreff: Re: problems with make...
> > >
> > > Jupp,
> > >
> > > For what behavior are you looking?
> > >
> > > corey
> > >
> > > On Tue, 8 Feb 2005 22:40:45 +0100, Jupp Tscheak <jupp_tscheak@gmx.de>
> > > wrote:
> > > > Hi,
> > > >
> > > > we're building our project with automatic generated Makefiles (using
> >
> > > > qt's .pro files, although some modules have nothing to do with qt!).
> >
> > > > The problem is that if a static linked library has changed, it says
> > > > "nothing to be done for..." (binary file is older than static lib so
> >
> > > > it should be relinked). Does anyone know how to avoid this behavior
> > > > (any flags for g++)?
> > > >
> > > > Thanks in advance
> > > >
> > > > Jupp Tscheak
> > > >
> > > >
> > >
> > >
> >
> >
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* problems with make...
@ 2005-02-09 1:46 Jupp Tscheak
0 siblings, 0 replies; 15+ messages in thread
From: Jupp Tscheak @ 2005-02-09 1:46 UTC (permalink / raw)
To: gcc-help
Hi,
we're building our project with automatic generated Makefiles (using qt's
.pro files, although
some modules have nothing to do with qt!). The problem is that if a static
linked library has changed,
it says "nothing to be done for..." (binary file is older than static lib so
it should be relinked).
Does anyone know how to avoid this behavior (any flags for g++)?
Thanks in advance
Jupp Tscheak
^ permalink raw reply [flat|nested] 15+ messages in thread
* problems with make...
@ 2005-02-09 1:46 Jupp Tscheak
0 siblings, 0 replies; 15+ messages in thread
From: Jupp Tscheak @ 2005-02-09 1:46 UTC (permalink / raw)
To: gcc-help
Hi,
we're building our project with automatic generated Makefiles (using qt's
.pro files, although
some modules have nothing to do with qt!). The problem is that if a static
linked library has changed,
it says "nothing to be done for..." (binary file is older than static lib so
it should be relinked).
Does anyone know how to avoid this behavior (any flags for g++)?
Thanks in advance
Jupp Tscheak
^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <616BE6A276E3714788D2AC35C40CD18D393F99@whale.softwire.co.uk>]
* RE: Problems with make
[not found] <616BE6A276E3714788D2AC35C40CD18D393F99@whale.softwire.co.uk>
@ 2002-01-28 4:28 ` Rupert Wood
0 siblings, 0 replies; 15+ messages in thread
From: Rupert Wood @ 2002-01-28 4:28 UTC (permalink / raw)
To: 'Momchil Velikov'; +Cc: kabir.patel, gcc-help
Momchil Velikov wrote:
> >> When I run >>make makefile
:
> Rupert> You need to tell make what you'd like it to build. If you
> Rupert> don't specify anything then it assumes a target 'all' which
> Rupert> doesn't exist in your makefile.
>
> Actually it picks up the first target, no need for ``all''.
>
> The problem is that there's no dependency upon the Makefile itself.
Oops, yes, I stand corrected; answered from memory without checking
docs. I also hadn't noticed that he was running 'make makefile' instead
of plain 'make'.
Kabir, if you want to specify the makefile to use then you should type
'make -f <makefile name>'. It will automatically search a number of
filenames to use as the makefile including 'makefile' and 'Makefile' if
you don't specify -f.
Rup.
^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <616BE6A276E3714788D2AC35C40CD18D393F88@whale.softwire.co.uk>]
* RE: Problems with make
[not found] <616BE6A276E3714788D2AC35C40CD18D393F88@whale.softwire.co.uk>
@ 2002-01-28 3:41 ` Rupert Wood
2002-01-28 4:16 ` Momchil Velikov
0 siblings, 1 reply; 15+ messages in thread
From: Rupert Wood @ 2002-01-28 3:41 UTC (permalink / raw)
To: kabir.patel; +Cc: gcc-help
Kabir Patel wrote:
> The makefile has the following :
>
> ex2: ex1.c
> gcc ex1.c -o ex2
>
> and nothing else.
> When I run >>make makefile
> I always get the same message, namely:
>
> make: Nothing to be done for `makefile'.
You need to tell make what you'd like it to build. If you don't specify
anything then it assumes a target 'all' which doesn't exist in your
makefile.
You either need to:
make ex2
or add an 'all' target to the makefile which references ex2, e.g.
ex2: ex1.c
gcc ex1.c -o ex2
all: ex2
You may wish to investigate the GNU automake project which simplifies
generation of complex makefiles.
Rup.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Problems with make
2002-01-28 3:41 ` Rupert Wood
@ 2002-01-28 4:16 ` Momchil Velikov
0 siblings, 0 replies; 15+ messages in thread
From: Momchil Velikov @ 2002-01-28 4:16 UTC (permalink / raw)
To: Rupert Wood; +Cc: kabir.patel, gcc-help
>>>>> "Rupert" == Rupert Wood <me@rupey.net> writes:
Rupert> Kabir Patel wrote:
>> The makefile has the following :
>>
>> ex2: ex1.c
>> gcc ex1.c -o ex2
>>
>> and nothing else.
>> When I run >>make makefile
>> I always get the same message, namely:
>>
>> make: Nothing to be done for `makefile'.
Rupert> You need to tell make what you'd like it to build. If you don't specify
Rupert> anything then it assumes a target 'all' which doesn't exist in your
Rupert> makefile.
Actually it picks up the first target, no need for ``all''.
The problem is that there's no dependency upon the Makefile itself.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Problems with make
@ 2002-01-28 3:31 kabir.patel
0 siblings, 0 replies; 15+ messages in thread
From: kabir.patel @ 2002-01-28 3:31 UTC (permalink / raw)
To: me; +Cc: gcc-help
Dear all,
I am trying to use a makfile to compile a simple piece of C.
The makefile has the following :
ex2: ex1.c
gcc ex1.c -o ex2
and nothing else.
When I run >>make makefile
I always get the same message, namely:
make: Nothing to be done for `makefile'.
This occurs even when I edit the file, or use additional options such as -W, or
when I use 'touch'.
When I run the command manually (gcc ex1.c -o ex2) it compiles fine.
Could somebody please tell me why this might be the case?
Thanks
*******************Internet Email Confidentiality Footer*******************
Privileged/Confidential Information may be contained in this message. If you
are not the addressee indicated in this message (or responsible for delivery of
the message to such person), you may not copy or deliver this message to anyone.
In such case, you should destroy this message and kindly notify the sender by
reply email. Please advise immediately if you or your employer does not consent
to Internet email for messages of this kind. Opinions, conclusions and other
information in this message that do not relate to the official business of my
firm shall be understood as neither given nor endorsed by it.
^ permalink raw reply [flat|nested] 15+ messages in thread
* problems with make
@ 1999-12-23 5:27 Adriano Holanda
1999-12-31 22:24 ` Adriano Holanda
0 siblings, 1 reply; 15+ messages in thread
From: Adriano Holanda @ 1999-12-23 5:27 UTC (permalink / raw)
To: gcc-help
My system is: Solaris 7 (SPARC)
I have installed binaries gcc in my machine, but some tasks it doesn't
make, like install some perl modules e some programs. So i decided install
the source gcc-2.95.2 and when I run make, this happened:
//final of the make output
/usr/local/gcc-2.95.2/libiberty/vfork.c -o pic/vfork.o
gcc -c -DHAVE_CONFIG_H -g -O2 -I.
-I/usr/local/gcc-2.95.2/libiberty/../include
/usr/local/gcc-2.95.2/libiberty/vfork.c
rm -f libiberty.a
ar rc libiberty.a \
argv.o choose-temp.o concat.o cplus-dem.o fdmatch.o fnmatch.o getopt.o
getopt1.o getruntime.o hex.o floatformat.o objalloc.o obstack.o pexecute.o
spaces.o splay-tree.o strerror.o strsignal.o xatexit.o xexit.o xmalloc.o
xstrdup.o xstrerror.o asprintf.o mkstemps.o setenv.o sigsetmask.o
vasprintf.o vfork.o
make[1]: ar: Command not found
make[1]: *** [libiberty.a] Error 127
make[1]: Leaving directory `/usr/local/gcc-2.95.2/obj/libiberty'
make: *** [all-libiberty] Error 2
How can I install gcc 2.95.2 source without this error?
Thanks,
Adriano.
^ permalink raw reply [flat|nested] 15+ messages in thread
* problems with make
1999-12-23 5:27 problems " Adriano Holanda
@ 1999-12-31 22:24 ` Adriano Holanda
0 siblings, 0 replies; 15+ messages in thread
From: Adriano Holanda @ 1999-12-31 22:24 UTC (permalink / raw)
To: gcc-help
My system is: Solaris 7 (SPARC)
I have installed binaries gcc in my machine, but some tasks it doesn't
make, like install some perl modules e some programs. So i decided install
the source gcc-2.95.2 and when I run make, this happened:
//final of the make output
/usr/local/gcc-2.95.2/libiberty/vfork.c -o pic/vfork.o
gcc -c -DHAVE_CONFIG_H -g -O2 -I.
-I/usr/local/gcc-2.95.2/libiberty/../include
/usr/local/gcc-2.95.2/libiberty/vfork.c
rm -f libiberty.a
ar rc libiberty.a \
argv.o choose-temp.o concat.o cplus-dem.o fdmatch.o fnmatch.o getopt.o
getopt1.o getruntime.o hex.o floatformat.o objalloc.o obstack.o pexecute.o
spaces.o splay-tree.o strerror.o strsignal.o xatexit.o xexit.o xmalloc.o
xstrdup.o xstrerror.o asprintf.o mkstemps.o setenv.o sigsetmask.o
vasprintf.o vfork.o
make[1]: ar: Command not found
make[1]: *** [libiberty.a] Error 127
make[1]: Leaving directory `/usr/local/gcc-2.95.2/obj/libiberty'
make: *** [all-libiberty] Error 2
How can I install gcc 2.95.2 source without this error?
Thanks,
Adriano.
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2005-02-08 23:21 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <420931cd.73b89a7f.78a5.30baSMTPIN_ADDED@mx.gmail.com>
2005-02-09 9:11 ` problems with make corey taylor
2005-02-09 14:18 ` AW: " Jupp Tscheak
2005-02-09 14:18 ` Jupp Tscheak
[not found] ` <42093505.69af1669.78a5.37f4SMTPIN_ADDED@mx.gmail.com>
2005-02-09 15:06 ` corey taylor
2005-02-09 15:10 ` Tony Wetmore
2005-02-09 16:01 ` corey taylor
2005-02-09 16:09 ` corey taylor
2005-02-09 1:46 Jupp Tscheak
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 1:46 Jupp Tscheak
[not found] <616BE6A276E3714788D2AC35C40CD18D393F99@whale.softwire.co.uk>
2002-01-28 4:28 ` Problems " Rupert Wood
[not found] <616BE6A276E3714788D2AC35C40CD18D393F88@whale.softwire.co.uk>
2002-01-28 3:41 ` Rupert Wood
2002-01-28 4:16 ` Momchil Velikov
2002-01-28 3:31 kabir.patel
1999-12-23 5:27 problems " Adriano Holanda
1999-12-31 22:24 ` Adriano Holanda
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).