#325 Problem with making

closed-invalid
None
5
2003-02-18
2002-04-11
Anonymous
No

Hello Sandeep

1 The cygwininst.txt file, referred to in
sdcc\doc\bccinst.txt,
does not appear to be in the sdcc-2.3.0.tar.gz
download.

2 My attempt to build SDCC from Cygwin,
using 'make -fMakefile'
causes Make to object to line 9 with 'Makefile.common:
No such file..'.
Makefile.common does not appear to be in the download,
though there is a Makefile.common.in .
Commenting out line 9 (the reference to
Makefile.common) causes
Make to generate the following:

$ make -fMakefile
for lib in support/cpp support/cpp2; do make -C $lib;
done
make[1]: Entering directory
`/cygdrive/c/sdcc/support/cpp'
make[1]: *** No targets specified and no makefile
found. Stop.
make[1]: Leaving directory
`/cygdrive/c/sdcc/support/cpp'
make[1]: Entering directory
`/cygdrive/c/sdcc/support/cpp2'
make[1]: *** No targets specified and no makefile
found. Stop.
make[1]: Leaving directory
`/cygdrive/c/sdcc/support/cpp2'
make: *** [sdcc-libs] Error 2

3 My attempt to build SDCC using Borland's bcc32
has so far also been unsuccessful.

4 My purpose in recompiling is to build a Win32
version of SDCC
in which all outputs to stdout and stderr are to one
or more ASCII files. This will enable me
to build a simple IDE, using MS's VC6, for use in
Windows.

Sorry to trouble you; can you find the time to help me?

Graham Wilson

Discussion

  • Johan Knol

    Johan Knol - 2003-02-18
    • assigned_to: nobody --> johanknol
    • status: open --> closed-invalid
     
  • Johan Knol

    Johan Knol - 2003-02-18

    Logged In: YES
    user_id=63512

    sdcc build perfectly using ./configure

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks