-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dxegen: unresolved symbol `___libemu_ident_string' #46
Comments
Wouldn't patching out the |
Yeah, I suppose that would work. In fact, I don't really see why both --- a/src/libemu/makefile
+++ b/src/libemu/makefile
@@ -12,7 +12,8 @@ include $(TOP)/../makefile.lib
all :: $(BIN)/emu387.dxe
$(BIN)/emu387.dxe : src/emu387.o src/emudummy.o
- $(HOSTBIN)/dxegen.exe $(BIN)/emu387.dxe __emu_entry src/emu387.o id_emu.o src/emudummy.o -L../../lib $(LIBGCCA) -lc $(LIBGCCA)
+ $(CROSS_GCC) -c -DLIB=libemu $(TOP)/../ident.c -o id_emudxe.o
+ $(HOSTBIN)/dxegen.exe $(BIN)/emu387.dxe __emu_entry src/emu387.o id_emudxe.o src/emudummy.o -L../../lib $(LIBGCCA) -lc $(LIBGCCA)
clean ::
$(MISC) rm makefile.sub |
I guess that would also work, sure. |
well, I just noticed the missing is it possible to only build the static library? |
This error sporadically appears while building djgpp's libemu:
Digging through the makefiles:
bin/emu387.dxe
requiresid_emu.o
, but is not listed as prerequisiteid_emu.o
is built in the recipe forlib/libemu.a
lib/libemu.a
is built in the recipe forall::
inmakefile.lib
(via recursive make)all::
inlibemu/makefile
listsbin/emu387.dxe
as prerequisiteSo there is a sort-of circular dependency, and whether this fails or not depends on the evaluation order of
all::
.It probably works consistently with non-parallel make, but this still looks pretty fragile.
We don't actually need to build this though, the DXE is not currently installed anywhere. I suppose I could put it in
i386-pc-msdosdjgpp/lib/
for completeness. For now, I think I'll drop libemu altogether. If anyone does need this, please complain below.The text was updated successfully, but these errors were encountered: