The mac install is confusing. Right now, "watir" only works on
windows. But "watir" is installed when you install firewatir on mac.
It all really depends on what you mean by "watir".

We will fix this on a future release. But right now, you have what you
need, and the "watir" example code will work for you.
Watir::Browser.new, etc etc will do the right thing.

Bret

On Oct 6, 3:11 pm, QAguy <qablogm...@gmail.com> wrote:
> Thanks for writing. I have those 2 installed already on my MAC:
>
> safariwatir (0.3.3)
> firewatir (1.6.2)
>
> but a straight
> sudo gem install watir fails. Is that gem not able to be installed on
> the MAC?
>
> Thanks
>
> On Oct 6, 3:40 pm, Bret Pettichord <bpettich...@gmail.com> wrote:> sudo gem 
> install firewatir
> > sudo gem install safariwatir
>
> > On Oct 6, 1:28 pm, QAguy <qablogm...@gmail.com> wrote:
>
> > > When I try to install the watir gem on the mac I am getting the
> > > following:
>
> > > host73:watir_site_regression employee$ sudo gem install watir --
> > > include-dependencies
> > > INFO:  `gem install -y` is now default and will be removed
> > > INFO:  use --ignore-dependencies to install only the gems you list
> > > Building native extensions.  This could take a while...
> > > ERROR:  Error installing watir:
> > >         ERROR: Failed to build gem native extension.
>
> > > /opt/local/bin/ruby extconf.rb
> > > checking for strncpy_s()... no
> > > creating Makefile
>
> > > make
> > > /usr/bin/gcc-4.2 -I. -I. -I/opt/local/lib/ruby/1.8/i686-darwin10 -I. -
> > > I/opt/local/include -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE  -I/opt/local/
> > > include -fno-common -O2 -arch x86_64  -fno-common -pipe -fno-common  -
> > > arch x86_64 -c win32/api.c
> > > win32/api.c:2:21: error: windows.h: No such file or directory
> > > win32/api.c:33: error: expected specifier-qualifier-list before
> > > ‘HANDLE’
> > > win32/api.c: In function ‘api_free’:
> > > win32/api.c:40: error: ‘Win32API’ has no member named ‘library’
> > > win32/api.c:41: error: ‘Win32API’ has no member named ‘library’
> > > win32/api.c: At top level:
> > > win32/api.c:58: error: expected ‘)’ before ‘dwError’
> > > win32/api.c: In function ‘callback_init’:
> > > win32/api.c:186: error: ‘LPARAM’ undeclared (first use in this
> > > function)
> > > win32/api.c:186: error: (Each undeclared identifier is reported only
> > > once
> > > win32/api.c:186: error: for each function it appears in.)
> > > win32/api.c:186: error: expected ‘)’ before ‘find_callback’
> > > win32/api.c: In function ‘api_init’:
> > > win32/api.c:233: error: ‘HMODULE’ undeclared (first use in this
> > > function)
> > > win32/api.c:233: error: expected ‘;’ before ‘hLibrary’
> > > win32/api.c:234: error: ‘FARPROC’ undeclared (first use in this
> > > function)
> > > win32/api.c:234: error: expected ‘;’ before ‘fProc’
> > > win32/api.c:270: error: ‘hLibrary’ undeclared (first use in this
> > > function)
> > > win32/api.c:280: error: ‘Win32API’ has no member named ‘library’
> > > win32/api.c:287: error: ‘fProc’ undeclared (first use in this
> > > function)
> > > win32/api.c:330: error: ‘Win32API’ has no member named ‘function’
> > > win32/api.c:338: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:341: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:344: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:347: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:350: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:353: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:367: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:373: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:376: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:379: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:382: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:385: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c: In function ‘func_init’:
> > > win32/api.c:456: error: ‘Win32API’ has no member named ‘function’
> > > win32/api.c:456: error: ‘FARPROC’ undeclared (first use in this
> > > function)
> > > win32/api.c:464: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:467: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:470: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:473: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:476: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:479: error: ‘Win32API’ has no member named ‘prototype’
> > > win32/api.c:493: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:499: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:502: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:505: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:508: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c:511: error: ‘Win32API’ has no member named ‘return_type’
> > > win32/api.c: At top level:
> > > win32/api.c:528: error: expected specifier-qualifier-list before
> > > ‘DWORD’
> > > win32/api.c:532: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CallbackFunction’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:690: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:692: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:693: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:694: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:694: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:694: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘CALLBACK’
> > > win32/api.c:694: error: expected ‘=’, ‘,’, ‘;’, ‘asm’
>
> > ...
>
> > read more »
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To post to this group, send email to watir-general@googlegroups.com
Before posting, please read the following guidelines: 
http://wiki.openqa.org/display/WTR/Support
To unsubscribe from this group, send email to 
watir-general-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/watir-general
-~----------~----~----~----~------~----~------~--~---

Reply via email to