Unless it’s with a very old Linux binary, you no longer need to use brandelf(1) to run Linix binaries; you just need pkgsrc: emulators/suse100_base and a symlink.
A running description of activity related to DragonFly BSD.
A running description of activity related to DragonFly BSD.
Unless it’s with a very old Linux binary, you no longer need to use brandelf(1) to run Linix binaries; you just need pkgsrc: emulators/suse100_base and a symlink.
Since I just finished wrangling with it last night, I might mention that firefox-bin from pkgsrc pretty much Just Works -if- you make a DragonFly-specific Makefile out of the NetBSD-specific one in… whew, what is it, www/mozilla-bin or somesuch? (Having checked, whee, it’s now seamonkey-bin, so pkgsrc’s Firefox build now ‘relies’ on code that’s suddenly ‘for’ what’s no longer an official Mozilla project. Durf.)
The mess is in seamonkey-bin/Makefile.common, where the conditionals around “# Linux builds on NetBSD” and “# builds typically want exactly ‘libgtk-1.2.so.0’, etc. symlink them # into the mozilla directory.” need to apply to DragonFly as well. In my case, I just wrenched it enough to get it installed, then removed the symlinks manually — apparently the Linuxulator’s library search path also Just Works, while explicit links to native DF libraries obviously don’t.
Trivial changes, and if I get a chance I’ll try to make a clean patch… but I’m not exactly reliable with such things. (After all, I’m posting this here rather than on a mailing list, right?)