Mombu the Programming Forum sponsored links

Go Back   Mombu the Programming Forum > Programming > about bootstrap the djgpp's gcc
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 4th May 06:16
aiko_sex
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


/dev/e/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/src/.libs/libstdcxx.a(
numeric_members.o)(.text._ZNSt8numpunctIcED0Ev+0x2 3):e:/gcc1/gnu/build.gcc/i586-
pc-msdosdjgpp/libstdc++-v3/src/numeric_members.cc:50: undefined
reference to `op
erator delete(void*)'
/dev/e/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/src/.libs/libstdcxx.a(
numeric_members.o)(.eh_frame+0x11):e:/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libs
tdc++-v3/src/numeric_members.cc:47: undefined reference to
`___gxx_personality_v
0'
/dev/e/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/src/.libs/libstdcxx.a(
time_members.o)(.eh_frame+0x11):e:/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc
++-v3/src/time_members.cc:60: undefined reference to
`___gxx_personality_v0'
/dev/e/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/src/.libs/libstdcxx.a(
messages_members.o)(.eh_frame+0x11):e:/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/lib
stdc++-v3/src/messages_members.cc:44: undefined reference to
`___gxx_personality
_v0'
collect2: ld returned 1 exit status
make.exe[4]: *** [abi_check] Error 1
make.exe[3]: *** [all-recursive] Error 1
make.exe[2]: *** [all] Error 2
make.exe[1]: *** [all-target-libstdc++-v3] Error 2
make.exe: *** [bootstrap] Error 2

this is my last info on the screen,i use djgpp on win98-msdos box .

below is my redrect the erro in a file and these are the last message:
LD_RUN_PATH=/dev/e/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/src/.libs
c:/djgpp/bin/sh.exe ../libtool --tag=CXX --mode=link `echo
/dev/e/gcc1/gnu/build
..gcc/gcc/xgcc -shared-libgcc -B/dev/e/gcc1/gnu/build.gcc/gcc/
-nostdinc++ -L/de
v/e/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/src
-L/dev/e/gcc1/gnu/bui
ld.gcc/i586-pc-msdosdjgpp/libstdc++-v3/src/.libs
-B/dev/env/DJDIR/i586-pc-msdosd
jgpp/bin/ -B/dev/env/DJDIR/i586-pc-msdosdjgpp/lib/ -isystem
/dev/env/DJDIR/i586-
pc-msdosdjgpp/include | sed 's/xgcc/g++/g'` -g -O2 -o abi_check
abi_check.o
-lm
mkdir .libs
/dev/e/gcc1/gnu/build.gcc/gcc/g++ -shared-libgcc
-B/dev/e/gcc1/gnu/build.gcc/gcc
/ -nostdinc++ -B/dev/env/DJDIR/i586-pc-msdosdjgpp/bin/
-B/dev/env/DJDIR/i586-pc-
msdosdjgpp/lib/ -isystem /dev/env/DJDIR/i586-pc-msdosdjgpp/include -g
-O2 -o abi
_check abi_check.o -L/dev/e/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/
src -L/dev/e/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/src/.libs
-lm
make.exe[4]: Leaving directory
`e:/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc
++-v3/testsuite'
make.exe[3]: Leaving directory
`e:/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc
-- More --

++-v3'
make.exe[2]: Leaving directory
`e:/gcc1/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc
++-v3'
make.exe[1]: Leaving directory `e:/gcc1/gnu/build.gcc'

E:\gcc1\gnu\build.gcc>

I read the readme.djgpp in the gcc 's source and do as it told me
cd $djgpp/gnu/build.gcc
sh djconfig.sh
sh sj make.sh bootstrap 2>1

,but alwayes fail like above in the stage3,anybody known why?i have
done it in the windows 2000 dos box server times and the same errors.

can djgpp's gcc bootstrap by itself?
  Reply With Quote


  sponsored links


2 4th May 06:17
aiko_sex
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


################################################## #############################
__gxx_personality_v0 errors are usually due to linking C++ programs with gcc


