Skip to content
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

makefile erroring in a strange way #1

Open
rebmcr opened this issue Oct 11, 2023 · 2 comments
Open

makefile erroring in a strange way #1

rebmcr opened this issue Oct 11, 2023 · 2 comments

Comments

@rebmcr
Copy link

rebmcr commented Oct 11, 2023

Hi, thanks for hosting this repo, and sorry for raising this issue such a long time after its last commit! In case you are still interested in the content, perhaps this information is welcome:

I'm trying to compile the rastertoultra filter for CUPS (which I believe relates to the security overlay that these printers apply to cards), so I executed make in the root of the repo, and after a bunch of warnings and notes (which I think don't matter), I get this error:

/usr/bin/ld: /tmp/ccLF6Mtu.o: in function `main':
rastertoultra.c:(.text.startup+0x6c): undefined reference to `initializeSettings'
collect2: error: ld returned 1 exit status
make: *** [makefile:68: rastertoultra] Error 1

I've looked inside the rastertoultra.c file, and I can see that initializeSettings is indeed called inside main on line 7619, but also that it is actually defined starting on line 857, and unfortunately I don't know any C with which I could diagnose further.

I'm using Ubuntu 20.04 with the libcups2-dev package (cups-devel isn't available for this platform, but I believe they are equivalent) and my gcc version is 9.4.0 with ld 2.34 and make 4.2.1

Would you have any suggestions for tracing the cause of the error please?

@pc-coholic
Copy link
Owner

The original code is not by me but rather by Magicard - and since I never touched it that much in the first place, I do not have much insight in it's workings..

You might be better off asking Magicard for a mor up to date copy of the original archive and manually backporting my changes (if even required).

Sorry...

@rebmcr
Copy link
Author

rebmcr commented Oct 11, 2023

No worries! I wasn't aware how much of the source was their own, I'll get in touch with them thanks. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants