I am getting some kind of compile error, in a file called gnome-metadata. Here is the error I am getting, if it helps any. You'll have to excuse my ignorance of Gnome, I never cared for it much as a desktop environment, and never really learned a whole lot about how it and all its libraries work.
You can post now and register later. If you have an account, sign in now to post with your account. Note: Your post will require moderator approval before it will be visible. Paste as plain text instead. Only 75 emoji are allowed. Display as a link instead. Clear editor. Upload or insert images from URL.
Share More sharing options Followers 0. This will pull in several other development packages. You can do the yum -y install development-tools which will pull in lots of extra stuff. Some of them will have the same name, others often don't. If you're following a tutorial, you should email the author and tell them to make it clear that the instructions are for Ubuntu.
If it's a good tutorial, they should track down the names of the packages with RH based systems, and give that as wellor say something like this is Ubuntu only, if you want to build it on another system, you have to track it down on your own. You don't say what you are trying to compile, but on package-based systems it is always best to first search available repos. If you have specific questions, please come back and ask, with appropriate details.
The more background you provide within reason :- the better help you can expect. Raw Blame. Open with Desktop View raw View blame. This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters Show hidden characters. Guess values for system-dependent variables and create Makefiles. Generated by GNU Autoconf 2. This configure script is free software; the Free Software Foundation. M4sh Initialization. Be more Bourne compatible. Disable this feature. Prefer a ksh shell builtin over an external printf program on Solaris,. The user is always right.
We need space, tab and new line, in precisely that order. Quoting is. Find who we are. Look in the path if we contain no directory separator. Unset variables that we do not need and which cause bugs e. But do not cause bugs in bash 2. NLS nuisances. Use a proper internal environment variable to ensure we don't fall. We cannot yet assume a decent shell, so we have to provide a. Preserve -v and -x to the replacement shell. Admittedly, this is quite paranoid, since all the known shells bail.
We don't want this to propagate to other subprocesses. Try only shells that exist, to save several forks. Then install. Unset more variables known to interfere with behavior of common tools. M4sh Shell Functions.
Portably unset VAR. Test if FILE is an executable regular file. Perform arithmetic evaluation on the ARGs, and store the result in the. Take advantage of shells that can avoid forks.
The arguments. Then exit the. Avoid depending upon Character Ranges. Blame Lee E. McMahon for sed's syntax. This has already happened in practice. Autoconf is especially sensitive to this. Exit status is that of the last command. Sed expression to map a string onto a valid CPP name. Sed expression to map a string onto a valid variable name.
Name of the host. Identity of this package. Factoring default headers for most tests. RPATH '. Initialize some variables set by options. The variables have the same names as the options, with. Installation directory options. Use braces instead of parens because sh, perl, etc. If the previous option needs an argument, assign it.
0コメント