I am trying to (cross-)compile Bazel 0.4.5 in the Yocto system. The target is an ARMv7 and the Linux distro is Poky.
I am getting this compilation error:
| � Building Bazel with Bazel.
| ................................
| ____Loading package: src
| ____Loading package: #bazel_tools//tools/cpp
| ____Loading package: #local_config_xcode//
| ERROR: in target '//external:cc_toolchain': no such package '#local_config_cc//': Traceback (most recent call last):
| File "/home/giuseppe/.cache/bazel/_bazel_giuseppe/32d64188b76850bf1edfd4141b911134/external/bazel_tools/tools/cpp/cc_configure.bzl", line 584
| _find_cc(repository_ctx)
| File "/home/giuseppe/.cache/bazel/_bazel_giuseppe/32d64188b76850bf1edfd4141b911134/external/bazel_tools/tools/cpp/cc_configure.bzl", line 383, in _find_cc
| repository_ctx.which(cc_name)
| Program argument of which() may not contains a / or a \ ('arm-poky-linux-gnueabi-gcc -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 --sysroot=/home/giuseppe/research/projects/zynq/yocto/build/tmp/sysroots/zc702-zynq7' given).
| ____Elapsed time: 3.851s
Do you have any suggestions?
Thank you
Maybe you can take a look at the meta-tensorflow layer. Link:
http://layers.openembedded.org/layerindex/branch/master/layer/meta-tensorflow/
Related
I'm using Cloud Code (extension for Visual Studio Code) and during the deploy, via UI, I'm trying to set the Environment Variables field like this:
KEY1:value1
KEY2:value2,value3
But I'm having this error:
Failed to deploy the app. Error: ERROR: (gcloud.run.deploy) argument --set-env-vars: Bad syntax for dict arg: [value3]. Please see gcloud topic flags-file or gcloud topic escaping for information on providing list or dictionary flag values with special characters. ,Usage: gcloud run deploy [[SERVICE] --namespace=NAMESPACE] [optional flags] optional flags may be --add-cloudsql-instances | --allow-unauthenticated | --args | --async | --binary-authorization | --breakglass | --clear-binary-authorization | --clear-cloudsql-instances | --clear-config-maps | --clear-env-vars | --clear-key | --clear-labels | --clear-post-key-revocation-action-type | --clear-secrets | --clear-vpc-connector | --cluster | --cluster-location | --command | --concurrency | --connectivity | --context | --cpu | --cpu-throttling | --env-vars-file | --help | --image | --ingress | --key | --kubeconfig | --labels | --max-instances | --memory | --min-instances | --namespace | --platform | --port | --post-key-revocation-action-type | --region | --remove-cloudsql-instances | --remove-config-maps | --remove-env-vars | --remove-labels | --remove-secrets | --revision-suffix | --service-account | --set-cloudsql-instances | --set-config-maps | --set-env-vars | --set-secrets | --source | --tag | --timeout | --no-traffic | --update-config-maps | --update-env-vars | --update-labels | --update-secrets | --use-http2 | --vpc-connector | --vpc-egress For detailed information on this command and its flags, run: gcloud run deploy --help
So it seems the comma needs to be escaped. How to do that via Cloud Code UI, please?
If you set the env-var like this: --set-env-var "A=B,C,D" to gcloud, it will treat the comma (,) character as another environment variable declaration and will try to split the value into multiple environment variables. This is explained here in detail.
However, to prevent splitting with commas, you need to specify a different custom delimiter that you’re sure won’t occur in your value string, such as ##:
--set-env-vars "^##^A=B,C,D"
You may also use a format like this as mentioned in the official docs:
--set-env-vars "^#^KEY1=value1,value2,value3#KEY2=..."
I don't think there is a work around here.
We are working to fix this through https://github.com/GoogleCloudPlatform/cloud-code-vscode/issues/560.
For now I could solve that by making "Environment Variables" UI field empty and using a Dockerfile to set the variables, where this syntax works:
ENV KEY1='value1'
ENV KEY2='value2,value3'
I'm using Yocto Project 2.4 and i.MX6 Quad sabreSD platform.I build Yocto Project on my Ubuntu 16.04 computer.
I want to have qt5.9 library in my rootFS so I build my image with below command.
bitbake fsl-image-qt5
After that, I tried to remove wayland cause I want to use eglfs to play my application.
So I add below line into local.conf.
DISTRO_FEATURES_remove = "wayland"
Then try to bitbake fsl-image-qt5 again but this time I got below error.
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: qtxmlpatterns-5.9.4+gitAUTOINC+757fc81657-r0 do_compile: oe_runmake failed
ERROR: qtxmlpatterns-5.9.4+gitAUTOINC+757fc81657-r0 do_compile: Function failed: do_compile (log file is located at /mnt/raid/forenex/yocto2.4/build- wayland-q/tmp/work/cortexa9hf-neon-poky-linux- gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/temp/log.do_compile.12439)
ERROR: Logfile of failure stored in: /mnt/raid/forenex/yocto2.4/build- wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/temp/log.do_compile.12439
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 MAKEFLAGS=-j 4 OE_QMAKE_COMPILER=arm-poky-linux-gnueabi- gcc -march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 -- sysroot=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon- poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot OE_QMAKE_CC=arm-poky-linux-gnueabi-gcc -march=armv7-a -mfpu=neon -mfloat- abi=hard -mcpu=cortex-a9 --sysroot=/mnt/raid/forenex/yocto2.4/build-wayland- q/tmp/work/cortexa9hf-neon-poky-linux- gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot OE_QMAKE_CXX=arm-poky-linux-gnueabi-g++ -march=armv7-a -mfpu=neon -mfloat- abi=hard -mcpu=cortex-a9 --sysroot=/mnt/raid/forenex/yocto2.4/build-wayland- q/tmp/work/cortexa9hf-neon-poky-linux- gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot OE_QMAKE_CFLAGS= -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix- map=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky- linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0=/usr/src/debug/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0 -fdebug-prefix-map=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native= -fdebug-prefix-map=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot= OE_QMAKE_CXXFLAGS= -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0=/usr/src/debug/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0 -fdebug-prefix-map=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native= -fdebug-prefix-map=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot= -fvisibility-inlines-hidden OE_QMAKE_LINK=arm-poky-linux-gnueabi-g++ -march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 --sysroot=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot OE_QMAKE_LDFLAGS=-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed OE_QMAKE_AR=arm-poky-linux-gnueabi-ar OE_QMAKE_STRIP=echo OE_QMAKE_WAYLAND_SCANNER=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/wayland-scanner OE_QMAKE_INCDIR_QT=/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot//usr/include/qt5
| cd src/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland- q/tmp/work/cortexa9hf-neon-poky-linux- gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/src/src.pro ) && make - f Makefile
| make[1]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/src'
| cd xmlpatterns/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/src/xmlpatterns/xmlpatterns.pro ) && make -f Makefile
| make[2]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/src/xmlpatterns'
| make[2]: Nothing to be done for `first'.
| make[2]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/src/xmlpatterns'
| make[1]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/src'
| cd tools/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tools/tools.pro ) && make -f Makefile
| cd examples/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/examples/examples.pro ) && make -f Makefile
| cd tests/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/tests.pro ) && make -f Makefile
| make[1]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests'
| cd auto/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/auto.pro ) && make -f Makefile
| make[1]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples'
| cd xmlpatterns/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/examples/xmlpatterns/xmlpatterns.pro ) && make -f Makefile
| make[1]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tools'
| cd xmlpatterns/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tools/xmlpatterns/xmlpatterns.pro ) && make -f Makefile
| cd xmlpatternsvalidator/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tools/xmlpatternsvalidator/xmlpatternsvalidator.pro ) && make -f Makefile
| make[2]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland- q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples/xmlpatterns'
| cd xquery/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/examples/xmlpatterns/xquery/xquery.pro ) && make -f Makefile
| cd recipes/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/examples/xmlpatterns/recipes/recipes.pro ) && make -f Makefile
| cd filetree/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/examples/xmlpatterns/filetree/filetree.pro ) && make -f Makefile
| cd schema/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/examples/xmlpatterns/schema/schema.pro ) && make -f Makefile
| make[2]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto'
| cd checkxmlfiles/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build- wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/checkxmlfiles/checkxmlfiles.pro ) && make -f Makefile
| cd cmake/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/cmake/cmake.pro ) && make -f Makefile
| cd patternistexamplefiletree/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/patternistexamplefiletree/patternistexamplefiletree.pro ) && make -f Makefile
| cd patternistexamples/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/patternistexamples/patternistexamples.pro ) && make -f Makefile
| make[3]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples/xmlpatterns/xquery'
| make[3]: Nothing to be done for `first'.
| make[3]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples/xmlpatterns/xquery'
| make[2]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tools/xmlpatterns'
| make[2]: Nothing to be done for `first'.
| make[2]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tools/xmlpatterns'
| make[3]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/cmake'
| make[3]: Nothing to be done for `first'.
| make[3]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland- q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/cmake'
| cd patternistheaders/ && ( test -e Makefile || /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/patternistheaders/patternistheaders.pro ) && make -f Makefile
| make[2]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tools/xmlpatternsvalidator'
| make[2]: Nothing to be done for `first'.
| make[2]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland- q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tools/xmlpatternsvalidator'
| make[1]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tools'
| make[3]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/patternistexamplefiletree'
| compiling /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/patternistexamplefiletree/tst_patternistexamplefiletree.cpp
| make[3]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples/xmlpatterns/recipes'
| make[3]: Nothing to be done for `first'.
| make[3]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657- r0/build/examples/xmlpatterns/recipes'
| make[3]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples/xmlpatterns/schema'
| make[3]: Nothing to be done for `first'.
| make[3]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657- r0/build/examples/xmlpatterns/schema'
| make[3]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/checkxmlfiles'
| compiling /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/checkxmlfiles/tst_checkxmlfiles.cpp
| make[3]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples/xmlpatterns/filetree'
| make[3]: Nothing to be done for `first'.
| make[3]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples/xmlpatterns/filetree'
| make[2]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples/xmlpatterns'
| make[1]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/examples'
| make[3]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/patternistheaders'
| compiling /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/patternistheaders/tst_patternistheaders.cpp
| make[3]: Entering directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/patternistexamples'
| compiling /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/patternistexamples/tst_patternistexamples.cpp
| /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/patternistexamplefiletree/tst_patternistexamplefiletree.cpp:54:10: fatal error: tst_patternistexamplefiletree.moc: No such file or directory
| #include "tst_patternistexamplefiletree.moc"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| compilation terminated.
| make[3]: *** [.obj/tst_patternistexamplefiletree.o] Error 1
| make[3]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/patternistexamplefiletree'
| make[2]: *** [sub-patternistexamplefiletree-make_first] Error 2
| make[2]: *** Waiting for unfinished jobs....
| /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/checkxmlfiles/tst_checkxmlfiles.cpp:96:10: fatal error: tst_checkxmlfiles.moc: No such file or directory
| #include "tst_checkxmlfiles.moc"
| ^~~~~~~~~~~~~~~~~~~~~~~
| compilation terminated.
| make[3]: *** [.obj/tst_checkxmlfiles.o] Error 1
| make[3]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/checkxmlfiles'
| make[2]: *** [sub-checkxmlfiles-make_first] Error 2
| /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/patternistexamples/tst_patternistexamples.cpp:346:10: fatal error: tst_patternistexamples.moc: No such file or directory
| #include "tst_patternistexamples.moc"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
| compilation terminated.
| make[3]: *** [.obj/tst_patternistexamples.o] Error 1
| make[3]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/patternistexamples'
| make[2]: *** [sub-patternistexamples-make_first] Error 2
| /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/git/tests/auto/patternistheaders/tst_patternistheaders.cpp:124:10: fatal error: tst_patternistheaders.moc: No such file or directory
| #include "tst_patternistheaders.moc"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
| compilation terminated.
| make[3]: *** [.obj/tst_patternistheaders.o] Error 1
| make[3]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto/patternistheaders'
| make[2]: *** [sub-patternistheaders-make_first] Error 2
| make[2]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests/auto'
| make[1]: *** [sub-auto-make_first] Error 2
| make[1]: Leaving directory `/mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/build/tests'
| make: *** [sub-tests-make_first] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /mnt/raid/forenex/yocto2.4/build-wayland-q/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtxmlpatterns/5.9.4+gitAUTOINC+757fc81657-r0/temp/log.do_compile.12439)
ERROR: Task (/mnt/raid/forenex/yocto2.4/sources/meta-qt5/recipes- qt/qt5/qtxmlpatterns_git.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5855 tasks of which 5853 didn't need to be rerun and 1 failed.
All the same steps that I did in Yocto Project 2.0 could work but Yocto Project 2.4 couldn't.
How to fix this error?
If I wish to use -platform eglfs to run my application, which way is the best to achieve it?
You should to add eglfs support to distro.
DISTRO_FEATURES_append = "eglfs"
I reinstall Yocto project and it works.
I think there is something got wrong when I repo the source code.
You should remove tmp/ directory from your build directory and rebuild the whole thing again after every change in DISTRO_FEATURES
I recently started James Molly's Kernel Devolpment Tutorials and has come as far as implementing the GDT and IDT .
The problem arises when I link together the high level functions with their low level assembly counterparts .
You can Find the Code here
Source on Github
Here is the Directory Structure
.
|-- arch
|-- boot
| |-- boot.s
| |-- buildboot.sh
| |-- gdt.s
| |-- idt.s
| `-- interrupt.s
|-- build
| |-- boot.s.o
| |-- gdt.o
| |-- gdt.s.o
| |-- idt.o
| |-- idt.s.o
| |-- interrupt.s.o
| |-- io.o
| |-- isr.o
| |-- main.o
| |-- memory.o
| |-- monitor.o
| `-- stdlib.o
|-- doc
| `-- Bug_Log.md
|-- include
| |-- gdt.cc
| |-- gdt.h
| |-- gdt.o
| |-- idt.cc
| |-- idt.h
| |-- idt.o
| |-- io.cc
| |-- io.h
| |-- io.o
| |-- isr.cc
| |-- isr.h
| |-- isr.o
| |-- memory.cc
| |-- memory.h
| |-- memory.o
| |-- monitor.cc
| |-- monitor.h
| |-- monitor.o
| |-- SConstruct
| |-- stdlib.cc
| |-- stdlib.h
| |-- stdlib.o
| `-- system.h
|-- JOSMake.sh
|-- link.ld
|-- main.cc
`-- ReadMe.md
Here is the Bash Scripts
JOSmake.sh
#
# Build File for JOS
#
# To Build
# bash build.sh
# To Run
# bash run.sh
# ----------------------------------------------------------------------------------------------
# JOS uses assembly to build the bootsector
# Compile the boot Sectors in boot
echo "==============================================="
echo "-------- Building Boot Sectors ----------------"
cd boot
# Run the Make Script inside the boot directory
bash buildboot.sh
cd ..
echo "==============================================="
# ----------------------------------------------------------------------------------------------
# ----------------------------------------------------------------------------------------------
# Compile the C++ Sources into Respective Objects
# Compile main.cc
echo "==============================================="
echo "--------- Compiling C++ Sources --------------"
g++ -c -nostdlib -nostdinc -fno-builtin -fno-stack-protector -ffreestanding -m32 -o main.o main.cc
mv main.o build
# Run scons to build the Entire Lbrary of C++ Files
cd include
rm *.o
scons
# Move all Object Files into Build Directory
cp *.o ../build
cd ..
echo "==============================================="
# ----------------------------------------------------------------------------------------------
# ----------------------------------------------------------------------------------------------
## When Everything is Finished Link together the Objects into a Kernel File
echo "==============================================="
echo "--------- Linking ----------------"
cd build
# require ld , link.ld
ld -T '../link.ld' -m elf_i386 -o kernel.jos *.o
# Clean Up After Build
#rm *.o
echo "==============================================="
# ----------------------------------------------------------------------------------------------
# ----------------------------------------------------------------------------------------------
## When Everything is Finished Run the Kernel
qemu-system-i386 -kernel kernel.jos
# -----------------------------------------------------------------------------------------
Here is the buildboot.sh
# Builds the Boot files for JOS
# require 'nasm'
# Add all the Assembly Files Here
nasm -f elf -o boot.s.o boot.s
nasm -f elf -o gdt.s.o gdt.s
nasm -f elf -o idt.s.o idt.s
nasm -f elf -o interrupt.s.o interrupt.s
# Move the Entire Object Files into the Build Directory
mv *.o ../build
And here is the Terminal Output when I run the Script
===============================================
-------- Building Boot Sectors ----------------
===============================================
===============================================
--------- Compiling C++ Sources --------------
In file included from include/system.h:22:0,
from main.cc:6:
include/idt.h:34:13: warning: ‘void init_idt()’ used but never defined
static void init_idt();
^
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
g++ -o gdt.o -c -nostdlib -nostdinc -fno-builtin -fno-stack-protector -ffreestanding -m32 gdt.cc
g++ -o idt.o -c -nostdlib -nostdinc -fno-builtin -fno-stack-protector -ffreestanding -m32 idt.cc
g++ -o io.o -c -nostdlib -nostdinc -fno-builtin -fno-stack-protector -ffreestanding -m32 io.cc
g++ -o isr.o -c -nostdlib -nostdinc -fno-builtin -fno-stack-protector -ffreestanding -m32 isr.cc
g++ -o memory.o -c -nostdlib -nostdinc -fno-builtin -fno-stack-protector -ffreestanding -m32 memory.cc
g++ -o monitor.o -c -nostdlib -nostdinc -fno-builtin -fno-stack-protector -ffreestanding -m32 monitor.cc
g++ -o stdlib.o -c -nostdlib -nostdinc -fno-builtin -fno-stack-protector -ffreestanding -m32 stdlib.cc
scons: done building targets.
===============================================
===============================================
--------- Linking ----------------
gdt.o: In function `init_gdt()':
gdt.cc:(.text+0xb0): undefined reference to `gdt_flush(unsigned int)'
idt.o: In function `init_idt()':
idt.cc:(.text+0x3a): undefined reference to `isr0()'
idt.cc:(.text+0x51): undefined reference to `isr1()'
idt.cc:(.text+0x68): undefined reference to `isr2()'
idt.cc:(.text+0x7f): undefined reference to `isr3()'
idt.cc:(.text+0x96): undefined reference to `isr4()'
idt.cc:(.text+0xad): undefined reference to `isr5()'
idt.cc:(.text+0xc4): undefined reference to `isr6()'
idt.cc:(.text+0xdb): undefined reference to `isr7()'
idt.cc:(.text+0xf2): undefined reference to `isr8()'
idt.cc:(.text+0x109): undefined reference to `isr9()'
idt.cc:(.text+0x120): undefined reference to `isr10()'
idt.cc:(.text+0x137): undefined reference to `isr11()'
idt.cc:(.text+0x14e): undefined reference to `isr12()'
idt.cc:(.text+0x165): undefined reference to `isr13()'
idt.cc:(.text+0x17c): undefined reference to `isr14()'
idt.cc:(.text+0x193): undefined reference to `isr15()'
idt.cc:(.text+0x1aa): undefined reference to `isr16()'
idt.cc:(.text+0x1c1): undefined reference to `isr17()'
idt.cc:(.text+0x1d8): undefined reference to `isr18()'
idt.cc:(.text+0x1ef): undefined reference to `isr19()'
idt.cc:(.text+0x206): undefined reference to `isr20()'
idt.cc:(.text+0x21d): undefined reference to `isr21()'
idt.cc:(.text+0x234): undefined reference to `isr22()'
idt.cc:(.text+0x24b): undefined reference to `isr23()'
idt.cc:(.text+0x262): undefined reference to `isr24()'
idt.cc:(.text+0x279): undefined reference to `isr25()'
idt.cc:(.text+0x290): undefined reference to `isr26()'
idt.cc:(.text+0x2a7): undefined reference to `isr27()'
idt.cc:(.text+0x2be): undefined reference to `isr28()'
idt.cc:(.text+0x2d5): undefined reference to `isr29()'
idt.cc:(.text+0x2ec): undefined reference to `isr30()'
idt.cc:(.text+0x303): undefined reference to `isr31()'
idt.cc:(.text+0x323): undefined reference to `idt_flush(unsigned int)'
interrupt.s.o: In function `isr_common_stub':
interrupt.s:(.text+0x10d): undefined reference to `isr_handler'
main.o: In function `main':
main.cc:(.text+0x17): undefined reference to `init_idt()'
===============================================
qemu: could not load kernel 'kernel.jos': No such file or directory
Could anyone Point out what Iam Doing Wrong
This looks like a name mangling issue.
The guide you're following is written in C, and your IDT code would probably work if it were compiled using GCC instead of G++. However if you choose to use C++ you need to make some changes to allow referring to assembler functions from C++ and vice versa.
Function names in C and assembler map directly to symbol names, but C++ by default adds some extra text to the symbol name to include information about classes, namespaces, overloading etc.
To make sure that your C++ code can refer to the assembler functions using the correct symbol name, you must tell the compiler to use C linkage for those functions.
Look for places in your C++ header files where you declare functions that are implemented in assembler, for example: the isrN() functions in idt.hh
.
Wrap those declarations in a C linkage block like so:
extern "C" {
extern int isr0();
extern int isr1();
// ... and so on for all your ASM functions.
}
And do the same for C++ functions that should be callable from assembler.
I am very familiar with
rpm -qa --last
and have found it to be very handy on certain occasions. However on this occasion I accidentally got a bit overzealous and installed a large yum group.
yum groupinstall "Development tools"
Is there an easy way to uninstall everything I just installed? Seems to me there should be some way to combine rpm query and rpm erase. i.e. piping the output from a query command into the remove command.
Update: based on user #rickhg12hs feedback
It was pointed out that I can see the transaction id with yum history which I did not know about. Here is what that looks like:
$ yum history
Loaded plugins: fastestmirror, security
ID | Login user | Date and time | Action(s) | Altered
----------------------------------------------------------------------------
69 | <jds> | 2015-05-11 01:31 | Install | 1
68 | <jds> | 2015-05-11 01:31 | Install | 1
67 | <jds> | 2015-05-11 01:10 | I, U | 210
66 | <jds> | 2015-05-05 12:41 | Install | 1
65 | <jds> | 2015-04-30 17:57 | Install | 2
64 | <ansible> | 2015-04-30 10:11 | Install | 1
63 | <ansible> | 2015-04-30 10:11 | Install | 1
62 | <ansible> | 2015-04-30 10:11 | Install | 1 EE
61 | <ansible> | 2015-04-30 10:11 | Install | 1
60 | <ansible> | 2015-04-30 10:11 | Install | 1
59 | <ansible> | 2015-04-30 09:58 | Install | 19 P<
58 | <ansible> | 2015-04-29 18:28 | Install | 1 >
57 | <ansible> | 2015-04-29 18:28 | Install | 1
56 | <ansible> | 2015-04-29 18:28 | Install | 9
55 | <ansible> | 2015-04-29 18:28 | Install | 3
54 | <ansible> | 2015-04-29 18:28 | Install | 1
53 | <ansible> | 2015-04-29 18:27 | I, U | 5
52 | <ansible> | 2015-04-29 18:27 | I, U | 4
51 | <ansible> | 2015-04-29 18:27 | Install | 1
50 | <ansible> | 2015-04-29 18:27 | Install | 1
and tada: There it is, a transaction id.
I want to uninstall from transaction id 67. So now that I am a bit wiser I have a new question.
So how can I use the yum or rpm command to uninstall a transaction?
Note: it was also pointed out to me that I can do a
$ yum history info 67 |less
Loaded plugins: fastestmirror, security
Transaction ID : 67
Begin time : Mon May 11 01:10:09 2015
Begin rpmdb : 1012:bb05598315dcb21812b038a356fa06333d277cde
End time : 01:13:25 2015 (196 seconds)
End rpmdb : 1174:cb7855e82c7bff545319c38b01a72a48f3ada1ab
User : <jds>
Return-Code : Success
Command Line : groupinstall Additional Development
Transaction performed with:
Installed rpm-4.8.0-38.el6_6.x86_64 #updates
Installed yum-3.2.29-60.el6.centos.noarch #anaconda-CentOS-201410241409.x86_64/6.6
Installed yum-plugin-fastestmirror-1.1.30-30.el6.noarch #anaconda-CentOS-201410241409.x86_64/6.6
Packages Altered:
Dep-Install GConf2-2.28.0-6.el6.x86_64 #base
Install GConf2-devel-2.28.0-6.el6.x86_64 #base
Dep-Install ORBit2-2.14.17-5.el6.x86_64 #base
... snip ...
I think this could prove quite helpful under certain circumstances.
If you uninstall packages, then you run the risk of removing things that were already there, but happened to be upgraded. As a rule, you should use yum (or equivalent) for managing packages, which allows you to downgrade a package. This would remove new packages, and downgrade existing ones. See for example How to safely downgrade or remove glibc with yum and rpm
Selecting the names of packages to downgrade can be done using the output of rpm -qa, formatted to allow simple selection of the given date. For instance (see CentOS: List the installed RPMs by date of installation/update?), you can list packages in the reverse-order of their install date using
rpm -qa --last
As a more elaborate approach, you can use the --queryformat option with the :date option to format the date exactly as you want (it uses strftime).
In either case, you can make a script to extract the package names from the output of rpm, and use those packages with yum (or even rpm) to manipulate as needed.
When doing a downgrade, there is one odd thing to keep in mind: that revises the install-date for packages to be the current date rather than a complete undo, by using the previous date.
All packages installed in a single transaction have
an identical RPMTAG_INSTALLTID tag value.
Use
rpm -qa --qf '[%{name}\t%{installtid:date}\n]'
to find all packages that were installed as part of the yum group install.
Yum has provision for you to undo your command i.e. yum history undo #blah
In your case, to remove all packages you installed today you can run :
yum history undo 69
yum history undo 68
yum history undo 67
hello all when i run the command to generate Localizable.string file from my terminal it says me bad entry in to the classes file the file gets generated but it has no entry in it infact it should have entry in it. Here is what i am running in my terminal but somehow it is not happening please guide me need to solve this
Last login: Mon Jun 7 18:02:09 on ttys000
comp10:~ admin$ cd ..
comp10:Users admin$ cd ..
comp10:/ admin$ cd /Users/admin/Desktop/localisationwithcode
comp10:localisationwithcode admin$ sudo
usage: sudo -K | -L | -V | -h | -k | -l | -v
usage: sudo [-HPSb] [-p prompt] [-u username|#uid]
{ -e file [...] | -i | -s | <command> }
comp10:localisationwithcode admin$ genstrings Classes/*.m
Bad entry in file Classes/localisationwithcodeViewController.m (line = 35): Argument is not a literal string.
Bad entry in file Classes/localisationwithcodeViewController.m (line = 36): Argument is not a literal string.
Bad entry in file Classes/localisationwithcodeViewController.m (line = 37): Argument is not a literal string.
Bad entry in file Classes/localisationwithcodeViewController.m (line = 38): Argument is not a literal string.
2010-06-07 18:04:45.047 genstrings[3851:10b] _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
comp10:localisationwithcode admin$
You have an alternative way to solve Issue:
1.Right click on your Project Name From Groups and Files
2.From there Click on Resources Tag(Mac OS)
3.On That you will get tag like String File Clink on that File and Name as per your Requirement...