Wed Dec 10 14:50:00 GMT 2014
* Marco Atzeri <email@example.com> [141210 15:41]:
> I was just suggesting the usage of a "standard" config systems:
> Automake, cmake...
No, this has been discussed internally befor many times. The project
already moved from autotools, scons, cmake to the current state.
So far it served us very well for a lot of different architectures
with minimal fuss (AIX, Haiku, GNU Hurd, minix, windows). This is
a community land mine.
> Attached a better chicken.cygport that allow the
> build on separate tree, identify the architecture
> correctly install and package.
> This also avoid the creation of not needed
> You still need to verify the check portion,
> it seems that the test in place is not fully working
> but I could be wrong.
Also if /usr is the preferred PREFIX it should be set to the same
value when calling make and make install.
Yes, the check portion should be just calling "make check".
> About x86_64 there is still a starting problem
> gcc -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES
> -c apply-hack.x86-64.S -o apply-hack.x86-64.o
> apply-hack.x86-64.S: Assembler messages:
> apply-hack.x86-64.S:32: Warning: .type pseudo-op used outside of .def/.endef
> apply-hack.x86-64.S:32: Error: junk at end of line, first unrecognized
> character is `_'
Thanks insteresting. Which gcc is this? Are you sure you build with
a 64 bit assembler there?
May you be peaceful, may you live in safety, may you be free from
suffering, and may you live with ease.
More information about the Cygwin-apps