I've run into this problem too while compiling ChucK for the Raspberry Pi.
The solution is to edit util_string.cpp by adding this line:
#include <limits.h>
I don't know why this wasn't an issue before, but it builds fine for me
after this fix.
Joel
On 12/04/2013 09:16 AM, Jeff Jacobson wrote:
After running 'make linux-alsa' things run smoothly until:
g++ -I. -Ilo -O3 -D__LINUX_ALSA__ -D__PLATFORM_LINUX__ -O3
-fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c ulib_regex.cpp -o
ulib_regex.o
ulib_regex.cpp: In function 'void regex_replace(void*,
Chuck_DL_Return*, Chuck_VM_Shred*, CK_DL_API)':
ulib_regex.cpp:308:19: warning: converting to non-pointer type 'long
int' from NULL [-Wconversion-null]
RETURN->v_int = NULL;
^
ulib_regex.cpp: In function 'void regex_replaceAll(void*,
Chuck_DL_Return*, Chuck_VM_Shred*, CK_DL_API)':
ulib_regex.cpp:397:19: warning: converting to non-pointer type 'long
int' from NULL [-Wconversion-null]
RETURN->v_int = NULL;
^
g++ -I. -Ilo -O3 -D__LINUX_ALSA__ -D__PLATFORM_LINUX__ -O3
-fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c util_buffers.cpp -o
util_buffers.o
g++ -I. -Ilo -O3 -D__LINUX_ALSA__ -D__PLATFORM_LINUX__ -O3
-fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c util_console.cpp -o
util_console.o
g++ -I. -Ilo -O3 -D__LINUX_ALSA__ -D__PLATFORM_LINUX__ -O3
-fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c util_string.cpp -o
util_string.o
util_string.cpp: In function 'std::string get_full_path(const string&)':
util_string.cpp:393:14: error: 'PATH_MAX' was not declared in this scope
char buf[PATH_MAX];
^
util_string.cpp:395:42: error: 'buf' was not declared in this scope
char * result = realpath(fp.c_str(), buf);
^
makefile:144: recipe for target 'util_string.o' failed
make: *** [util_string.o] Error 1
My googling found no similar errors. Versions of dependencies are as
follows:
alsa-lib 1.0.27.2-1
alsa-utils 1.0.27.2-1
libsndfile 1.0.25-3
gcc 4.8.2-5
flex 2.5.37-1
bison 3.0.1-1
make 4.0-1
I'm new to building software from source so I apologize if this is a
beginner's misunderstanding. Thanks for any help you can give me; I'm
looking forward to trying ChucK.
_______________________________________________
chuck-users mailing list
[email protected]
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________
chuck-users mailing list
[email protected]
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
