e3be
![]() |
|
|
|
|
|||||||
| Installation and Maintenance of FreeBSD Ports or Packages Installing and maintaining the FreeBSD Ports Collection or FreeBSD Packages (i.e. third party software). |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
When I run "make" I get this error:
Code:
make: don't know how to make cflags. Stop https://github.com/c00kiemon5ter/monsterwm Thanks. |
|
#2
|
|||
|
|||
|
Solved.
|
|
#3
|
||||
|
||||
|
__________________
Senior UNIX Engineer at Unix Support Nederland Experience is something you don't get until just after you need it. |
|
#4
|
|||
|
|||
|
Yes, I didn't know that FreeBSD had a different "make" than GNU/Linux.
|
|
#5
|
|||
|
|||
|
It actually doesn't work on me. I edited that too, but still the same errors. Isn't it true that source code for GNU/Linux won't compile on *BSD?
__________________
"put your faith in me, in every fantasy - the phuture is a saviour" |
|
#6
|
|||
|
|||
|
It usually does assuming tools like devel/autoconf etc are used properly and the source code is of such nature that it doesn't make assumptions about the system. Source code that depends on the internals of the operating system is very rarely portable to other systems though.
|
|
#7
|
|||
|
|||
|
Try compiling with default settings, and see if it works. Then try adding more and more of your own settings to get to the root of the problem. Also, make sure your ports tree is up to date.
Usually, you shouldn't play with CFLAGS too much, since they're pretty well configured for each port. Any changes you make there will work for some packages but not for all in general, so you'd have to switch back and in some cases and recompile them again along with all dependencies, which makes it annoying in time. There is also actually a pretty good reason, why you should keep stuff in /usr/local/ ... the thing is that /usr/ holds some parts of the base system. When you're upgrading your FreeBSD "world" and issue # make installworld, it may do some funny things to your installed packages there, but keeping things separate ensures your packages and their config files (yup ... /usr/local/etc/) remain intact throughout the whole procedure. Which is awesome (obviously!)
Last edited by jozze; April 29th, 2013 at 09:06. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [Solved] How do I change port compile options after first compile? | michaelrmgreen | Installation and Maintenance of FreeBSD Ports or Packages | 2 | February 15th, 2013 16:55 |
| math/fftw3 - Variable CFLAGS is recursive. | break19 | Installation and Maintenance of FreeBSD Ports or Packages | 11 | September 25th, 2011 22:47 |
| [Solved] WITH_DEBUG and CFLAGS sometimes are ignored | kenorb | Installation and Maintenance of FreeBSD Ports or Packages | 2 | November 11th, 2010 12:17 |
| how to compile new BSD Distro | Security-Defensive | General | 12 | October 26th, 2010 07:40 |
| What's better for upgrade base system ? + Question about CFLAGS | elvis4526 | Installing & Upgrading | 7 | August 4th, 2010 04:33 |