i known the _gxx_personality_vo symbols in the libstdcxx.a library,
and i test the original gpp (the one bootstrap the gcc above),and it
can successfully compile and link .but when bootstrap in the stage3,it
will stop as above.i retried server versions gcc source download from
the DJ's home.for example:gcc321s.zip,gcc322s.zip,gcc323s.zip,gcc2.9 52s.zip.all
failed for the symbol in the libstdcxx.a at stage 3 linking time.i
don't know wheather the gcc in the djgpp can bootstrap with the
source from DJ's home.If i make directly it will success,but when
bootstrap ,it failed alwayes in the stage3 for those symbols in the
libstdcxx.a

so ,i don't think these were leaded by my original gpp .sombody even
successly bootstrap gcc without no change the source download from the
DJ's home?
I want your help.:_)
  Reply With Quote
3 4th May 06:17
andrew cottrell
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


Based on my past experience this occurs when something goes horibbly
wrong and you get a brain dead C++ lib file. This has occured with
file utils in the past and one other app, but I can't remember what it
was.

So long as you use all of the alpha 1 or the files from clio then
building from gcc***s.zip should work fine (*** > 310).

To save you allot of time please ensure that you are using all of the
files from the ftp.delorie.com/pub/djgpp/alpha directory, do NOT mix
2.03 and 2.04 files if you are trying to build GCC as you may come
accross symlink issues or 2.03 issues on your W2K OS.

Please have a read of the following URLs:-
http://www.phekda.freeserve.co.uk/richdawe/djgpp/2.04/status204.html
http://clio.rice.edu/djgpp/win2k/main_204.htm

If you use all of the apps from either the alpha or clio.rice.edu then
from the clio.rice.edu have a look at the build utils section as there
is a http://clio.rice.edu/djgpp/win2k/dj204_build_batch.zip file which
includes the batch files I use to build all of the zip files at
clio.rice.edu.

If you still can't get it to build then I also suggest that you setup
DJGPP in a new directory from scratch and see if this new version
works. Check the dates of the exes in the bin directory to ensure that
they are from this year and all from about the same date. If they
aren't then you have installed an old program.


Andrew
  Reply With Quote
4 4th May 06:17
aiko_sex
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


well, I have download all the packages needed by readme.djgpp in
gcc322s.zip from ftp://ftp.iij.ad.jp/pub/djgpp/alpha/ (I want to konw
why are there not the same date stamp package in the alpha,so I have
to use some time of 2003.6.18's and some are 2003 4.25's packages.but
this time i have the error as blow:

make.exe[2]: Nothing to be done for `all'.
make.exe[2]: Leaving directory
`f:/gcc7/gnu/build.gcc/libiberty/testsuite'
make.exe[1]: Leaving directory `f:/gcc7/gnu/build.gcc/libiberty'
Bootstrapping the compiler
make.exe[1]: Entering directory `f:/gcc7/gnu/build.gcc/gcc'
c:/djgpp204/bin/make.exe CC="gcc" libdir=/dev/env/DJDIR/lib
libsubdir=/dev/env/D
JDIR/lib/gcc-lib/djgpp/3.22 \
gcc_version=3.22 LANGUAGES="c " \
CFLAGS="-g " MAKEINFO="makeinfo " \
MAKEINFOFLAGS=""
make.exe[2]: Entering directory `f:/gcc7/gnu/build.gcc/gcc'
(cd intl && c:/djgpp204/bin/make.exe all)
make.exe[3]: Entering directory `f:/gcc7/gnu/build.gcc/gcc/intl'
make.exe[3]: Nothing to be done for `all'. make.exe[3]: Leaving directory `f:/gcc7/gnu/build.gcc/gcc/intl'
../genattrtab.exe /gcc7/gnu/gcc-3.22/gcc/config/i386/i386.md >
tmp-attrtab.c

Cannot allocate 64 bytes after allocating 33334116 bytes
make.exe[2]: *** [s-attrtab] Error 1
make.exe[2]: Leaving directory `f:/gcc7/gnu/build.gcc/gcc'
make.exe[1]: *** [stage1_build] Error 2
make.exe[1]: Leaving directory `f:/gcc7/gnu/build.gcc/gcc'
make.exe: *** [bootstrap] Error 2

