dyld:warning,未知的环境变量:DYLD_LIBRARY_PATH_64位 [英] dyld: warning, unknown environment variable: DYLD_LIBRARY_PATH_64-bit

查看:1598
本文介绍了dyld:warning,未知的环境变量:DYLD_LIBRARY_PATH_64位的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用Mac OS X开发工具捆绑的属性列表编辑器将环境变量DYLD_LIBRARY_PATH_64位设置为文件〜/ .MacOSX / environment.plist中的值path / to / dylib。我保存了这个文件并注销了。

I used the bundled Property List Editor of Mac OS X Developer Tools to set an environment variable DYLD_LIBRARY_PATH_64-bit to the value path/to/dylib in the file ~/.MacOSX/environment.plist. I saved this file and logged out.

登录后,控制台显示dyld:warning,unknown environment variable:DYLD_LIBRARY_PATH_64-bit的多条消息。我从Property List Editor中删除了来自environment.plist的条目,保存文件并注销。

Upon logging back in, the console displayed multiple messages of "dyld: warning, unknown environment variable: DYLD_LIBRARY_PATH_64-bit." I removed the entry from environment.plist with the Property List Editor, saved the file and logged out.

我已登录,并且警告消息仍然存在。 dyld手册页显示一个与我的环境变量类似的常量列表,因为它们都以DYLD_开头。源文件dyld.cpp在长行的DYLD常量之后显示一个else,其代码打印出相同的警告消息。也许我飞过太靠近环境变量命名的太阳。我以为我们是免费的!

I logged back in, and the warning message persists. The dyld man page displays a list of constants which appear similar to my wayward environmental variable, as they all start with "DYLD_." A source file, dyld.cpp, shows an else after a long line of DYLD constants, with code to print the very same warning message. Maybe I flew too close to the sun of environmental variable naming. I thought we were free!

我尝试过update_dyld_shared_cache无效。也许我错过了一些重要的标志?

I tried update_dyld_shared_cache to no avail. Perhaps I am missing some important flags?

我在/etc/launchd.conf中添加了setenv DYLD_LIBRARY_PATH_64-bit path / to / dylib,试图添加一个显然格式错误)环境变量到我的路径,希望如果它出现,我可以删除它 - 没有成功。

I added "setenv DYLD_LIBRARY_PATH_64-bit path/to/dylib" to /etc/launchd.conf in an attempt to add a (apparently malformed) environmental variable to my paths, hoping that if it showed up, I could delete it - without success.

从命令行,导出不显示DYLD_LIBRARY_PATH_64位。以下是一些示例输出:

From the command-line, export does not show DYLD_LIBRARY_PATH_64-bit. Here's some sample output:

$ unset $DYLD_LIBRARY_PATH_64-bit 
-bash: unset: -b: invalid option

$ echo $DYLD_LIBRARY_PATH_64-bit
-bit

$ unset DYLD_LIBRARY_PATH_64-bit
-bash: unset: `DYLD_LIBRARY_PATH_64-bit': not a valid identifier

故事的道德是永远不要使用属性列表编辑器,至少与动态库路径。好吧,这个故事的道德决不会在环境变量名字结束时使用破折号,因为他们看起来像标志。

The moral of the story is to never use Property List Editor, at least with dynamic library paths. Well no - the moral of the story is never use the dash at the end of environmental variable names, since they look like flags.

那么说,你会有什么建议来摆脱这个伪装的环境变量,并清理我的控制台重复的dyld警告?

With that said, do ya'll have any recommendations for getting rid of this masquerading environmental variable, and of cleaning my console of repeated dyld warnings?

谢谢!

推荐答案

这是解决隐形环境的一种方法属性列表编辑器无意中设置的变量:重新格式化机器。打扫。清洁它用火。

Here's one way to solve an invisible environment variable inadvertently set by the Property List Editor: re-format the machine. Clean it. Clean it with fire.

为我们所有人,特别是我自己的一个令人激动的教训。在使用属性列表编辑器时,不要使用环境变量中的破折号,以免在您的机器的所有日子中使用dyld:警告消息。对于主板而言,因为她的CPU是生产率不高的,而是将其缩减为将文件打印到文件2(标准错误)。

A sobering lesson for all of us, and especially myself. Use not the dash in your environment variables when using Property List Editor, lest you be riddled with dyld: warning messages for all the days of your machine. Woe to the motherboard, for her CPU is barren of productivity, and instead she is reduced to printing messages to file 2 (standard error).

没有认真的:属性列表编辑器将让您指定Bash永远不会让您摆脱的假冒环境变量。在用户必须知道他在做什么的意义上,Mac OS X就像UNIX一样。

No seriously: Property List Editor will let you specify bogus environmental variables that Bash would never let you get away with. In the sense of "the user must know what he's doing," Mac OS X becomes UNIX-like.

这篇关于dyld:warning,未知的环境变量:DYLD_LIBRARY_PATH_64位的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