Open anr2me opened 5 months ago
For the uuid
header issue, you'll need to install libuuid
. I believe for CentOS/RedHat based distros, it is the following install:
sudo yum install libuuid libuuid-devel
Since make config=release
failed with an error.
Will the make -f Bootstrap.mak linux
creates a release version? or build version?
I'm not 100% sure, what you can do is run make -f Bootstrap.mak
to create a premake binary, use that premake binary to generate new makefiles with the gmake2
exporter, then run make
on the newly generated makefiles to ensure you've built release. A bit of a roundabout way to do it, but it works well (and is how you would do it if you're building from repository sources instead of release sources).
Just following up to see if this resolved your question.
Sorry i didn't had the chance to try it yet (kinda busy with other things), i will update/close this issue if it works.
Apparently, doing make -f Bootstrap.mak linux
gets the same error to make config=release
ssl_msg.c
select.c
../../contrib/mbedtls/library/ssl_msg.c: In function ‘mbedtls_ssl_cf_memcpy_if_eq’:
../../contrib/mbedtls/library/ssl_msg.c:1169:5: error: ‘for’ loop initial declarations are only allowed in C99 mode
for( size_t i = 0; i < len; i++ )
^
../../contrib/mbedtls/library/ssl_msg.c:1169:5: note: use option -std=c99 or -std=gnu99 to compile your code
sendf.c
share.c
make[2]: *** [obj/Release/mbedtls-lib/ssl_msg.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Btw, I can get a working premake4 binary by installing rpm from opensuse leap 15.5 https://opensuse.pkgs.org/15.5/opensuse-oss-x86_64/premake4-4.4beta4-bp155.2.10.x86_64.rpm.html
And do premake4 gmake
(since gmake2
is not valid on premake4), followed by make
But getting an error:
==== Building Premake5 (release) ====
Creating obj/Release
ldump.c
lmem.c
lstate.c
liolib.c
loslib.c
lapi.c
lparser.c
ltable.c
...
os_copyfile.c
lua_auxlib.c
path_normalize.c
Linking Premake5
obj/Release/os_uuid.o: In function `os_uuid':
os_uuid.c:(.text+0xb4): undefined reference to `uuid_generate'
collect2: error: ld returned 1 exit status
make[1]: *** [bin/release/premake5] Error 1
make: *** [Premake5] Error 2
I've also tried to do make clean
before make
but still getting the same error.
Before opening a new issue, please use the issue search feature to see if a similar issue already exists. If not, please help us help you by filling in the template below.
What are you trying to do? A short, concise description of the outcome you are trying to achieve, ex. "Add build settings to a specific file".
I want to try building premake5 from release source:
Due to the pre-built binary requires a different version of shared
libm.so.6
andlibc.so.6
(the one i have are a different GLIBC versions, and i'm not sure how to get those missing specific version properly):What problem are you having? A clear and concise description of the problem that is blocking you from your desired outcome, ex. "Premake is crashing with this error message: ..." or "I don't know how to do it."
Getting this error while doing
make config=release
I've also tried
make -f Bootstrap.mak linux
but getting a different error:What have you tried so far? Describe any steps you've already taken to try to get past this issue.
Not sure what to do here, i wished there is an easier way to get premake on CentOS 7 (eg. through
yum
or something) or at least the pre-built binary doesn't relies on specific version of shared libs (specific major version are okay) or use static libs.What version of Premake are you using?
premake5 --version
will show you the version. If you are running a "-dev" version, please make sure you are up to date with the latest master branch. Doesn't have any working premake.Anything else we should know? Add any other context about the problem here.
Btw, I'm using gcc & g++ 4.8.5 which came from
yum install gcc g++
, and libc fromyum install glibc
, not sure what else needed to be installed as there are no library/package prerequisites that need to be installed first on premake's build guide/wiki.(You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to issues like these!)