I use the windows 2003 enterpise server and use djgpp in its dos
box.anyhow,does the gcc in the 2.04 alpha( gcc322b.zip & gpp322.zip)
support the ISO C89?

because i have some errors like follows:
/gcc7/gnu/gcc-3.22/include/xregex2.h:551: warning: ISO C89 does not
support `sta
tic' or type qualifiers in parameter array declarators

and i have redirect all the errors in a file ,its have all the erros
like below:

In file included from /gcc7/gnu/gcc-3.22/include/xregex.h:26,
from /gcc7/gnu/gcc-3.22/libiberty/regex.c:195:
/gcc7/gnu/gcc-3.22/include/xregex2.h:551: warning: ISO C89 does not
support `static' or type qualifiers in parameter array declarators
In file included from /gcc7/gnu/gcc-3.22/libiberty/regex.c:649:
/gcc7/gnu/gcc-3.22/libiberty/regex.c: In function
`byte_compile_range':
/gcc7/gnu/gcc-3.22/libiberty/regex.c:4602: warning: signed and
unsigned type in conditional expression
/gcc7/gnu/gcc-3.22/libiberty/regex.c:4612: warning: signed and
unsigned type in conditional expression
/gcc7/gnu/gcc-3.22/libiberty/regex.c:4612: warning: signed and
unsigned type in conditional expression
/gcc7/gnu/gcc-3.22/libiberty/regex.c: At top level:
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1380: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1382: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1383: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1385: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1386: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1388: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1389: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1391: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1392: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1394: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1395: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1397: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1398: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1400: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1401: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1403: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1404: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1406: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1407: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1409: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1410: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1412: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1413: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1415: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1416: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1418: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1419: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1421: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1422: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1424: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1425: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c:1427: warning: traditional C
rejects string concatenation
/gcc7/gnu/gcc-3.22/libiberty/regex.c: In function `xregerror':
/gcc7/gnu/gcc-3.22/libiberty/regex.c:8234: warning: unused parameter
`preg'
/gcc7/gnu/gcc-3.22/libiberty/md5.c:356:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:357:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:358:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:359:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:360:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:361:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:362:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:363:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:364:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:365:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:366:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:367:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:368:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:369:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:370:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:371:58: warning: function-like
macro "FG" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:374:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:375:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:376:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:377:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:378:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:379:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:380:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:381:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:382:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:383:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:384:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:385:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:386:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:387:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:388:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:389:58: warning: function-like
macro "FH" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:392:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:393:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:394:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:395:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:396:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:397:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:398:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:399:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:400:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:401:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:402:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:403:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:404:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:405:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:406:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/md5.c:407:58: warning: function-like
macro "FI" must be used with arguments in traditional C
/gcc7/gnu/gcc-3.22/libiberty/getopt.c: In function
`_getopt_initialize':
/gcc7/gnu/gcc-3.22/libiberty/getopt.c:396: warning: unused parameter
`argc'
/gcc7/gnu/gcc-3.22/libiberty/getopt.c:397: warning: unused parameter
`argv'
/gcc7/gnu/gcc-3.22/libiberty/pexecute.c: In function `pexecute':
/gcc7/gnu/gcc-3.22/libiberty/pexecute.c:146: warning: unused parameter
`this_pname'
/gcc7/gnu/gcc-3.22/libiberty/pexecute.c:147: warning: unused parameter
`temp_base'
/gcc7/gnu/gcc-3.22/libiberty/pexecute.c: In function `pwait':
/gcc7/gnu/gcc-3.22/libiberty/pexecute.c:231: warning: unused parameter
`flags'
/gcc7/gnu/gcc-3.22/gcc/cppfiles.c: In function `open_file':
/gcc7/gnu/gcc-3.22/gcc/cppfiles.c:279: warning: implicit declaration
of function `setmode'
/gcc7/gnu/gcc-3.22/gcc/calls.c:2069: warning: function declaration
isn't a prototype
/gcc7/gnu/gcc-3.22/gcc/combine.c: In function `combine_simplify_rtx':
/gcc7/gnu/gcc-3.22/gcc/combine.c:4106: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c: In function `simplify_if_then_else':
/gcc7/gnu/gcc-3.22/gcc/combine.c:4866: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:4881: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c: In function `force_to_mode':
/gcc7/gnu/gcc-3.22/gcc/combine.c:6779: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c: In function `extended_count':
/gcc7/gnu/gcc-3.22/gcc/combine.c:8773: warning: signed and unsigned
type in conditional expression
/gcc7/gnu/gcc-3.22/gcc/combine.c: In function `simplify_shift_const':
/gcc7/gnu/gcc-3.22/gcc/combine.c:9001: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9119: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9161: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9195: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9352: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9407: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9426: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9450: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9515: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9518: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:9581: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c: In function `recog_for_combine':
/gcc7/gnu/gcc-3.22/gcc/combine.c:9708: warning: pointer targets in
passing arg 1 of `do_SUBST_INT' differ in signedness
/gcc7/gnu/gcc-3.22/gcc/combine.c: In function `simplify_comparison':
/gcc7/gnu/gcc-3.22/gcc/combine.c:10494: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:10578: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:10835: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:10932: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:11033: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/combine.c:11035: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/emit-rtl.c: In function `gen_rtx_REG':
/gcc7/gnu/gcc-3.22/gcc/emit-rtl.c:424: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/emit-rtl.c: In function
`set_mem_attributes_minus_bitpos':
/gcc7/gnu/gcc-3.22/gcc/emit-rtl.c:1866: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/expr.c: In function `expand_assignment':
/gcc7/gnu/gcc-3.22/gcc/expr.c:3719: warning: unused variable
`old_expr'
/gcc7/gnu/gcc-3.22/gcc/fold-const.c: In function `lshift_double':
/gcc7/gnu/gcc-3.22/gcc/fold-const.c:418: warning: signed and unsigned
type in conditional expression
/gcc7/gnu/gcc-3.22/gcc/fold-const.c: In function
`div_and_round_double':
/gcc7/gnu/gcc-3.22/gcc/fold-const.c:723: warning: comparison between
signed and unsigned
/gcc7/gnu/gcc-3.22/gcc/function.c: In function
`assign_stack_temp_for_type':
/gcc7/gnu/gcc-3.22/gcc/function.c:764: warning: signed and unsigned
type in conditional expression

