I just upgraded my XAMPP to latest release and found myself trapped with no memory of how to install xdebug on a Mac with XAMPP. Install Xcode and autoconf Thanks to and pointing out that I had not noticed I had all the needed developer tools already in place from all the development I do on my Mac. According to Cedric’s experience, you’ll need to have at least Autoconf installed via or and that in turn will require you to install Xcode.
Once you have Xcode installed, go to Xcode prefs - Downloads pane and install ‘Xcode command line tools’ and when that is done, open terminal and enter: sudo xcode-select -switch /Applications/Xcode.app This will set the folder where the Xcode is installed so that all the command line tools find it. Now continue with Macports or Homebrew to install autoconf. Install XAMPP Developer package Building xdebug requires you to have php headers, so download and install corresponding developer package for. Download xdebug Download xdebug source from or checkout from GIT: git clone git://github.com/derickr/xdebug.git cd xdebug 3. PHPIZE Run phpize /Applications/XAMPP/xamppfiles/bin/phpize 4. Hi, I need to setup xdebug on my 64-Bit Mac OS X Leopard, and your post is the most relevant one I can find for my needs. I have XAMPP working fine and after I generate the xdebug.so file, i receive the following error: Failed loading /Applications/XAMPP/xamppfiles/lib/php/php-5.3.1/extensions/no-debug-non-zts-20090626/xdebug.so: dlopen(/Applications/XAMPP/xamppfiles/lib/php/php-5.3.1/extensions/no-debug-non-zts-20090626/xdebug.so, 9): no suitable image found.
Did find: /Applications/XAMPP/xamppfiles/lib/php/php-5.3.1/extensions/no-debug-non-zts-20090626/xdebug.so: mach-o, but wrong architecture Can you please help me? Hi Roosevelt, Can you check that you configured Xdebug with i386 support as XAMPP is still compiled for i386/ppc, not x8664. To do that, run: lipo -info /Applications/XAMPP/xamppfiles/lib/php/php-5.3.1/extensions/no-debug-non-zts-20090626/xdebug.so And see that it lists i386 as an architecture. If it does not, please recheck step 4 above, to set appropriate flags for the compiler. BTW, I switched my XAMPP for a self-compiled apache and did not need xdebug anymore, so I haven’t recompiled it since. But I still hope this post is not that outdated and still aplies.
Apr 17, 2012 - There are some steps you need to be aware of. First requirement is that you have a working installation of XAMPP on your Mac. Sep 18, 2013 Step 4: Here, you can select the components you want to install. Choose the default selection and click ‘Next’. Step 5: Choose the folder you want to install XAMPP in. This folder will hold all your web application files, so make sure to select a drive that has plenty of space.
I followed your instructions and ran into a problem with the phpize command, because autoconf wasn’t available on my system. To work this out I installed Xcode via the Mac App Store, then I installed the Xcode Command Line Tools (via the Xcode prefs - downloads pane), then I had to set the Xcode folder with the command line tool xcode-select (I set the folder to /Applications/Xcode). After all that, I installed macports to get autoconf Without the Xcode command line tools, and the xcode-select configuration, macports refused to operate which explains all the steps. Hope this helps others as well. This has been the best explanation of why I get the architecture issue when attempting to use Xdebug in my dev environment. I have been going in circles getting AMPPS configured on a Mac OSX 10.8 with PHP debugging.
I consistently get the wrong architecture. I tried both methods of changing the architecture listed here in the blog post (thank you), but I still get a x8664 architecture when running ‘sudo make install’. I’ve included the terminal output below for reference to the process. Any ideas on why I can’t seem to compile in the right architecture would be appreciated. Xdebug-2.2.2 jeremiah$./configure -enable-xdebug -with-php-config=/Applications/AMPPS/php-5.3/bin/php-config CFLAGS='-arch i386 $CFLAGS' CCFLAGS='-arch i386 $CCFLAGS' CXXFLAGS='-arch i386 $CXXFLAGS' LDFLAGS='-arch i386 $LDFLAGS' checking for grep that handles long lines and -e. /usr/bin/grep checking for egrep.
/usr/bin/grep -E checking for a sed that does not truncate output. /usr/bin/sed checking for cc. Cc checking whether the C compiler works. Yes checking for C compiler default output file name.
A.out checking for suffix of executables. Checking whether we are cross compiling.
No checking for suffix of object files. O checking whether we are using the GNU C compiler. Yes checking whether cc accepts -g. Yes checking for cc option to accept ISO C89. None needed checking how to run the C preprocessor. Cc -E checking for icc. No checking for suncc.
No checking whether cc understands -c and -o together. Yes checking for system library directory. Lib checking if compiler supports -R. No checking if compiler supports -Wl,-rpath. Yes checking build system type. I386-apple-darwin12.3.0 checking host system type. I386-apple-darwin12.3.0 checking target system type.
![For For](https://elgg.org/plugins/icon/874534/icon.jpg)
I386-apple-darwin12.3.0 checking for PHP prefix. /Applications/AMPPS/php-5.3 checking for PHP includes.I/Applications/AMPPS/php-5.3/include/php -I/Applications/AMPPS/php-5.3/include/php/main -I/Applications/AMPPS/php-5.3/include/php/TSRM -I/Applications/AMPPS/php-5.3/include/php/Zend -I/Applications/AMPPS/php-5.3/include/php/ext -I/Applications/AMPPS/php-5.3/include/php/ext/date/lib checking for PHP extension directory. /Applications/AMPPS/php-5.3/lib/extensions/no-debug-non-zts-20090626 checking for PHP installed headers prefix.
/Applications/AMPPS/php-5.3/include/php checking if debug is enabled. No checking if zts is enabled.
No checking for re2c. No configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers. Checking for gawk. No checking for nawk. No checking for awk. Awk checking if awk is broken. No checking whether to enable eXtended debugging support.
Yes, shared checking Check for supported PHP versions. Supported (5.3.21) checking for gettimeofday. Yes checking for cos in -lm. Yes checking for ld used by cc.
/usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld. No checking for /usr/bin/ld option to reload object files.r checking for BSD-compatible nm. /usr/bin/nm checking whether ln -s works.
Yes checking how to recognize dependent libraries. Passall checking for ANSI C header files. Yes checking for sys/types.h. Yes checking for sys/stat.h.
Yes checking for stdlib.h. Yes checking for string.h.
Yes checking for memory.h. Yes checking for strings.h.
Yes checking for inttypes.h. Yes checking for stdint.h. Yes checking for unistd.h.
Yes checking dlfcn.h usability. Yes checking dlfcn.h presence. Yes checking for dlfcn.h. Yes checking the maximum length of command line arguments. 196608 checking command to parse /usr/bin/nm output from cc object. Ok checking for objdir.libs checking for ar.
Ar checking for ranlib. Ranlib checking for strip. Strip checking for dsymutil. Dsymutil checking for nmedit.
Nmedit checking for -singlemodule linker flag. Yes checking for -exportedsymbolslist linker flag. Yes checking if cc supports -fno-rtti -fno-exceptions. Yes checking for cc option to produce PIC.fno-common checking if cc PIC flag -fno-common works. Yes checking if cc static flag -static works. No checking if cc supports -c -o file.o. Yes checking whether the cc linker (/usr/bin/ld) supports shared libraries.
Yes checking dynamic linker characteristics. Darwin12.3.0 dyld checking how to hardcode library paths into programs. Immediate checking whether stripping libraries is possible. Yes checking if libtool supports shared libraries.
Yes checking whether to build shared libraries. Yes checking whether to build static libraries. No creating libtool appending configuration tag 'CXX' to libtool configure: creating./config.status config.status: creating config.h config.status: config.h is unchanged Like. Hi Jeremiah, From your output, I can’t tell what went wrong (probably because./configure does not report setting the flags).
I’ve confirmed that above method still does produce 32-bit binary in Mac OS X 10.8.3 Mountain Lion. Also, I updated the step 4 above and added a screenshot of Makefile differences that should help you to adjust your Makefile manually. If that still doesn’t produce 32-bit binary, then I’m afraid, this goes beyond my knowledge of Mac OS X compiler settings (maybe there is a global forced setting somewhere deep in system etc).
Laravel 5.7 requires PHP version 7.1.3 or more, and some other extensions. Since we are doing setup on XAMPP. Make sure to Install the XAMPP with version = 7.2.0. Install XAMPP First of all we need to download and install XAMPP.
Download it from the. Download the XAMPP version 7.2.0. Download the version for OSX (Mac). Follow the steps to install the XAMPP. If you are on MAC, the install location for XAMPP will be /Applications/XAMPP.
Once the XAMPP is Installed, you should be able to access the XAMPP Console from where you can start or stop the necessary services. If you XAMPP is installed correctly and if you have the apache service running under it, you should see the following page when you access localhost on your browser. Composer After you have downloaded XAMPP, We need to install Composer. Composer is a dependency management or package management tool which is integrated with Laravel Framework. Check by running composer command in your terminal if your system has composer already installed in it.
If not you can install it by following the steps for OSX ( ). Install Laravel Framework The default directory of XAMPP for installing or keeping PHP project is htdocs. Navigate to following directory in your terminal /Applications/XAMPP/htdocs and run following composer command to create a fresh Laravel 5.5 version composer create-project laravel/laravel myProject '5.5.' After running this command composer should start downloading dependencies that are required to create the Laravel project. –More downloading– When it finishes it will create a Laravel 5.5 project with following data structure.
Modify Directory Permissions In the newly created Laravel Project we need to modify the directory permissions of certain directory otherwise we will get following error on accessing the project The stream or file “laravel.log” could not be opened: failed to open stream: Permission denied. cd into your Laravel project. sudo chmod -R 777 storage. sudo chmod -R 777 bootstrap/cache XAMPP Virtual Host We need to configure XAMPP Virtual Host to set the document root to correct directory of laravel project and to also assign a name to the project by which we will be accessing it in browser. Navigate and open file /Applications/XAMPP/etc/httpd.conf file and uncomment the line that includes the virtual host file. # Virtual hosts Include etc/extra/httpd-vhosts.conf Navigate and open file /Applications/XAMPP/etc/extra/httpd-vhosts.conf and include following Virtual host entry in this file.
# VirtualHost for LARAVEL.LOCAL DocumentRoot 'C: xampp htdocs myProject public' ServerAdmin laravel.local Options Indexes FollowSymLinks AllowOverride All Require all granted With this entry our apache is listening to laravel.local, but we also have to edit our hosts file to include an entry for the new domain. Edit file /etc/hosts and add following entry to that file. 127.0.0.1 laravel.local Restart your apache and access laravel.local on your browser you should be able to see this screen.