Is there a package for pkgsrc for emacs-nox11 that has support for dynamic modules?

neirac: I don't use emacs, what does that look like in practice and what errors, if any, are our current packages outputting?

jperkin I use vterm in emacs and that pop ups an error : Your build of Emacs lacks dynamic modules support

that should be a flag when compiling, I'm trying to build it myself to get used to the process, this is still valid? perkin.org.uk/pages/pkgsrc-binary-packages-for-osx.html , I don't want to do the pbulk way I'm just building one package, is that possible ?

just git clone pkgsrc, go to the directory of the software and bmake ?

I just migrated from homebrew I found a couple of packages that should be quick to add once I get use to the process, and at the end I'm using pkgsrc in my servers so is just easier to just consolidate in pkgsrc

for emacs is just add --with-modules on the configure step

that link is pretty old at this point, you can either bootstrap yourself or install my binary packages and then just build emacs

if you're using my binaries then adding DEPENDS_TARGET=bin-install and BINPKG_SITES=pkgsrc.smartos.org/packages/Darwin/11.3/arm64 (or x86_64) to /opt/pkg/etc/mk.conf.local will install binary packages as dependenceis

I should probably put those in my release mk.conf

the other thing you may need to add is OSX_SDK_PATH pointing to a valid SDK in /Library/Developer/CommandLineTools/SDKs, as I specifically use an older SDK in my binary packages to make the work across multiple OS releases

I'll ask on the list why it's not enabled and unless there are objections I'll add it

jperkin thanks!, I'll try to make those changes to see if I could build a package in macos, now I'm just getting configure: error: cannot run C compiled programs.

have a look at config.log, but that could be due to the OSX_SDK_PATH thing

jperkin I see clang: error: unsupported option '-V -isysroot' I'll add the OSX_SDK_PATH to mk.conf then

e.g. on my laptop I have OSX_SDK_PATH=/Library/Developer/CommandLineTools/SDKs/MacOSX13.3.sdk

I just built it --with-modules and it builds and runs at least

jperkin what's the value ofMACOSX_DEPLOYMENT_TARGET in your /opt/pkg/etc/mk.conf

11.3, that's what my build machines use

I could probably ditch that at release time too

be nice if building stuff worked out of the box for everyone

ok, so commenting out MACOSX_DEPLOYMENT_TARGET is probably simplest, then in theory you don't need to set OSX_SDK_PATH

if I comment MACOS_DEPLOYMENT_TARGET bmake fails with ERROR: No suitable Xcode SDK or Command Line Tools installed.

jperkin adding BINPKG_SITES and DEPENDS_TARGET=bin-install make it advance but fails saying there is no dlopen? is odd that should be in every unix as far as I know paste.ec/paste/KyT4USHp#maNmXGpw+dwMBeY+bxeHV1PLnul0LrmeOwW+giCFpHH

is "/usr/bin/xcrun --sdk macosx --show-sdk-path" empty or something?

output for that command is: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk

but there's no /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk/usr/include/stdio.h?

there is one, file /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk/usr/include/stdio.h: c program text, ASCII text

just trying to figure out how you are reaching here: github.com/NetBSD/pkgsrc/blob/trunk/mk/platform/Darwin.mk#L131

oh, do you still have OSX_SDK_PATH set?

I just tried without OSX_SDK_PATH set, same result this is my /opt/pkg/etc/mk.conf file termbin.com/a5q2

the last commit for the pkgsrc branch I'm using is ab899660f03794280338b3d7f2f27ba99de4ae80

that's from Thu Oct 13 20:54:47 2022 +0100 , is that ok?

no that's not right, that's the old macos release branch

it's now "release/macos"

that'll explain the SDK issues as the code has been updated since then

jperkin, I copied the fetch repositories part of github.com/TritonDataCenter/pkgsrc/wiki/pkgdev:setup#os-setup-macos from joyent/release/macos now it should be just release/macos right?

yeh. I'll review and fix that page

at least now I have a different error: ERROR: No suitable Xcode SDK or Command Line Tools installed. when executing bmake

that's with nothing set related to OSX_SDK_PATH or MACOSX_DEPLOYMENT_TARGET at all?

oh, I know what the problem is

so for now if you just 'git checkout trunk' and remove any OSX_SDK_PATH or MACOSX_DEPLOYMENT_TARGET from your mk.conf it should work

the problem is my release/macos branch has this commit: NetBSD/pkgsrc ddcfc89

which helps speed up my bulk build host, but then messes things up if you're using it on a different system

there are relatively few changes on release/macos compared to trunk so there's no harm in just using trunk

jperkin I'll try using trunk

jperkin I removed OSX_SDK_PATH and MACOSX_DEPLOYMENT_TARGET from /opt/pkg/etc/mk.conf but I'm still getting ERROR: No suitable Xcode SDK or Command Line Tools installed., the last commit I see in this branch is 296ddb24c8d625752094d4d051693cb883110af3 December 28, 2023

git pull should get you newer but shouldn't affect this. what does 'bmake -v OSX_SDK_PATH' say, and does that path exist?

I can't reproduce that here with apparently the same settings, just make sure they aren't set in the environment or similar

bmake -v OSX_SDK_PATH returns nothing

huh, that shouldn't be possible

you're within a pkgsrc directory, right?

jperkin, yes I'm on ~/Projects/OSS/pkgsrc/editors/emacs28-nox11 and typed bmake -v OSX_SDK_PATH

I'm reading an old pkgsrc thread regarding the same I hope it has a happy ending mail-index.netbsd.org/tech-pkg/2016/01/06/msg016237.html

jperkin now is working now!

jperkin after I understood your instructions and read this stix.id.au/wiki/pkgsrc_on_Mac_OS_X it started working

now I have fortunes installed

going for emacs now

finally it worked, now I'm running emacs-29-nox11 with dynamic modules support, thanks jperkin

oh was xcode not installed correctly?

hopefully you shouldn't need to set OSX_SDK_PATH as per that last blog, if you're on trunk then it should work with all the settings removed

thanks for going through this, it's always helpful to get a fresh perspective, I'll clean up the docs and the bootstrap kits so this all works out of the box

jperkin I tried with and without it, it works

I think I have hit some bug on SmartOS install with not being able to make ' zones ' ZFS pool bootable even if option is selected during the install stage. Have done it 2 times on hardware (this time with UUID visible)

Not necessarily a bug.

Is the pool one that's bootable?

(if you escape into a shell during installation, what does `zpool list -v zones` say?)

The automated pool creation can sabotage `zpool create -B` and the installer will dutifully roll back to `zpool create`.

To be fair it's a bug maybe in that we aren't as helpful in detailing the situation.

hello - curious if anyone can point me to some docs or other resources for migrating from a freebsd/bhyve hypervisor to smartOS. i'm specifically curious to see how people imported the freebsd VM's into smartOS.

the challenge is my VM's are raw disk images, not zvols

Is pkgsrc.smartos.org experiencing overload, or is it just me?

oh, sorry for the noise, i should have read the handbook more closely. there seems to be a great example of doing this with vmware images using qemu-im convert.