![]() |
|
NetBSD General Other questions regarding NetBSD which do not fit in any of the categories below. |
![]() |
|
Thread Tools | Display Modes |
|
|||
![]()
Hi there,
I'm trying to compile a new kernel on NetBSD-4.0.1. But when it comes to "make depend" I get this error: Quote:
I have copied the example from /usr/pkgsrc/mk/defaults/mk.conf to /etc. So I thought it should be ok. Any ideas? |
|
|||
![]() Quote:
thanks for your hint! I will look it up, when I'm home from work this evening. This example mk.conf from pkgsrc is a quite long document and I haven't read it in total ![]() In fact up to now I just used it for building xorg and for several ACCEPTABLE_LICENSE details. |
|
||||
![]()
@nihonto
Did you add any extra options to /etc/mk.conf or you just copied it over to /etc and did a 'make depend'? Also, try deleting the content of mk.conf file and put only stuff you need, there is no need for default options to be listed, and it's way clearer for reading. ![]()
__________________
The best way to learn UNIX is to play with it, and the harder you play, the more you learn. If you play hard enough, you'll break something for sure, and having to fix a badly broken system is arguably the fastest way of all to learn. -Michael Lucas, AbsoluteBSD |
|
||||
![]() Quote:
![]() Quote:
Quote:
![]() By the way - what does the "+" sign mean in front of the equals sign? And I have even seen question marks in front of the equals sign like here: Quote:
|
|
|||
![]()
Well, this evening I have chosen the easy solution
![]() In this new document I placed only entries, that I know I need: Quote:
![]() |
|
|||
![]()
RE: "Malformed conditional". The following, done on OpenBSD, explains this error
Code:
# cat -n Makefile ; make 1 #OPSYS = IRIX 2 3 .if ( ${OPSYS} == "IRIX" ) 4 message: 5 @echo Yes the operating system is IRIX! 6 .endif 7 "Makefile", line 3: Malformed conditional (( ${OPSYS} == "IRIX" )) "Makefile", line 3: Missing dependency operator "Makefile", line 6: if-less endif "Makefile", line 6: Need an operator Fatal errors encountered -- cannot continue Code:
$ cat -n Makefile ; make 1 OPSYS = IRIX 2 3 .if ( ${OPSYS} == "IRIX" ) 4 message: 5 @echo Yes the operating system is IRIX! 6 .endif 7 Yes the operating system is IRIX! A more common cause for the "need an operator" message is using a spaces instead of the required tab in the shell command line (here lines 2-3): Code:
$ cat -nt Makefile 1 message: 2 ^I@echo "Yes the operating system is IRIX!" 3 ^I@echo "===" 4 Yes the operating system is IRIX! === Code:
$ cat -nt Makefile ; make 1 message: 2 @echo "Yes the operating system is IRIX!" 3 @echo "===" 4 "Makefile", line 3: Need an operator Fatal errors encountered -- cannot continue
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
||||
![]() Quote:
Code:
VARIABLE ASSIGNMENTS Variables in make are much like variables in the shell, and, by tradi- tion, consist of all upper-case letters. Variable assignment modifiers The five operators that can be used to assign values to variables are as follows: = Assign the value to the variable. Any previous value is overrid- den. += Append the value to the current value of the variable. ?= Assign the value to the variable if it is not already defined. := Assign with expansion, i.e. expand the value before assigning it to the variable. Normally, expansion is not done until the vari- able is referenced. NOTE: References to undefined variables are not expanded. This can cause problems when variable modifiers are used. != Expand the value and pass it to the shell for execution and assign the result to the variable. Any newlines in the result are replaced with spaces.
__________________
The best way to learn UNIX is to play with it, and the harder you play, the more you learn. If you play hard enough, you'll break something for sure, and having to fix a badly broken system is arguably the fastest way of all to learn. -Michael Lucas, AbsoluteBSD |
|
||||
![]()
As for the error, I found this thread, check Hubert Feyrer's response: http://arkiv.netbsd.se/?ml=netbsd-te...05-01&t=592114
__________________
The best way to learn UNIX is to play with it, and the harder you play, the more you learn. If you play hard enough, you'll break something for sure, and having to fix a badly broken system is arguably the fastest way of all to learn. -Michael Lucas, AbsoluteBSD |
|
|||
![]()
Ahhh, there is a description of the signs
![]() ![]() That's the trick with manpages - you have to know which one solves your needs ![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Opera Port - conflicting pkgs in "make install" | IronForge | OpenBSD Packages and Ports | 5 | 29th October 2009 05:10 AM |
Fixed "xinit" after _7 _8, "how" here in case anyones' "X" breaks... using "nvidia" | jb_daefo | Guides | 0 | 5th October 2009 09:31 PM |
Thoughts on "make deinstall clean" | Mantazz | FreeBSD Ports and Packages | 8 | 14th September 2009 06:45 PM |
"Thanks" and "Edit Tags". | diw | Feedback and Suggestions | 2 | 29th March 2009 12:06 AM |
TIP:a nice way to make your pf more "stealth" | marc | OpenBSD Security | 2 | 30th January 2009 09:39 PM |