Note: If you want to install a 32-bit or 64-bit version of Office, but this is different from what you previously installed, you need to first. You can then select the version you want. Select Other install options, your language, and then under Version select Advanced, and choose 64-bit or 32-bit, and then select Install. For more information about which version is right for you see.
Office should now begin downloading. Follow the prompts in Step 2 to complete the installation.
Don't see an install option after signing in? There could be an issue with your account. Select from above and review the section Account questions. Step 2: Install Office.
Download p7zip for Linux (Posix) (x86 binaries and source code): p7zip at SourceForge p7zip is the command line version of 7-Zip for Linux / Unix, made by an independent developer. Oct 10, 2017 - Description When using this command to install php brew install php70 --with-httpd. This is caused by the httpd formula changing the default mpm from prefork to event so if you.
Depending on your browser, select Run (in Edge or Internet Explorer), Setup (in Chrome), or Save File (in Firefox). If you see the User Account Control prompt that says, Do you want to allow this app to make changes to your device? The install begins. Your install is finished when you see the phrase, 'You're all set! Office is installed now' and an animation plays to show you where to find Office applications on your computer. Select Close. Follow the instructions in the window to find your Office apps.
For example depending on your version of Windows, select Start and then scroll to find the app you want to open such as Excel or Word, or type the name of the app in the search box. Installation or sign in issues? If you're having an installation issue such as Office taking long to install, try for a list of common issues. Step 3: Activate Office Start using an Office application right away by opening any app such as Word or Excel.
In most cases, Office is activated once you start an application and after you click Accept to agree to the License terms. If you need activation help, see. Select Install Office Apps Office 2016 if you signed in with a work or school account. (Note: The link may say Office 2016, however Office will install the most up-to-date version of the Office apps as set by your Office 365 admin.) This begins the download of Office.
Prefork C Download For Mac
Follow the prompts on your screen to complete the install. Don't see an install option after signing in? There could be an issue with your account. Select from above and review the issues listed in the section Account questions.
Step 2: Install Office. Once the download has completed, open Finder, go to Downloads, and double-click Microsoft Office installer.pkg file (the name might vary slightly). Tip: If you see an error that says the Microsoft Office installer.pkg can't be opened because it is from an unidentified developer, wait 10 seconds and move the downloaded file to your desktop. Hold Control + click the file to launch the installer. On the first installation screen, select Continue to begin the installation process. Review the software license agreement, and then click Continue.
Select Agree to agree to the terms of the software license agreement. Choose how you want to install Office and click Continue. Review the disk space requirements or change your install location, and then click Install. Note: If you want to only install specific Office apps and not the entire suite, click the Customize button and uncheck the programs you don't want. Enter your Mac login password, if prompted, and then click Install Software.
(This is the password that you use to log in to your Mac.). The software begins to install. Click Close when the installation is finished. If Office installation fails, see. Step 3: Launch an Office for Mac app and start the activation process.
Click the Launchpad icon in the Dock to display all of your apps. Click the Microsoft Word icon in the Launchpad. The What's New window opens automatically when you launch Word. Click Get Started to start activating. If you need help activating Office, see. If Office activation fails, see. Installation notes Installation notes How do I pin the Office app icons to the dock?.
Go to Finder Applications and open the Office app you want. In the Dock, Control+click or right-click the app icon and choose Options Keep in Dock. Can I install Office on my iPhone or iPad? If you're trying to sign in with your work or school account to www.office.com and your sign in is blocked, it likely means your Office 365 administrator set up a security policy that's preventing you from signing in to that location.
To install Office, try signing in directly to the page instead. Select the language and bit-version you want (PC users can choose between 32-bit and 64-bit), and then click Install.
See Steps 2 and 3 on the PC or Mac tabs above to help you with the rest of the install process. Office won't install: Your computer must be running a supported operating system to install Office. You can find a list of which systems are supported on the page. For example, your install won't be successful if you're trying to install Office on a computer running Windows Vista or Windows XP operating system.
If your computer can't install the full desktop version of Office, try the free using your desktop browser. I received an error message: If you got an error message while trying to install Office and it has a Learn More link, select it to get information for how to troubleshoot that particular error. If there wasn't a link, see. I received an unsupported operating system message: If you got an unsupported operating system error message you may be trying to install Office on an unsupported device such as installing the Mac version of Office on a PC or vice versa, or trying to install Office on a Chromebook or other mobile device. Help with specific applications, and help for Office 365 admins.
Checking Your Installation When debugging modwsgi or a WSGI application, it is import to be able to understand how modwsgi has been installed, what Apache and/or Python it uses and how those systems have been configured, plus under what configuration the WSGI application is running. This document details various such checks that can be made. The primary purpose of providing this information is so that when people ask questions on the modwsgi mailing list, they can be directed here to perform certain checks as a way of collecting additional information needed to help debug their problem. If you are reading this document because you have been directed here from the mailing list, then ensure that you actually provide the full amount of detail obtained from the checks and not leave out information.
When you leave out information then it means guesses have to be made about your setup which makes it harder to debug your problems. $ /usr/sbin/httpd -V Server version: Apache/2.2.14 (Unix) Server built: Feb 10 2010 22:22:39 Server's Module Magic Number: 20051115:23 Server loaded: APR 1.3.8, APR-Util 1.3.9 Compiled using: APR 1.3.8, APR-Util 1.3.9 Architecture: 64-bit Server MPM: Prefork threaded: no forked: yes (variable process count) Server compiled with. /bin/sh # # Created by configure '/SourceCache/apache/apache-747.1/httpd/configure' '-prefix=/usr' '-enable-layout=Darwin' '-with-apr=/usr' '-with-apr-util=/usr' '-with-pcre=/usr/local/bin/pcre-config' '-enable-mods-shared=all' '-enable-ssl' '-enable-cache' '-enable-mem-cache' '-enable-proxy-balancer' '-enable-proxy' '-enable-proxy-http' '-enable-disk-cache' '$@' Not only does this indicate what features of Apache have been compiled in, it also indicates by way of the -enable-layout option what custom Apache installation layout has been used. $ /usr/sbin/httpd -l Compiled in modules: core.c prefork.c httpcore.c modso.c This indicates that the only module that is loaded statically is ‘modso’. This is actually the Apache module that handles the task of dynamically loading other Apache modules. For a specific Apache configuration, you can determine what Apache modules will be loaded dynamically by using the -M option for the Apache executable. On MacOS X, for the operating system supplied Apache the output from running -M option, where the only additional module added is modwsgi, is.
Global Accept Mutex Because Apache is a multi process server, it needs to use a global cross process mutex to control which of the Apache child processes get the next chance to accept a connection from a HTTP client. This cross process mutex can be implemented using a variety of different mechanisms and exactly which is used can vary based on the operating system. Which mechanism is used can also be overridden in the Apache configuration if absolutely required. A simlar instance of a cross process mutex is also used for each modwsgi daemon process group to mediate which process in the daemon process group gets to accept the next request proxied to that daemon process group via the Apache child processes. The list of mechanisms which might be used to implement the cross process mutex are as follows. flock. fcntl.
sysvsem. posixsem. pthread In the event that there are issues which communicating between the Apache child processes and the modwsgi daemon process in particular, it can be useful to know what mechanism is used to implement the cross process mutex.
By default, the Apache configuration files would not specify a specific mechanism, and instead which is used would be automatically selected by the underlying Apache runtime libraries based on various build time and system checks about what is the prefered mechanism for a particular operating system. Which mechanism is used by default can be determined from the build information displayed by the -V option to the Apache executable described previously. The particular entries of interest are those with ‘SERIALIZE’ in the name of the macro. On MacOS X, using operating system supplied Apache, the entries of interest are. D APRUSESYSVSEMSERIALIZE - D APRUSEPTHREADSERIALIZE which indicates that ‘sysvsem’ mechanism is instead used. This mechanism is also what would be used by modwsgi by default as well for the cross process mutex for daemon process groups.
This mechanism will be different where the AcceptMutex and WSGIAcceptMutex directives are used. If the AcceptMutex directive is defined in the Apache configuration file, then what ever mechanism is specified will be used instead for Apache child processes. Provided that Apache 2.2 or older is used, and WSGIAcceptMutex is not specified, then when AcceptMutex is used, that will also then be used by modwsgi daemon processes as well.
In the case of Apache 2.4 and later, AcceptMutex will no longer override the default for modwsgi daemon process groups, and instead WSGIAcceptMutex must be specified seperately if it needs to be overridden for both. Either way, you should check the Apache configuration files as to whether either AcceptMutex or WSGIAcceptMutex directives are used as they will override the defaults calculated above. Under normal circumstances neither should be set as default would always be used. If wanting to look at overriding the default mechanism, what options exist for what mechanism can be used will be dependent on the operating system being used.
There are a couple of ways this can be determined. The first is to find the ‘apr.h’ header file from the Apache runtime library installation that Apache was compiled against. In that you will find entries similar to the ‘USE’ macros above. You will also find ‘HAS’ entries. In this case we are interested in the ‘HAS’ entries. On MacOS X, with the operating system supplied APR library, the entries in ‘apr.h’ are.
$ ldd modwsgi.so linux-vdso.so.1 = (0x00007fffeb3fe000) libpython2.5.so.1.0 = /usr/local/lib/libpython2.5.so.1.0 (0x00002adebf94d000) libpthread.so.0 = /lib/libpthread.so.0 (0x00002adebfcba000) libdl.so.2 = /lib/libdl.so.2 (0x00002adebfed6000) libutil.so.1 = /lib/libutil.so.1 (0x00002adec00da000) libc.so.6 = /lib/libc.so.6 (0x00002adec02dd000) libm.so.6 = /lib/libm.so.6 (0x00002adec0635000) /lib64/ld-linux-x86-64.so.2 (0x554000) What you want to see is a reference to an instance of ‘libpythonX.Y.so’. Normally the operating system shared library version suffix would always be ‘1.0’. What it is shouldn’t really matter though. This reference should refer to the actual Python shared library for your Python installation. Do note though, that ‘ldd’ will take into consideration any local user setting of the ‘LDLIBRARYPATH’ environment variable. That is, ‘ldd’ will also search any directories listed in that environment variable for shared libraries.
Although that environment variable may be defined in your user account, it will not normally be defined in the environment of the account that Apache starts up as. Thus, it is important that you unset the ‘LDLIBRARYPATH’ environment variable when running ‘ldd’.
If you run the check with and without ‘LDLIBRARYPATH’ set and find that without it that a different, or no Python shared library is found, then you will likely have a problem. For the case of it not being found, Apache will fail to start. For where it is found but it is a different installation to that which you want used, subtle problems could occur due to C extension modules for Python being used which were compiled against that installation.
For example, if ‘LDLIBRARYPATH’ contained the directory ‘/usr/local/lib’ and you obtained the results above, but when you unset it, it picked up shared library from ‘/usr/lib’ instead, then you may end up with problems if for a different installation. In this case you would see.
$ unset LDLIBRARYPATH $ ldd modwsgi.so linux-vdso.so.1 = (0x00007fffeb3fe000) libpython2.5.so.1.0 = /usr/lib/libpython2.5.so.1.0 (0x00002adebf94d000) libpthread.so.0 = /lib/libpthread.so.0 (0x00002adebfcba000) libdl.so.2 = /lib/libdl.so.2 (0x00002adebfed6000) libutil.so.1 = /lib/libutil.so.1 (0x00002adec00da000) libc.so.6 = /lib/libc.so.6 (0x00002adec02dd000) libm.so.6 = /lib/libm.so.6 (0x00002adec0635000) /lib64/ld-linux-x86-64.so.2 (0x554000) Similarly, if not found at all, you would see. $ otool -L modwsgi.so modwsgi.so: /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0) /System/Library/Frameworks/Python.framework/Versions/2.6/Python (compatibility version 2.6.0, current version 2.6.1) If using standard MacOS X compilers and not using Fink or!MacPorts, there generally should not ever be any issues with whether it is a shared library or not as everything should just work. The only issue with MacOS X is that for whatever reason, the location dependency for the shared library (framework) isn’t always encoded into ‘modwsgi.so’ correctly. This seems to vary between what Python installation was used and what MacOS X operating system version. In this case, if multiple installations of same version of Python in different locations, may find the system installation rather than your custom installation. In that situation you may need to use the -disable-framework option to ‘configure’ script for modwsgi.
This doesn’t actually disable use of the framework, but does change how it links to use a more traditional library style linking rather than framework linking. This seems to resolve the problems in most cases.
Python Installation In Use Although the ‘modwsgi.so’ file may be finding a specific Python shared library and that may be from the correct installation, the Python library when initialised doesn’t actually know from where it came. As such, it uses a series of checks to try and determine where the Python installation is actually located. This check has various subtleties and how it works varies depending on the platform used. At its simplest though, on most UNIX systems it will check all directories listed in the ‘PATH’ environment variable of the process.
In each of those directories it will look for the ‘python’ program. When it finds such a file, it will then look for a corresponding ‘lib’ directory containing a valid Python installation for the same version of Python as is being run. When it finds such a directory, the home for the Python installation will be taken as being the parent directory of the directory containing the ‘python’ program file found. Because this search is dependent on the ‘PATH’ environment variable, which is likely set to a minimal set of directories for the Apache user, then if you are using a Python installation in a non standard location, then it may not properly find the location of that installation. The easiest way to validate which Python installation is being used is to use a test WSGI script to output the value of ‘sys.prefix’. Import sys def application ( environ, startresponse ): status = '200 OK' output = u 'sys.path =%s '% repr ( sys.
Path ) responseheaders = ( 'Content-type', 'text/plain' ), ( 'Content-Length', str ( len ( output ))) startresponse ( status, responseheaders ) return output. Encode ( 'UTF-8' ) In both cases, even if incorrect location is being used for Python installation and even if there is no actual Python installation of the correct version under that root directory, then these test scripts should still run as ‘sys’ module is a builtin module which can be satisified via just the Python library. If debugging, whether there is a Python installation underneath that root directory, the subdirectory which you would want to look for is ‘lib/pythonX.Y’ corresponding to version of Python being used. If the calculated directory is wrong, then you will need to use the WSGIPythonHome directory to set the location to the correct value. The value to use is what ‘sys.prefix’ is set to when the correct Python is run from the command line and ‘sys.prefix’ output.
Single Or Multi Threaded Apache supports differing Multiprocessing Modules (MPMs) having different attributes. One such difference is whether a specific Apache child process uses multiple threads for handling requests or whether a single thread is instead used.
Depending on how you configure a daemon process group when using daemon mode will also dictate whether single or multithreaded. By default, if number of threads is not explicitly specified for a daemon process group, it will be multithreaded. Whether a WSGI application is executing within a multithreaded environment is important to know. If it is, then you need to ensure that your own code and any framework you are using is also thread safe. A test WSGI script for validating whether WSGI application running in multithread configuration is as follows.