Skip to content

Commit 9b2541b

Browse files
committed
+ Added fix for failing Rugged Gem failing to install
+ TOC
1 parent 072b303 commit 9b2541b

File tree

1 file changed

+33
-8
lines changed

1 file changed

+33
-8
lines changed

install/freebsd/README.md

Lines changed: 33 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,48 @@
1+
# FreeBsd 8 / 9 Install Troubleshooting
12

2-
## FreeBsd 8 / 9 Install Troubleshooting
3+
## Naughty Gems
34

45

5-
### Charlock Holmes installation fails
6+
- [charlock_holmes](#charlock-holmes-gem-install-fails-or-breaks-after-pkg-upgrade)
67

7-
Every now and then `devel/icu` (the freebsd port of `libicu-dev`) or another library charlock_holmes depends on will get updated, thus invalidating the gem currently
8-
installed in the gitlab directory.
8+
- [rugged](#rugged-gem-install-fails-wo-gmake)
99

10-
N.B. Your running server will continue normal operation in that case, but updates or things like a rake backup command will suddenly fail.
10+
### Charlock Holmes-Gem install fails or breaks after `pkg upgrade`
1111

12-
__Solution__:
12+
Every now and then `devel/icu` - or other dependencies of charlock_holmes - will get updated, sometimes invalidating the gem installation in the gitlab directory.
1313

14-
Implicetely tell the installer where to look for dependencies:
14+
N.B. Your running server will continue normal operation in that case, but updates and/or rake commands in general may suddenly fail.
15+
16+
__Cure__ ([Kudos to herrBeesch](https://github.com/brianmario/charlock_holmes/issues/9#issuecomment-10370071))
17+
18+
On FreeBSD we need to tell the gem install routine where to look for certain dependencies:
1519

1620
```
1721
sudo gem install charlock_holmes -- --with-icu-dir=/usr/lib --with-opt-include=/usr/local/include/
1822
```
1923

20-
After this has run through, rake commands as well as the update process (repeat last failed step) should resume normal operation.
24+
This process _should_ now succeed, provided _that_ it does, let's store those values in the build configuration for gitlab:
25+
26+
```
27+
sudo -u git -H bundle config build.charlock_holmes --with-opt-include=/usr/local/include/ --with-opt-lib=/usr/local/lib/
28+
```
29+
30+
Now you should be able to pickup where you were when you bumped into this :)
2131

2232

2333

34+
### Rugged-Gem install fails w/o gmake
35+
36+
```
37+
checking for gmake... no
38+
checking for make... yes
39+
-- /usr/bin/make -f Makefile.embed
40+
*** extconf.rb failed ***
41+
Could not create Makefile due to some reason, probably lack of necessary
42+
libraries and/or headers. Check the mkmf.log file for more details. You may
43+
need configuration options.
44+
```
45+
__Remedy__:
46+
47+
Make gmake available `sudo pkg install gmake` (or whatever freebsd install routine you prefer) and retry.
48+

0 commit comments

Comments
 (0)