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
Closed
mukeshhope opened this issue
Aug 17, 2021
· 11 comments
Assignees
Comments
Host Environment
- OS: Windows 10 enterprise
To Reproduce
Steps to reproduce the behavior:
vcpkg.exe install azure-iot-sdk-c:x64-windows
Failure logs
Computing installation plan...
The following packages will be built and installed:
* azure-c-shared-utility[core]:x64-windows -> 2020-12-09#1
azure-iot-sdk-c[core]:x64-windows -> 2020-12-09#2
* azure-macro-utils-c[core]:x64-windows -> 2020-06-17#2
* azure-uamqp-c[core]:x64-windows -> 2020-12-09
* azure-uhttp-c[core]:x64-windows -> 2020-12-09
* azure-umqtt-c[core]:x64-windows -> 2020-12-09
* parson[core]:x64-windows -> 2020-09-14
* umock-c[core]:x64-windows -> 2020-06-17-1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
Could not locate cached archive: C:UsersmuctAppDataLocalvcpkgarchives7b7bac0664f0e9df9f61fac88be02428313d51beed192af5c0e39fbd9c87e849ce.zip
Could not locate cached archive: C:UsersmuctAppDataLocalvcpkgarchives828209cbb0a2fd9cb220dceea999ec55dc19dc1e1a010e7855ec5ae5b52f7d786d.zip
Could not locate cached archive: C:UsersmuctAppDataLocalvcpkgarchivesa9a993f2fcddddd9771ce34281b3b1e0f6650a966a82e26399075df7da7aa62f6e.zip
Could not locate cached archive: C:UsersmuctAppDataLocalvcpkgarchivesdbdb8f54c3217020a14566723741e3b799826d69503ea266bbc67cff342b023fbe.zip
Could not locate cached archive: C:UsersmuctAppDataLocalvcpkgarchivesd5d557b25766af0c89fa9102f9d313c4b852d27ff485277dcd37330ba005eb26fd.zip
Could not locate cached archive: C:UsersmuctAppDataLocalvcpkgarchives5353ee7d13c30909e5b25589473008bce1e4f4cbac6ee5332ee97013f6e6f40b27.zip
Could not locate cached archive: C:UsersmuctAppDataLocalvcpkgarchivesefefc5c597a049427bd09a1b76a1086d4565ff09fbe3cfef0f94d5fd69440ce419.zip
Could not locate cached archive: C:UsersmuctAppDataLocalvcpkgarchives5f5f7f0dae07ea17ea58d2396d462e04daf46849c21f3f7580f2ab718e92349bea.zip
Starting package 1/8: azure-macro-utils-c:x64-windows
Building package azure-macro-utils-c[core]:x64-windows...
-- Note: azure-macro-utils-c only supports static library linkage. Building static library.
-- Downloading https://github.com/Azure/azure-macro-utils-c/archive/5926caf4e42e98e730e6d03395788205649a3ada.tar.gz -> Azure-azure-macro-utils-c-5926caf4e42e98e730e6d03395788205649a3ada-1.tar.gz...
-- Extracting source C:/Mukesh/IOTedge/vcpkg/downloads/Azure-azure-macro-utils-c-5926caf4e42e98e730e6d03395788205649a3ada-1.tar.gz
-- Using source at C:/Mukesh/IOTedge/vcpkg/buildtrees/azure-macro-utils-c/src/05649a3ada-59e162c9fa.clean
-- Found external ninja('1.10.2').
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
Command failed: ninja -v
Working Directory: C:/Mukesh/IOTedge/vcpkg/buildtrees/azure-macro-utils-c/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
C:MukeshIOTedgevcpkgbuildtreesazure-macro-utils-cconfig-x64-windows-out.log
Call Stack (most recent call first): scripts/cmake/vcpkg_configure_cmake.cmake:356 (vcpkg_execute_required_process)
ports/azure-macro-utils-c/portfile.cmake:23 (vcpkg_configure_cmake)
Additional context
log file attached
config-x64-windows-out.log
@mukeshhope ,Thanks for posting this issue,try removing your current build files and starting over. From the Pangolin root directory
Hi @JonLiu1993 ,
I tried by removing whole vcpkg folder and then git clone again but it did not work.
What do you mean my Pangolin root directory, I could not understand this.
Thankyou for quick response
FAILED: ../../x64-windows-dbg/CMakeCache.txt
cmd /c "cd ../../x64-windows-dbg && "C:/Mukesh/IOTedge/vcpkg/downloads/tools/cmake-3.21.1-windows/cmake-3.21.1-windows-i386/bin/cmake.exe" "C:/Mukesh/IOTedge/vcpkg/buildtrees/azure-macro-utils-c/src/05649a3ada-59e162c9fa.clean" "-Drun_int_tests=OFF" "-DCMAKE_MAKE_PROGRAM=C:/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=OFF" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Mukesh/IOTedge/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/Mukesh/IOTedge/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/Mukesh/IOTedge/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/Mukesh/IOTedge/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/Mukesh/IOTedge/vcpkg/packages/azure-macro-utils-c_x64-windows/debug""
The system cannot find the path specified.
Maybe a permission issue. Can you please retry on non-system disk?
Thanks.
Hi Jack..
I started command prompt as administrator.
I do not have a non-system disk right now on my computer.
Thankyou for your response
@mukeshhope ,I can’t produce the error in system disk ,please use powershell as administrator to try again
-- Using source at C:/test1/vcpkg/buildtrees/azure-iot-sdk-c/src/eff40b92ec-46a358aeca
-- Found external ninja('1.10.2').
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Performing post-build validation
-- Performing post-build validation done
Building package azure-iot-sdk-c[core]:x64-windows... done
Installing package azure-iot-sdk-c[core]:x64-windows...
Installing package azure-iot-sdk-c[core]:x64-windows... done
Elapsed time for package azure-iot-sdk-c:x64-windows: 22.23 s
Total elapsed time: 46.53 s
The package azure-iot-sdk-c:x64-windows provides CMake targets:
find_package(azure_iot_sdks CONFIG REQUIRED)
# Note: 6 target(s) were omitted.
target_link_libraries(main PRIVATE serializer iothub_client prov_auth_client hsm_security_client)
Hello Jon,
Today once again I performed a git pull and then run the command as an administrator but again I faced same error
I think the reason is one of the following:
- run «cd ../../x64-windows-dbg» failed since ../../x64-windows-dbg doesn’t exist or we don’t have permission to access it,
- run «C:/Mukesh/IOTedge/vcpkg/downloads/tools/cmake-3.21.1-windows/cmake-3.21.1-windows-i386/bin/cmake.exe» failed since it doesn’t exist or we don’t have permission to access it.
Sadly, we can’t reproduce it locally, can you please confirm the above 2 items?
Thanks.
Hi Jack,
yes it looks like so as it says, System can not find path specified.
Please have a look on attached log
config-x64-windows-out.log
@mukeshhope Can you confirm Article 1 or Article 2 in my comment?
We don’t have enough information to solve this issue, unfortunately; if you have any more information to help us solve this, please reopen!
@MichalDulski That’s a different issue, please open a new issue and provide the logs.
I am trying to install shc on Ubuntu 18.04
wget http://www.datsi.fi.upm.es/~frosal/sources/shc-3.8.9b.tgz
tar xvfz shc-3.8.9.tgz
cd shc-3.8.9
make
But receive the following error:
cc -Wall shc.c -o shc
make: cc: Command not found
makefile:31: recipe for target 'shc' failed
make: *** [shc] Error 127
The makefile:
# Makefile
#
INSTALL_PATH = /usr/local
# For SCO
CFLAGS = -b elf -O -D_SVID
# For IRIX
CFLAGS = -xansi -fullwarn -O3 -g0
# For Solaris
CFLAGS = -fast -xO4 -s -v -Xa
# For HPUX
CFLAGS = -Wall -O -Ae
# For OSF1
CFLAGS = -w -verbose -fast -std1 -g0
# For GNU C compiler
CFLAGS = -Wall # -O6 -pedantic
#SHELL = /bin/sh
SHCFLAGS = -v -T # Add -T option to allow binary to be traceable
all: shc ask_for_test
shc: shc.c
$(CC) $(CFLAGS) $@.c -o $@
ask_for_test:
@echo '*** �Do you want to probe shc with a test script?'
@echo '*** Please try... make test'
test: make_the_test ask_for_strings
make_the_test: match.x
@echo '*** Running a compiled test script!'
@echo '*** It must show files with substring "sh" in your PATH...'
./match.x sh
match.x: shc match
@echo '*** Compiling script "match"'
CFLAGS="$(CFLAGS)" ./shc $(SHCFLAGS) -f match
ask_for_strings:
@echo '*** �Do you want to see strings in the generated binary?'
@echo '*** Please try... make strings'
strings: make_the_strings ask_for_expiration
make_the_strings: match.x
@echo '*** Running: "strings -n 5 'match.x'"'
@echo '*** It must show no sensible information...'
strings -n 5 match.x
ask_for_expiration:
@echo '*** �Do you want to probe expiration date?'
@echo '*** Please try... make expiration'
expiration: til_yesterday ask_for_install
til_yesterday: shc match
@echo '*** Compiling "match" to expired date'
CFLAGS="$(CFLAGS)" ./shc $(SHCFLAGS) -vv -e `date "+%d/%m/%Y"` -f match
@echo '*** Running a compiled test script!'
@echo '*** It must fail showing "./match.x: has expired!"'
./match.x
ask_for_install:
@echo '*** �Do you want to install shc?'
@echo '*** Please try... make install'
install: shc
@echo '*** Installing shc and shc.1 on '$(INSTALL_PATH)
@echo -n '*** �Do you want to continue? '; read ANS; case "$$ANS" in y|Y|yes|Yes|YES) ;; *) exit 1;; esac;
install -c -s shc $(INSTALL_PATH)/bin/
install -c -m 644 shc.1 $(INSTALL_PATH)/man/man1/
clean:
rm -f *.o *~ *.x.c
cleanall: clean
rm -f shc *.x
I have no idea how to fix this error. Can anyone help?
mature
3,7199 gold badges29 silver badges64 bronze badges
asked Nov 22, 2018 at 17:24
2
cc is an alias for the GNU C compiler (gcc). You can install it as follows:
sudo apt install gcc
If, for some reason, the gcc compiler is already installed, but the symbolic link /usr/bin/cc is missing, you can also do:
make CC=gcc
answered Nov 22, 2018 at 18:07
1
sudo apt install build-essential
This will install a C compiler (providing the cc command) as well as other tools that you may need for building software from source.
answered Nov 22, 2018 at 19:39
MarkMark
5724 silver badges13 bronze badges
Hello,
I’m trying to compile cmake version 3.16.2 via bootstrap with a custom OpenSSL (/path/to/openssl/lib):
cd cmake-3.16.2 &&
./bootstrap
--verbose
--parallel=$(nproc)
--prefix=/path/to/cmake
--
-DCMAKE_BUILD_TYPE=RELEASE
-DCMAKE_PREFIX_PATH="/path/to/openssl"
make -C cmake-3.16.2 -j $(nproc)
make -C cmake-3.16.2 -j $(nproc) installBut I have an issue during the installation step:
# ...
Install the project...
bin/cmake -P cmake_install.cmake
bin/cmake: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
Makefile:76: recipe for target 'install' failed
make: *** [install] Error 127Here is the output of ldd of bin/cmake:
ldd bin/cmake
linux-vdso.so.1 (0x00007ffc6e1dc000)
libssl.so.1.1 => not found
libcrypto.so.1.1 => not found
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f27de26a000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f27de062000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f27dde45000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f27ddb3a000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f27dd839000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f27dd623000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f27dd278000)
/lib64/ld-linux-x86-64.so.2 (0x00007f27de46e000)After taking a look at the CMakeLists.txt, I think that there is a missing check line 756 (OR CMAKE_USE_OPENSSL) to activate proper BUILD RPATH handling when using OpenSSL.
Do I miss or forget something ?
Thanks for your answer,
Regards,
- Форум русскоязычного сообщества Ubuntu »
- Поддержка »
- Настройка системы (Модераторы: Дмитрий Бо, www777) »
- make Error 127
- Печать
Страницы: [1] Вниз
Тема: make Error 127 (Прочитано 6818 раз)
0 Пользователей и 1 Гость просматривают эту тему.
w2e
Ubuntu 12.04
трей
—————————————————————————
000@1000:~/dd/dir320$ make kernel_menuconfigчто делать? кто нить знает?
make[1]: Entering directory `/home/000/dd/dir320/target/linux'
make[2]: Entering directory `/home/000/dd/dir320/target/linux/brcm47xx'
if [ -s "/home/000/dd/dir320/build_dir/linux-brcm47xx/linux-2.6.32.27/patches/series" ]; then (cd "/home/000/dd/dir320/build_dir/linux-brcm47xx/linux-2.6.32.27"; if quilt --quiltrc=- next >/dev/null 2>&1; then quilt --quiltrc=- push -a; else quilt --quiltrc=- top >/dev/null 2>&1; fi ); fi
make[2]: *** [/home/000/dd/dir320/build_dir/linux-brcm47xx/linux-2.6.32.27/.quilt_checked] Error 127
make[2]: Leaving directory `/home/000/dd/dir320/target/linux/brcm47xx'
make[1]: *** [menuconfig] Error 2
make[1]: Leaving directory `/home/000/dd/dir320/target/linux'
make: *** [kernel_menuconfig] Ошибка 2
Пользователь решил продолжить мысль 30 Июня 2012, 16:59:41:
проблема решена не хватала пакета quilt.
« Последнее редактирование: 30 Июня 2012, 16:59:41 от w2e »
victor00000
- Печать
Страницы: [1] Вверх
- Форум русскоязычного сообщества Ubuntu »
- Поддержка »
- Настройка системы (Модераторы: Дмитрий Бо, www777) »
- make Error 127
SMF 2.0.19 |
SMF © 2011, Simple Machines | Карта форума
Страница сгенерирована за 0.036 секунд. Запросов: 25.
Maybe you will get the following error when you try to work with a go operator-sdk project you cloned from GitHub.
Here we see that simply the bin directory with the needed controller-gen, kustomize and setup-envtest files, wasn’t created by operator-sdk commands.
This blog post does address that topic for a macOS operating system and is structured in following sections:
- Fast solution
- Reproduce the problem
- Fix the problem
1. Fast solution
In short words we need just to copy the
bindirectory from an existing operator-sdk project we have on our machine and past it into the cloned project and it will work for our cloned project.
But we will have problems, when we create new projects with that installation setup using brew install operator-sdk.
(even when this is my preferred way 😦 because I want to avoid FATA[0009] failed to create API: unable to run post-scaffold tasks of “base.go.kubebuilder.io/v3”: exit status 2)
I created a GitHub issue.
2. Reproduce the problem
We are using the currently available operator SDK version 19.1.0 which we installed using brew as described in the operator-sdk documentation.
Step 1: Clone a GO operator-sdk project from GitHub
git clone https://github.com/thomassuedbroecker/multi-tenancy-frontend-operator.git cd multi-tenancy-frontend-operator/frontendOperator
Step 2: Run make generate and get the error
- Example output:
As we will see, there are files and bin folder missing.
bin/controller-gen: No such file or directory
... go: added sigs.k8s.io/yaml v1.3.0 /multi-tenancy-frontend-operator/frontendOperator/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..." bash: /Users/thomassuedbroecker/Downloads/dev/verify/multi-tenancy-frontend-operator/frontendOperator/bin/controller-gen: No such file or directory make: *** [generate] Error 127
Step 3: Verify operator-sdk version
- Example output:
Ensure you have operator-sdk version: "v1.19.1" installed.
operator-sdk version: "v1.19.1", commit: "079d8852ce5b42aa5306a1e33f7ca725ec48d0e3", kubernetes version: "v1.23", go version: "go1.18.1", GOOS: "darwin", GOARCH: "amd64"
3. Fix the problem for now
We are using an Operator SDK version that worked before, in my case I used 18.0.0 successfully some time ago. As far as I remember, golang version 1.17.6 was related to operator-sdk 18.0.0 version.
Note: If you want to install an older Operator SDK version with brew, that won’t work as there is only one brew formulae, as I found out. I hope that the brew installation will be fixed in the future.
So, we will do the following sequence to fix the problem:
- Uninstall the
operator-sdkwe installed with brew - Install
operator-sdk 18.0.0using the binaries and install golang in versiongo 1.17.6 - Verify does the creation of a new operator project now include the
binand the related files
Step 1: Uninstall operator-sdk we installed with brew
Follow the steps outlined in one of my blog posts, but only for uninstalling. The current version of the operator-sdk in brew is 1.19.1.
YOUR_USER=YOUR_USER sudo go clean -cache brew uninstall operator-sdk brew uninstall go sudo rm -rf /usr/local/Cellar/go sudo rm -rf /usr/local/go sudo rm -rf /Users/$YOUR_USER/go
Step 2: Install operator-sdk 18.0.0 and goland 1.17.6 using the binaries¶
Here we follow the related operator-sdk documentation.
1. Create a folder for your downloads
mkdir operator-sdk cd operator-sdk
2. Set platform information
export ARCH=$(case $(uname -m) in x86_64) echo -n amd64 ;; aarch64) echo -n arm64 ;; *) echo -n $(uname -m) ;; esac)
export OS=$(uname | awk '{print tolower($0)}')
3. Download the binary for your platform
export OPERATOR_SDK_DL_URL=https://github.com/operator-framework/operator-sdk/releases/download/v1.18.0
curl -LO ${OPERATOR_SDK_DL_URL}/operator-sdk_${OS}_${ARCH}
4. Install the release binary in your PATH
chmod +x operator-sdk_${OS}_${ARCH} && sudo mv operator-sdk_${OS}_${ARCH} /usr/local/bin/operator-sdk
5. Download go 1.17.6
https://go.dev/dl/go1.17.6.darwin-amd64.pkg
6. Install go 1.17.6 using the downloaded file
7. Verify the installed operator-sdk and golang version
- Example output:
operator-sdk version: "v1.18.0", commit: "c9c61b6921b29d731e64cd3cc33d268215fb3b25", kubernetes version: "1.21", go version: "go1.17.7", GOOS: "darwin", GOARCH: "amd64"
3. Confirm that creating a new operator project now contains the bin and associated files
Let us just create an example project problemfix.
Step 1: Create a new empty folder outside the cloned project¶
cd .. mkdir fixproblem cd fixproblem
Step 2: Run operator-sdk init
operator-sdk init --domain myproblemfix.net --repo github.com/myproblemfix/myproblemfix
- Example output:
... go: downloading github.com/kr/text v0.2.0 go: downloading gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7 go: downloading github.com/cespare/xxhash v1.1.0 Next: define a resource with: $ operator-sdk create api
Step 2: Create an API¶
operator-sdk create api --group myproblemfix --version v1alpha1 --kind Myproblemfix --resource --controller
- Example output:
... Next: implement your new API and generate the manifests (e.g. CRDs,CRs) with: $ make manifests
Step 3: Run make generate
make generate make manifest make build
Step 3: Verify the bin folder and the needed files were created¶
fixproblem % tree . ├── Dockerfile ├── Makefile ├── PROJECT ├── api │ └── v1alpha1 │ ├── groupversion_info.go │ ├── myproblemfix_types.go │ └── zz_generated.deepcopy.go ├── bin │ ├── controller-gen │ ├── kustomize │ └── manager ├── config │ ├── crd │ │ ├── bases │ │ │ └── myproblemfix.myproblemfix.net_myproblemfixes.yaml │ │ ├── kustomization.yaml │ │ ├── kustomizeconfig.yaml │ │ └── patches │ │ ├── cainjection_in_myproblemfixes.yaml │ │ └── webhook_in_myproblemfixes.yaml │ ├── default │ │ ├── kustomization.yaml │ │ ├── manager_auth_proxy_patch.yaml │ │ └── manager_config_patch.yaml │ ├── manager │ │ ├── controller_manager_config.yaml │ │ ├── kustomization.yaml │ │ └── manager.yaml │ ├── manifests │ │ └── kustomization.yaml │ ├── prometheus │ │ ├── kustomization.yaml │ │ └── monitor.yaml │ ├── rbac │ │ ├── auth_proxy_client_clusterrole.yaml │ │ ├── auth_proxy_role.yaml │ │ ├── auth_proxy_role_binding.yaml │ │ ├── auth_proxy_service.yaml │ │ ├── kustomization.yaml │ │ ├── leader_election_role.yaml │ │ ├── leader_election_role_binding.yaml │ │ ├── myproblemfix_editor_role.yaml │ │ ├── myproblemfix_viewer_role.yaml │ │ ├── role.yaml │ │ ├── role_binding.yaml │ │ └── service_account.yaml │ ├── samples │ │ ├── kustomization.yaml │ │ └── myproblemfix_v1alpha1_myproblemfix.yaml │ └── scorecard │ ├── bases │ │ └── config.yaml │ ├── kustomization.yaml │ └── patches │ ├── basic.config.yaml │ └── olm.config.yaml ├── controllers │ ├── myproblemfix_controller.go │ └── suite_test.go ├── go.mod ├── go.sum ├── hack │ └── boilerplate.go.txt └── main.go
Summary¶
With that we ensure you have a working version. Now you can try to install different operator-sdk binaries if they work with the golang 1.17.6 related to operator development.
I hope this was useful to you and let’s see what’s next?
Greetings,
Thomas
#operatorsdk, #macos, #golang, #operators