提醒”libc.so.6: version `GLIBC_2.14′ not found”系统的glibc版本太低

参考:
(1)http://www.cnblogs.com/gw811/p/3676856.html
(2)http://m.oschina.net/blog/262275

【linux】提示”libc.so.6: version `GLIBC_2.14′ not found”,系统的glibc版本太低

0.以下在系统CentOS 6.3 x86_64上操作

1.试图运行程序,提示”libc.so.6: version `GLIBC_2.14′ not found”,原因是系统的glibc版本太低,软件编译时使用了较高版本的glibc引起的:

  1. [ghui@StuOS bin]$ pwd
  2. /var/VMdisks/cross/mingw32/bin
  3. [ghui@StuOS bin]$ ls
  4. lrelease     QtCore4.dll         QtNetwork4.dll      QtSql4.dll     QtXml4.dll
  5. moc          QtDeclarative4.dll  QtOpenGL4.dll       QtSvg4.dll     rcc
  6. phonon4.dll  QtGui4.dll          QtScript4.dll       QtTest4.dll    uic
  7. qmake        QtMultimedia4.dll   QtScriptTools4.dll  QtWebKit4.dll
  8. [ghui@StuOS bin]$ ./qmake
  9. ./qmake: /lib64/libc.so.6: version `GLIBC_2.14′ not found (required by ./qmake)

 

2.查看系统glibc支持的版本:

  1. [ghui@StuOS bin]$ strings /lib64/libc.so.6 |grep GLIBC_
  2. GLIBC_2.2.5
  3. GLIBC_2.2.6
  4. GLIBC_2.3
  5. GLIBC_2.3.2
  6. GLIBC_2.3.3
  7. GLIBC_2.3.4
  8. GLIBC_2.4
  9. GLIBC_2.5
  10. GLIBC_2.6
  11. GLIBC_2.7
  12. GLIBC_2.8
  13. GLIBC_2.9
  14. GLIBC_2.10
  15. GLIBC_2.11
  16. GLIBC_2.12
  17. GLIBC_PRIVATE
  1. [ghui@StuOS bin]$ rpm -qa |grep glibc
  2. glibc-static-2.12-1.80.el6_3.6.x86_64
  3. glibc-headers-2.12-1.80.el6_3.6.x86_64
  4. glibc-common-2.12-1.80.el6_3.6.x86_64
  5. glibc-devel-2.12-1.80.el6_3.6.x86_64
  6. glibc-static-2.12-1.80.el6_3.6.i686
  7. glibc-devel-2.12-1.80.el6_3.6.i686
  8. glibc-2.12-1.80.el6_3.6.i686
  9. glibc-2.12-1.80.el6_3.6.x86_64

 

3.可以看到最高只支持2.12版本,所以考虑编译解决这个问题:

a. 到http://www.gnu.org/software/libc/下载最新版本,我这里下载了glibc-2.14.tar.xz 这个版本,解压到任意目录准备编译

b.这里解压到/var/VMdisks/glibc-2.14/

  1. [ghui@StuOS bin]$ cd /var/VMdisks/glibc-2.14/
  2. [ghui@StuOS glibc-2.14]$ pwd
  3. /var/VMdisks/glibc-2.14
  4. [ghui@StuOS glibc-2.14]$ ls
  5. abilist            config.h.in           intl           README.libm
  6. abi-tags           config.log            io             resolv
  7. aclocal.m4         config.make.in        libc-abis      resource
  8. aout               configure             libidn         rt
  9. argp               configure.in          libio          Rules
  10. assert             conform               LICENSES       scripts
  11. autom4te.cache     CONFORMANCE           locale         setjmp
  12. bits               COPYING               localedata     shadow
  13. BUGS               COPYING.LIB           login          shlib-versions
  14. build              cppflags-iterator.mk  mach           signal
  15. CANCEL-FCT-WAIVE   crypt                 Makeconfig     socket
  16. CANCEL-FILE-WAIVE  csu                   Makefile       soft-fp
  17. catgets            ctype                 Makefile.in    stdio-common
  18. ChangeLog          debug                 Makerules      stdlib
  19. ChangeLog.1        dirent                malloc         streams
  20. ChangeLog.10       dlfcn                 manual         string
  21. ChangeLog.11       elf                   math           sunrpc
  22. ChangeLog.12       extra-lib.mk          misc           sysdeps
  23. ChangeLog.13       extra-modules.mk      NAMESPACE      sysvipc
  24. ChangeLog.14       FAQ                   NEWS           termios
  25. ChangeLog.15       FAQ.in                nis            test-skeleton.c
  26. ChangeLog.16       gmon                  NOTES          time
  27. ChangeLog.17       gnulib                nptl           timezone
  28. ChangeLog.2        grp                   nptl_db        tls.make.c
  29. ChangeLog.3        gshadow               nscd           version.h
  30. ChangeLog.4        hesiod                nss            Versions.def
  31. ChangeLog.5        hurd                  o-iterator.mk  wcsmbs
  32. ChangeLog.6        iconv                 po             wctype
  33. ChangeLog.7        iconvdata             posix          WUR-REPORT
  34. ChangeLog.8        include               PROJECTS
  35. ChangeLog.9        inet                  pwd
  36. conf               INSTALL               README

