Closed ghost closed 10 years ago
MMD-4 doesn't use glibc (and it never did... Nor does MMD-3 for quite a while). So you're doing something incorrectly.
Oops. I meant libc6 not glibc. I believe libc6 is being linked in. For example, the question here refers to the same.
nm ./multimarkdown | grep libc
:
0000000000728820 B __libc_argc
0000000000728828 B __libc_argv
:
nm multimarkdown | grep libc
on Mac OS X is empty. On Ubuntu 13.10, it results in __libc_csu_fini
, __libc_csu_init
, and __libc_start_main@@GLIBC_2.2.5
.
It appears that everything is handled differently based on the environment/OS. The changes you suggest fail when run on Mac OS X, but seem to work on Ubuntu 13.10. I don't know whether this is an entirely good idea, but I added the changes to the Makefile to allow make static
.
Thanks, I just pulled in your commit, confirm that it works.
Glad to hear it!
I compiled mmd-4 on a local Ubuntu machine and transferred it to a remote Debian Wheezy server. When I try to run the binary on the remote,
The error simply means that
Glibclibc6 was being linked dynamically instead of statically. GCC accepts-static
option to create a standlone, statically-linked binaries. I got it working by changing the top-level Makefile to:So, this bug report is for requesting to add this functionality. The default makefile target could be changed to build statically or may be create separate target, say,
make static
which will build the static version. Either of them are fine with me.EDIT: The following patch seems to work for enabling
make static
: