Many thanks. I _am_ glad someone else had the same problem...
It was the touch pptpd.c that did the trick.
Bob
Jerome Ibanes wrote:
Bob,
mk: don't know how to make '/386/bin/fossil/fossil' in directory
/sys/src/9/pc
touch /386/bin/fossil/fossil then you can mk 'CONF=pcf' if you want
>> touch /386/bin/fossil/fossil then you can mk 'CONF=pcf' if you want.
>
> if you are trying to boot from a fossil root and do this,
> your kernel will not be able to successfully mount the root
> filesystem.
>
> don't do this if you expect to boot.
Only if there was no /386/bin/fossil/fossil b
> Bob,
>
>> mk: don't know how to make '/386/bin/fossil/fossil' in directory
>> /sys/src/9/pc
>
> touch /386/bin/fossil/fossil then you can mk 'CONF=pcf' if you want.
if you are trying to boot from a fossil root and do this,
your kernel will not be able to successfully mount the root
filesystem.
Bob,
> mk: don't know how to make '/386/bin/fossil/fossil' in directory
> /sys/src/9/pc
touch /386/bin/fossil/fossil then you can mk 'CONF=pcf' if you want.
Hope this helps,
Jerome Ibanes
> what i know is
> a) it build just fine on my system, but i don't use pull.
> b) if for some xyzw mk requires xyzw.8 and there's no xyzw.$x
> so that there's a mk rule like so "%.8: %.$x", i get the following
> error message
> ; mk xyzw.8
> mk: no recipe to make 'xyzw.8' in directory /
9,
>> mk: no recipe to make 'pptpd.8' in directory /sys/src/cmd/ip
> does /sys/src/cmd/ip/pptpd.c exist? if not, there must be an
> error in the pull database on sources. you can copy it
> by hand with
> 9fs sources && cp -x /n/sources/plan9/sys/src/cmd/ip/pptpd.c
> /sys/src/cmd/ip/
> Eri
> Erik, it already exists and has the same MD5 checksum than the one in
> sources.
i'm fresh out of ideas, then.
what i know is
a) it build just fine on my system, but i don't use pull.
b) if for some xyzw mk requires xyzw.8 and there's no xyzw.$x
so that there's a mk rule like so "%.8: %.$x", i
9,
>> mk: no recipe to make 'pptpd.8' in directory /sys/src/cmd/ip
> does /sys/src/cmd/ip/pptpd.c exist? if not, there must be an
> error in the pull database on sources. you can copy it
> by hand with
> 9fs sources && cp -x /n/sources/plan9/sys/src/cmd/ip/pptpd.c
> /sys/src/cmd/ip/
Erik
> I'm having the same exact issue with a July 19th iso.
>
>>> this would be expected due to the pull which sets the mtimes of
>>> new files to be older than the .8s. try "mk clean" before proceeding.
>> So, now in /sys/src I do
>> mk cleanok,
>> mk allfails with
>>
9,
>> Something not quite right with my system??? It's from the plan9 iso
>> dated June 26th..
I'm having the same exact issue with a July 19th iso.
>> this would be expected due to the pull which sets the mtimes of
>> new files to be older than the .8s. try "mk clean" before proceeding.
> So,
>> by "work" you mean not generate an out-of-range
>> memory access nor not produce unexpected values?
>>
>> - erik
>
> i meant "pass muster", which i thought was the sense originally
> intended (ie, link without diagnostic) but i see now that wasn't intended.
> sorry.
>
> anyhow, that's why it
>> not exactly. it will work on most Unix systems and
>> on Plan 9 without -T because nothing checks
>> external types across object module boundaries. the linker/loader in both
>> systems
>> will allocate in BSS the largest size seen for a given symbol,
>> so it doesn't matter whether int == lon
erik quanstrom wrote:
Ok. I pulled and remade fossil which got over that error. But now I do
mk 'CONF=pcf' and get
size 9pcf
links: incompatible type signitures ..(for a whole load of init
files ie tcpinit, udpinit etc)
and then
mk: 8c -FTVv '-DKERNDATE='`{date ... : exit status=rc
> not exactly. it will work on most Unix systems and
> on Plan 9 without -T because nothing checks
> external types across object module boundaries. the linker/loader in both
> systems
> will allocate in BSS the largest size seen for a given symbol,
> so it doesn't matter whether int == long or n
> it will work perfectly if the -T flag is not
> given (since there is a deep assumption
> in plan 9 that int == long). but i the
not exactly. it will work on most Unix systems and
on Plan 9 without -T because nothing checks
external types across object module boundaries. the linker/loader in bo
> this would be expected due to the pull which sets the mtimes of
> new files to be older than the .8s. try "mk clean" before proceeding.
i should explain that type signatures are 32-bit
signatures in .$O files that define the type of
external symbols. the c compiler sets the type
signature to z
> Ok. I pulled and remade fossil which got over that error. But now I do
> mk 'CONF=pcf' and get
>
> size 9pcf
> links: incompatible type signitures ..(for a whole load of init
> files ie tcpinit, udpinit etc)
>
> and then
>
> mk: 8c -FTVv '-DKERNDATE='`{date ... : exit status=rc 1887:
erik quanstrom wrote:
I am having trouble building a new kernel for a terminal.
I do
mk 'CONF=pcf'
and I get the error
mk: don't know how to make '/386/bin/fossil/fossil' in directory
/sys/src/9/pc
does /386/bin/fossil/fossil exist? if not, it's a little
worrying that it does
Thank you both for your infromative replies.
A 'mk all' in /sys/src/cmd gave errors so I am doing a pull now
Bob
> I am having trouble building a new kernel for a terminal.
> I do
>mk 'CONF=pcf'
> and I get the error
>
> mk: don't know how to make '/386/bin/fossil/fossil' in directory
> /sys/src/9/pc
does /386/bin/fossil/fossil exist? if not, it's a little
worrying that it doesn't. perhaps th
The kernel mkfiles don't know how to build dependencies from
the cmd tree. The mk you're doing knows fossil is missing or out
of date, but not how to do anything about it. Build it yourself. I
mk all of /sys/src/cmd to be safe, but you could just hit the list
you need for your kernel (whatever file
Hi all,
I am having trouble building a new kernel for a terminal.
I do
mk 'CONF=pcf'
and I get the error
mk: don't know how to make '/386/bin/fossil/fossil' in directory
/sys/src/9/pc
A
mk 'CONF=pc'
works fine.
I am hoping this is some simple newbie mistake.
Thanks
Bob
22 matches
Mail list logo