c.在glibc源码目录建立构建目录,并cd进入构建目录

  1. [ghui@StuOS glibc-2.14]$ mkdir build
  1. [ghui@StuOS glibc-2.14]$ cd build

d.运行configure配置,make && sudo  make install

  1. [ghui@StuOS build]$ ../configure –prefix=/opt/glibc-2.14
  2. [ghui@StuOS build]$ make -j4
  3. [ghui@StuOS build]$ sudo make install
  4. [sudo] password for ghui:

4.临时修改环境变量

  1. [ghui@StuOS bin]$ export LD_LIBRARY_PATH=/opt/glibc-2.14/lib:$LD_LIBRARY_PATH
  1. [ghui@StuOS glibc-2.14]$ cd /var/VMdisks/cross/mingw32/bin/

 

  1. [ghui@StuOS bin]$ ./qmake
  2. Usage: ./qmake [mode] [options] [files]
  3. QMake has two modes, one mode for generating project files based on
  4. some heuristics, and the other for generating makefiles. Normally you
  5. shouldn’t need to specify a mode, as makefile generation is the default
  6. mode for qmake, but you may use this to test qmake on an existing project

 

此时运行正常,问题解决。

Git Permissions

Refer to https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/permissions/permissions.md

Permissions

Users have different abilities depending on the access level they have in a particular group or project.

If a user is both in a project group and in the project itself, the highest permission level is used.

If a user is a GitLab administrator they receive all permissions.

On public and internal projects the Guest role is not enforced. All users will be able to create issues, leave comments, and pull or download the project code.

To add or import a user, you can follow the project users and members documentation.

Project

Action Guest Reporter Developer Master Owner
Create new issue
Leave comments
See a list of builds 1
See a build log 1
Download and browse build artifacts 1
Pull project code
Download project
Create code snippets
Manage issue tracker
Manage labels
See a commit status
See a container registry
Manage merge requests
Create new merge request
Create new branches
Push to non-protected branches
Force push to non-protected branches
Remove non-protected branches
Add tags
Write a wiki
Cancel and retry builds
Create or update commit status
Update a container registry
Create new milestones
Add new team members
Push to protected branches
Enable/disable branch protection
Turn on/off prot. branch push for devs
Rewrite/remove git tags
Edit project
Add deploy keys to project
Configure project hooks
Manage runners
Manage build triggers
Manage variables
Switch visibility level
Transfer project to another namespace
Remove project
Force push to protected branches 2
Remove protected branches 2

Group

In order for a group to appear as public and be browsable, it must contain at least one public project.

Any user can remove themselves from a group, unless they are the last Owner of the group.

Action Guest Reporter Developer Master Owner
Browse group
Edit group
Create project in group
Manage group members
Remove group

External Users

In cases where it is desired that a user has access only to some internal or private projects, there is the option of creating External Users. This feature may be useful when for example a contractor is working on a given project and should only have access to that project.

External users can only access projects to which they are explicitly granted access, thus hiding all other internal or private ones from them. Access can be granted by adding the user as member to the project or group.

They will, like usual users, receive a role in the project or group with all the abilities that are mentioned in the table above. They cannot however create groups or projects, and they have the same access as logged out users in all other cases.

An administrator can flag a user as external through the API or by checking the checkbox on the admin panel. As an administrator, navigate to Admin > Users to create a new user or edit an existing one. There, you will find the option to flag the user as external.


  1. If Allow guest to access builds is enabled in CI settings 
  2. Not allowed for Guest, Reporter, Developer, Master, or Owner 

利用scp 远程上传下载文件/文件夹

利用scp传输文件

1、从服务器下载文件
scp username@servername:/path/filename /tmp/local_destination
例如scp codinglog@192.168.0.101:/home/kimi/test.txt  把192.168.0.101上的/home/kimi/test.txt
的文件下载到 /tmp/local_destination
2、上传本地文件到服务器
scp /path/local_filename username@servername:/path
例如scp /var/www/test.php  codinglog@192.168.0.101:/var/www/  把本机/var/www/目录下的test.php文件
上传到192.168.0.101这台服务器上的/var/www/目录中

3、从服务器下载整个目录
scp -r username@servername:remote_dir/ /tmp/local_dir
例如:scp -r codinglog@192.168.0.101 /home/kimi/test  /tmp/local_dir

4、上传目录到服务器
scp  -r /tmp/local_dir username@servername:remote_dir
例如:
scp -r test      codinglog@192.168.0.101:/var/www/   把当前目录下的test目录上传到服务器的/var/www/ 目录

参考:http://www.cnblogs.com/no7dw/archive/2012/07/07/2580307.html