Cannot allocate 64 bytes after allocating 33334116 bytes
make.exe[2]: *** [s-attrtab] Error 1
make.exe[1]: *** [stage1_build] Error 2
make.exe: *** [bootstrap] Error 2


please, some djgpp's guru help?with my appreciation in advance.
  Reply With Quote
5 4th May 06:17
richard dawe
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


Hello.

The dj* packages were made on 2003-04-25 by me. I don't know about the
timestamps of the other packages. I guess Andrew uploaded new builds or
something. (Andrew Cottrell is building almost all of the packages for DJGPP 2.04 alpha.)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^
That is worrying.

I don't know if anyone else has tried DJGPP on Windows 2003 Enterprise Server.

That is not an error. It is a warning. Don't worry about that. It just means
that the gcc source is using constructs that are not standard C.

Warnings do not stop gcc from compiling and building.

Warnings sometimes indicate that there is a bug. Sometimes not. Generally it
is a good idea to fix warnings.

[snip]

Again, I wouldn't worry about the warnings.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^
That is worrying.


Since you're probably the first person to run DJGPP 2.04 alpha on Windows 2003
Enterprise Server, I'm not sure anyone can help you right now. I'll see if any
of the djgpp-workers (DJGPP developers) has access to Windows 2003.

Sorry, that's not much help.

Regards,

--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
  Reply With Quote
6 4th May 06:17
andrew cottrell
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


The June dates are for GCC 3.3.


Could be bin utils?


I have sent you a direct email in order to take this offline as it is
easy this way.

If you don't get it please let me know what your email is via the
following email adress after removing the '2' and adding the '.' at
the right spots:-

andrew2djgpp
@
swiftdsl2
com
2au


Andrew
  Reply With Quote
7 4th May 06:17
aiko_sex
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


well,:-)
I've successfully bootstrap the gcc under win2000 server use the 2.04
alpha,so, thanks all foe helping
  Reply With Quote
