Re: [Tinycc-devel] RE : [RFC] Moving source code to src

2015-07-29 Thread Michael Matz
Hi,

On Mon, 27 Jul 2015, gus knight wrote:

 On Mon, Jul 27, 2015 at 12:48 PM, Christian JULLIEN eli...@orange.fr wrote:
  Hi Gus,
 
  This is a good idea. If you do so, I also suggest an arch directory that
  contains subdirectories for all supported archives
 
 I wound up going with one dir per arch rather than an arch
 directory. Let me know if there are any regressions.

$ cd tinycc
$ ./configure  make
...
make: *** No targets specified and no makefile found.  Stop.

Sigh.  Also make -C src is broken, the documentation in particular:

$ make -C src
...
./texi2pod.pl ../docs/tcc-doc.texi tcc.pod
make: ./texi2pod.pl: Command not found
make: [tcc.1] Error 127 (ignored)
pod2man --section=1 --center=Tiny C Compiler --release=`cat ./../VERSION` 
tcc.pod  tcc.1
Can't open tcc.pod: No such file or directory at /usr/bin/pod2man line 60.
make: [tcc.1] Error 2 (ignored)

This is because you've moved texi2pod.pl from ./ into ./docs/ but haven't 
changed the makefile.  Please fix.


Ciao,
Michael.

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


Re: [Tinycc-devel] RE : [RFC] Moving source code to src

2015-07-29 Thread Vincent Lefevre
On 2015-07-29 09:00:18 -0400, gus knight wrote:
 Ah, oops. Looks like make didn't fail on the docs command as I expected it to.

Also, don't forget to test out-of-tree builds with a read-only source
directory.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/
100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


Re: [Tinycc-devel] RE : [RFC] Moving source code to src

2015-07-29 Thread gus knight
On Wed, Jul 29, 2015 at 8:58 AM, Michael Matz matz@frakked.de wrote:
 make: *** No targets specified and no makefile found.  Stop.

 Sigh.  Also make -C src is broken, the documentation in particular:

 $ make -C src
 ...
 ./texi2pod.pl ../docs/tcc-doc.texi tcc.pod
 make: ./texi2pod.pl: Command not found
 make: [tcc.1] Error 127 (ignored)
 pod2man --section=1 --center=Tiny C Compiler --release=`cat ./../VERSION` 
 tcc.pod  tcc.1
 Can't open tcc.pod: No such file or directory at /usr/bin/pod2man line 60.
 make: [tcc.1] Error 2 (ignored)

 This is because you've moved texi2pod.pl from ./ into ./docs/ but haven't
 changed the makefile.  Please fix.

Ah, oops. Looks like make didn't fail on the docs command as I expected it to.

-gus

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


[Tinycc-devel] RE : [RFC] Moving source code to src

2015-07-27 Thread Christian JULLIEN
Hi Gus,
This is a good idea. If you do so, I also suggest an arch directory that 
contains subdirectories for all supported archives
arch/armarch/arm64arch/i386...
I'm afraid this code refactory will take long until it works on all platforms 
(including Windows).
Talking about Windows, who has a good Makefile producing standalone tcc for 
x86/x64 using recent Cygwin toolchain (and no more using Cygwin after it has 
been compiled).My dream would be a unique tcc.exe having -m32/-m64 option.

- message d'origine -
De : gus knight lt;waddlespl...@gmail.comgt;
date lun. 27/07/2015 18:25 (GMT +02:00)
À : TinyCC ML lt;tinycc-devel@nongnu.orggt;
Objet : [Tinycc-devel] [RFC] Moving source code to src

Hi,

ATM the root directory of TinyCC is a bit cluttered, mostly because
the core of TinyCC's code is there. I propose moving it to a src
subdirectory.

-gus

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


Re: [Tinycc-devel] RE : [RFC] Moving source code to src

2015-07-27 Thread Chris Marshall
I've not yet been able to build tcc on cygwin, neither in the
unix context provided by cygwin, nor with the --enable-cygwin
option which is out of date with the gcc naming schemes for
the mingw compilers on cygwin.

On Mon, Jul 27, 2015 at 12:48 PM, Christian JULLIEN eli...@orange.fr
wrote:

 Hi Gus,

 This is a good idea. If you do so, I also suggest an arch directory that
 contains subdirectories for all supported archives

 arch/arm
 arch/arm64
 arch/i386
 ...

 I'm afraid this code refactory will take long until it works on all
 platforms (including Windows).

 Talking about Windows, who has a good Makefile producing standalone tcc
 for x86/x64 using recent Cygwin toolchain (and no more using Cygwin after
 it has been compiled).
 My dream would be a unique tcc.exe having -m32/-m64 option.


This should be doable if the various build assumptions that break
now can be fixed.

Regards,
Chris
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel