On 01 Aug 2001 11:47:38 +, Thomas Joseph wrote:
> Dear Sir
>
> I can't make the gdb stubs as an errore occurs. Please suggest any method to make
>i386-elf-gdb from Insight or standard gbd.
>
You need to mail the ecos and gdb lists (see sources.redhat.com for more
information on this). Thi
This is not applicable to make. You should either mail the glibc
mailing list
or the gas mailing list ([EMAIL PROTECTED]).
-eric
On 21 Jul 2001 15:04:43 +0200, jiv wrote:
> ric -D_LIBC_REENTRANT -include ../include/libc-symbols.h -o signals.o
> /tmp/ccAMGVRy.s: Assembler messages:
> /tmp
On 28 May 2001 14:30:41 -0700, leon Saviski wrote:
> hi;
> i have a problems with installation GNU make.
> I have WIN 98 2 ed. Whenever i try to do installation I fail.DO i have to
> install CYGWIN?
You can install cygwin, but you do not have to do so. Perhaps if you
were to tell one of us what y
> That was a "no" to your assertion. All of the Cygwin tools I'm using are
> precompiled from Cygwin.
Aaah. Then you don't want the complete environment?
>
> I was thinking as an alternative to hard-coding the shell to "/bin/sh.exe",
> I could modify make to look for "sh.exe" on the path if
Shawn Carey wrote:
>
> Thanks for the quick replies, folks!
>
> FYI, I'm using the bone-stock, cygwin compiled make executable with the
> latest DLL (1.3.1-1).
>
So that was a yes to my assertion that you weren't using the binaries
produced by the cygwin project?
> At the risk of being a pest
"Paul D. Smith" wrote:
>
> If you're using Cygwin's version of GNU make, you need to talk to them
> about it. Their version is not the same as the "normal" FSF-distributed
> GNU make.
>
> If you want to try the FSF version you can get it from:
>
> ftp://ftp.gnu.org/gnu/make/
>
I _think_
Ala Ridha wrote:
>
> I keep getting messages about file modification time in the future when
> I compile my programs using make in Solaris and Red Hat 7.
>
Sounds like you are:
a) compiling over nfs
b) the times are different between the two machines by some degree
If this isn't the case let
> "Stangl, Alex" wrote:
>
> P.S. A developer here told me afterwards I could use umount followed
> by mount to fix the root mount point problem, but I didn't realize at
> the time that CygWin supported the UNIX mount/unmount commands.
>
Yep. This is the right answer.
-eric
ps. can you avoid
> "Stangl, Alex" wrote:
>
> OK, thanks for the info. I figured it worth a shot. My box is a
> Pentium III, 600 MHz with 256 MB RAM, running NT 4.0 Workstation and
> the "B20" version of CygWin.
>
Wow. This is quite old. You might want to try upgrading to the newest
version of cygwin (www.cygw
> This is not a problem with make.
>
> Please contact the author of Checker and/or GCC for help.
>
> as> gcc -c -DGCCCHECKER -I. -I./l-malloc -I. -I./lib -I./config/obj-formats
> as> -I./config/i386/Linux -O2 -g -Wall -Wstrict-prototypes
> as> ./config/i386/Linux/munmap.c -o munmap.o
>
> Also I have problems with temp files created by make on /tmp.
> I see I have now less errors if I run make without -j5 option.
> Is this a bug or I must change my CPU?
> KDE2 team said me that is CPU's problems...
Okay, a few things:
1) These aren't bugs in make. Isn't that a wonderful thing
Michele De Luca wrote:
>
> When I run the gmake in digital machine I have this error:
>
> m2c not found
>
> can you help me???
>
I'd look for m2c on your system and look in the makefile and install
instructions for some guidance on what you need to compile the package
you have. You could als
You didn't specify what version of windows you are running on, or which
shell you are using. I imagine that it is the dos shell from Win95 (or
some such) which does have a fairly low limit of characters on a single
line. A way around this is to either use the NT shell (slightly better)
or use /b
> > On the gcc FAQ it said to send questions pertaining to build
> > problems to this address. I am a user on a Solaris 2.7 system, and I find
> > the available software less than adequate. So I've decided to compile a
> > bunch of the GNU software, and keep the GNU executables and other
Nirav,
> gmake[2]: Entering directory `/home/postgres/postgresql-6.5.3/src/lextest'
>
> lex scan.l
> gmake[2]: lex: Command not found
>From looking at this I would guess that you need to have lex somewhere
in your path when you build up the sql server.
If you were to correct this your problem
> Your choices are: (1) change your makefile back to use UNIX line
> endings, (2) get a fixed version of GNU make from Cygwin (ask them about
> it), or (3) get the latest "regular" version of GNU make (3.79.1) from
> the FSF (www.gnu.org) and build it for Windows (see the README.W32 file
> for in
16 matches
Mail list logo
