https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198738
--- Comment #4 from Dimitry Andric <d...@freebsd.org> --- I think this may depend entirely on the port. In your example of devel/sdl20, its Makefile contains: OPTIONS_DEFINE= ALSA ASM DLOPEN ESOUND MMX NAS OSS \ PULSEAUDIO PTHREADS SSE SDL_ATOMIC SDL_AUDIO \ SDL_CPUINFO SDL_EVENTS SDL_FILE SDL_HAPTIC \ SDL_JOYSTICK SDL_LOADSO SDL_POWER SDL_RENDER \ SDL_THREADS SDL_TIMERS SDL_VIDEO VIDEO_OPENGL VIDEO_X11 OPTIONS_DEFAULT= ASM DLOPEN OSS PTHREADS SDL_ATOMIC SDL_AUDIO \ SDL_CPUINFO SDL_EVENTS SDL_FILE SDL_HAPTIC \ SDL_JOYSTICK SDL_LOADSO SDL_POWER SDL_RENDER \ SDL_THREADS SDL_TIMERS SDL_VIDEO VIDEO_OPENGL VIDEO_X11 OPTIONS_DEFAULT_i386= MMX SSE OPTIONS_DEFAULT_amd64= MMX SSE and then later on: SSE_CONFIGURE_ENABLE= sse sse2 ssemath this causes bsd.options.mk to pass all three as 'enable' options to sdl20's configure script: # ${opt}_CONFIGURE_ENABLE Will add to CONFIGURE_ARGS: # Option enabled --enable-${content} # Option disabled --disable-${content} So in case of the sdl20 port, enabling the *port* SSE option will enable both the SSE and SSE2 *configure* options. This is probably debatable. But it is trickier to have two separate port options for SSE and SSE2, I guess. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information