8 4th May 06:17
aiko_sex
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


same version dictory?(could 2.04 alpha mix to work together?or can I
replace the gcc322b.zip with gcc33b.zip when I use djgpp2.04 without
another packages to change with the same date satmp with the
gcc33b.zip?)

next:i found the "cxxfilt.exe" in the djdev204b.zip,and another one
also named "cxxfilt.exe" in the gpp322b.zip,what's about the two
?which one I should use? I found this make me too confused.
  Reply With Quote
9 4th May 06:17
mike
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


"Andrew Cottrell" <spam@bigpond.com.au>
??????:tq86lvcoaf7i2s7e73cojsdab9he6olbto@4ax.com. ..

####

gcc,

that, if

example:gcc321s.zip,gcc322s.zip,gcc323s.zip,gcc2.9 52s.zip.all

I do as you told,and i found if i use the 2.04alpha version to
bootstrap,then it still can't found the ___gxx_personality_v0 symbols and
other symbols in the libstdcxx.a at stage 3.the erros just the same as
above.
If I use 2.03 version ,then the erros like follows(blow is the all erros in
my redirect erros file):

cc1plus.exe: warning: -ffunction-sections may affect debugging on some
targets
In file included from
/dev/f/gcc6/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/
include/bits/fpos.h:45,
from
/dev/f/gcc6/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/
include/bits/char_traits.h:46,
from
/dev/f/gcc6/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/
include/string:47,
from
/dev/f/gcc6/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/
include/bitset:55,
from /gcc6/gnu/gcc-3.22/libstdc++-v3/src/bitset.cc:43:
/dev/f/gcc6/gnu/build.gcc/i586-pc-msdosdjgpp/libstdc++-v3/include/cwchar:65:
con
flicting
types for `typedef struct mbstate_t mbstate_t'
c:/djgpp/include/wchar.h:27: previous declaration as `typedef struct
mbstate_t
mbstate_t'
make.exe[4]: *** [bitset.lo] Error 1
make.exe[3]: *** [all-recursive] Error 1
make.exe[2]: *** [all] Error 2
make.exe[1]: *** [all-target-libstdc++-v3] Error 2
make.exe: *** [bootstrap] Error 2
it still stop at stage3.

I download all the 2.04 alpha from the mirro
ftp://ftp.iij.ad.jp/pub/djgpp/alpha( just used for above and the erros is
from this version ,i choosed all the same year and almost the same date
,except those no the same date foe me to choose,and so ,i choosed the near
date's)
and yet download all the alpha 2.04 from
http://clio.rice.edu/djgpp/win2k/main_204.htm, then still failed in stage
1.

all the version above i used the acnf213b.zip and amake14b for extra
requested in the gcc's readme.DJGPP.

I have make a ne dictory and install djgpp in the ne directory,but still
failed.(the erros just above)

how could I?
  Reply With Quote
10 4th May 06:17
andrew cottrell
External User
 
Posts: 1
Default about bootstrap the djgpp's gcc


It depends on if you are using C or C++ and if you come accross a bug
that was discovered after the alpha 1 release.

If you want to ensure that you don;t hit the bug then don't mix the
following files from alpha 1 and clio:-
djdev*.zip
gcc*b.zip

Here is the relevant part out of the GCC readme file :-
NOTE: Object files generated from C sources by gcc-3.3.1 will be
compatible with ones from earlier version, except gcc-3.2.2 where I
unfortunatelly introduced a bug, which breaked compatibility. Note
that binary archive of DJGPP v2.04 Alpha 1 is built using gcc-3.2.2,
so it's needed to rebuild it from sources, if You are going to use
this version (not needed with DJGPP v2.03 pachlevel 2, older versions
are not supported). Object files generated from C++ sources should be
compatible with ones from gcc-3.2, gcc-3.2.1, gcc-3.2.3. However I
would recommend to still use the same compilerm for all sources.

The "cxxfilt.exe" is not in the djdev204b.zip from ftp.delorie.com or
gpp322b.zip, it's in the bnu214b.zip. Use the one from bnu214.zip
  Reply With Quote
Reply


Thread Tools
Display Modes




Copyright 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666