Fails to build in

[GoogleCodeExporter]

Fails to build in

[GoogleCodeExporter]

Fails to build in FreeBSD

line in ./src/ctemplate/template_string.h:
typedef TemplateId; 
fails.

had to change it to:
typedef __uint64_t TemplateId;

Original comment by [email protected] on 28 Sep 2009 at 4:56

[GoogleCodeExporter]

Strange.  I've successfully compiled this on FreeBSD (6.0).

This looks to be an issue with the configure run.  Can you attach your 
config.log file?

Original comment by [email protected] on 29 Sep 2009 at 6:50

• Added labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

Looking back into my bash_history to confirm, I ran configure like this:
CPPFLAGS="-Os -march=native -fomit-frame-pointer" ./configure

which runs fine on my Gentoo box.  If it helps, my Gentoo uses gcc 4.4.1 and my
FreeBSD uses 4.2.1, also:

[root@marconi /etc]# uname -a
FreeBSD marconi.domain 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan  1 14:37:25 
UTC
2009     [email protected]:/usr/obj/usr/src/sys/GENERIC  i386

Original comment by [email protected] on 29 Sep 2009 at 10:57

Attachments:

• config.log

[GoogleCodeExporter]

OK, something really weird is going on here.  Your config.log says:
   ac_cv_uint64=''

But the configure script says:
---
if test "$ac_cv_type_u_int64_t" == "yes"; then
   ac_cv_uint64=u_int64_t

elif test "$ac_cv_type_uint64_t" == "yes"; then
   ac_cv_uint64=uint64_t

elif test "$ac_cv_type___int64" == "yes"; then
   ac_cv_uint64=unsigned __int64

else
   ac_cv_uint64=unsigned long long
   # best we can do
fi
---

I don't see any way ac_cv_uint64 could be assigned to ''.  Does your configure 
script
also have that code snippet above?

Actually, I'm very suspicious of this:
---
line in ./src/ctemplate/template_string.h:
typedef TemplateId; 
fails.
---

Is that verbatim what you had in the file?  I would have expected two spaces 
between
typedef and TemplateId.  Maybe you can attach this entire file?

Original comment by [email protected] on 29 Sep 2009 at 11:12

[GoogleCodeExporter]

Yes, my configure has that, verbatim, and I found something very similar in
configure.ac.

Yes, your right, I did not copy it properly, the correct is:

typedef  TemplateId;

I'm attaching all the files that were generated by the configure script.  I
extracted the tar.gz file in a new location, ran configure and tar'ed all the 
files
listed at the end of the script that were created; e.g. 

config.status creating Makefile

Original comment by [email protected] on 30 Sep 2009 at 11:01

Attachments:

• files.tgz

[GoogleCodeExporter]

Thanks.  I don't see any smoking guns in these files, unfortunately.  Can you 
also
attach your config.status file?  Might as well throw in your configure script 
for
good measure.

Original comment by [email protected] on 1 Oct 2009 at 4:57

[GoogleCodeExporter]

tar czvf config.tgz config*     ;-)

Original comment by [email protected] on 1 Oct 2009 at 5:13

Attachments:

• config.tgz

[GoogleCodeExporter]

OK, I'm at a loss.  Everything seems to be working properly, to me.  My only 
guess is
I have a bash-ism in there somewhere.  What happens when you run
   bash configure
instead of just ./configure?

Original comment by [email protected] on 2 Oct 2009 at 8:21

[GoogleCodeExporter]

'bash configure' works fine!

Original comment by [email protected] on 6 Oct 2009 at 5:13

Attachments:

• works.tgz

[GoogleCodeExporter]

OK, I'm going to assume it's that == is a bash-ism, then.  I've fixed this for 
the
next release.  Let's revisit this bug then and see if it's fixed for you.

Original comment by [email protected] on 13 Oct 2009 at 1:02

• Changed state: Started

[GoogleCodeExporter]

Which '=='?  Could you attach the file with this fix so I could test it?

Original comment by [email protected] on 19 Oct 2009 at 3:48

[GoogleCodeExporter]

This should be fixed in ctemplate 0.96, just released.  If not, please feel 
free to
reopen the bug.

Original comment by [email protected] on 20 Oct 2009 at 5:32

• Changed state: Fixed

[GoogleCodeExporter]

I've tested it and can confirm: it has been fixed.
Thank you.

Original comment by [email protected] on 20 Oct 2009 at 6:15