Created
September 29, 2016 00:15
-
-
Save petdance/cfa346c6614c56ca923886da8b7b71c2 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(blead) clifford:~/perlfromperlorg $ make malloc.o | |
clang -c -DPERL_CORE -D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_S | |
OURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -std=c89 -O3 -Wall -Werror=declaration-after-statement -Wextra -Wc++-compat -Wwrite-strings | |
malloc.c | |
malloc.c:257:4: error: "MYMALLOC is not defined" | |
# error "MYMALLOC is not defined" | |
^ | |
malloc.c:985:13: warning: implicit declaration of function 'malloced_size' [-Wimplicit-function-declaration] | |
*size = malloced_size(pv) + M_OVERHEAD; | |
^ |
Using perlbrew, I tried make malloc.o
on 5.10.0, 5.14.4 and 5.20.3. Same (or very similar) errors.
My hunch is that make malloc.o
is not a valid make
target and never has been.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Andy, when I configure with
sh ./Configure -des -Dusedevel -Dcc=clang
and then call:
make malloc.o
I get failures like yours:
And this is independent of which C compiler I use. Omitting
-Dcc=clang
-- thereby defaulting to gcc -- gives the same failures.However, when I simply call
make
, I get a successful build. (blead on Ubuntu Linux 16.04 LTS)I should note that I have never previously called
make malloc.o
, so I don't have any idea how it should normally behave.How are you configuring?
Thank you very much.
Jim Keenan