-
Notifications
You must be signed in to change notification settings - Fork 168
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
hardcoded architecture #17
Comments
Also, the whole linux build environment seems to assume gcc is the standard compiler. Both Xcode and FreeBSD are on their way to phase out gcc in favor of LLVM/clang. It would be very nice if ‘linux/gcc’ could be made more BSD friendly. |
Should probably be a separate issue. At the very least, one can do |
Feel free to fix this. I know almost nothing about the Linux environment; I learned just enough to make a Linux build for the roughly 4 users who have asked for it. I do want the build system to continue to make 32 bit builds only. This is because type developers typically don't have money to upgrade machines very often, and 2 of four Linux flavor FDK users (that I know about) are still running 32 bit intel systems. |
I think you are hugely underestimating the number of Linux users of this suite of tools :). |
I agree with @behdad. Although a small number of people specifically requested it, I am sure that the number of people using AFDKO on Linux is much larger. A quick search of social media activity suggests this. |
32-bit dependence is a bug; it should not be happening. And not everyone even has a multilib environment capable of building and running 32-bit programs. I would think fixing this ought to be a priority even without known users. |
Is the FDK instrumented to report daily users? :) |
Thank you. I see that I can still build 32 bit executables for my FDK distribution simply by building on a 32 bit Linux system. |
The flag
-m32
is littered throughout the build configuration.Is there any reason for this? If you're fine with removing it, I'd be happy to make a pull request.
The text was updated successfully, but these errors were encountered: