2015-06-22 17:03 GMT+02:00 Luigi Rizzo :
>
>
> On Monday, June 22, 2015, Stefano Garzarella
> wrote:
>
>> Hi all,
>> I'm using picobsd on FreeBSD-head (r284697) to build a picobsd image with
>> gcc, but I have the following errors during the init phase
&g
On Monday, June 22, 2015, Stefano Garzarella
wrote:
> Hi all,
> I'm using picobsd on FreeBSD-head (r284697) to build a picobsd image with
> gcc, but I have the following errors during the init phase
> (release/picobsd/build/picobsd --init):
>
> In file included from
&g
Hi all,
I'm using picobsd on FreeBSD-head (r284697) to build a picobsd image with
gcc, but I have the following errors during the init phase
(release/picobsd/build/picobsd --init):
In file included from
/usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/lz/lz_encoder
On Wed, Jan 4, 2012 at 9:50 PM, Adrian Chadd wrote:
> On 4 January 2012 20:53, Jacques Fourie wrote:
>> I've posted a diff to -arm about 2 years ago that I used to
>> cross-build arm picobsd images for a gumstix platform on a i386 host.
>> I don't know if the diff
On 4 January 2012 20:53, Jacques Fourie wrote:
> I've posted a diff to -arm about 2 years ago that I used to
> cross-build arm picobsd images for a gumstix platform on a i386 host.
> I don't know if the diff will apply cleanly anymore but here it is in
> anyway.
Hi,
I&
I've posted a diff to -arm about 2 years ago that I used to
cross-build arm picobsd images for a gumstix platform on a i386 host.
I don't know if the diff will apply cleanly anymore but here it is in
anyway.
--- a/release/picobsd/build/Makefile.conf
+++ b/release/picobsd/build/Mak
On 12/20/11 18:19, Olivier Cochard-Labbé wrote:
> On Mon, Dec 19, 2011 at 11:45 PM, Luigi Rizzo wrote:
>> On a related topic, does anyone have experience on cross-building
>> nanobsd images ?
> Hi Luigi,
>
> I using "little" cross-building nanobsd images (i386 on amd64 and vice versa).
> All my pa
Hi,
I used to build a few ARM images (on amd64 host) using
/usr/src/tools/tools/nanobsd/gateworks/
and regularly i386 images (on amd64 host too) using
/usr/src/tools/tools/nanobsd/pcengines/
Bye/2
---
Michael Reifenberger
mich...@reifenberger.com
http://www.Reifenberger.com
_
2011/12/20 Olivier Cochard-Labbé :
> On Mon, Dec 19, 2011 at 11:45 PM, Luigi Rizzo wrote:
>>
>> On a related topic, does anyone have experience on cross-building
>> nanobsd images ?
Hello Mr. Olivier!
> I using "little" cross-building nanobsd images (i386 on amd64 and vice versa).
> All my patch
On Mon, Dec 19, 2011 at 11:45 PM, Luigi Rizzo wrote:
>
> On a related topic, does anyone have experience on cross-building
> nanobsd images ?
Hi Luigi,
I using "little" cross-building nanobsd images (i386 on amd64 and vice versa).
All my patchs for nanobsd are available on BSD Router Project
(ht
Hi,
recently I have tried to build picobsd image for a different
architecture than the current one, with only partial success.
In particular, three weeks ago i committed some changes to the
picobsd script so now i can build working amd64 images on amd64.
However when i try a cross build (e.g
It appears that a recent change to src/Makefile.inc1 has broken the
build of PicoBSD when I attempt to build CURRENT on FreeBSD-4.8
host:
*** PICO_OBJ is /home/possum/u0/pavlin/freebsd_src/../usr/obj-pico/picobsd/pim
make: no target to make.
"/scratch/possum/u1/pavlin/FreeBSD/HEAD.cv
Can someone help me, I want to build a picobsd floppy.
Command: release/picobsd/build/picobsd bridge
Error: suffix or operands invalid for 'shr'
I think the complain is about the fillkptphys(prot) macro
in sys/i386/i386/locore.s
I cvsuped current yesterday
I havent build pico
> Is there any particular reason for using -current for that? The
> problem is that -current is in horrible state now (gcc 3.1, KSE-III
> and so on), so that I'd suggest to use -stable branch or -current
> sources just before gcc 3.1 import.
>
Well there are two things going on. My employer wan
Hi,
At 22:55 1/7/02, George V. Neville-Neil wrote:
> When picobsd goes to build the libraries etc. it chokes on the csu
>stuff: [etc]
First, I'd echo what someone else said about avoiding -current right now.
Second, you may have better luck if you buildworld before attempting a
pi
>
> Hey Folks,
>
> So now I'm working somewhere that we're trying to use Picobsd on the
> Soekris boards (www.soekris.com). Right now there is a build problem I'm
> trying to
> solve. When picobsd goes to build the libraries etc. it chokes on the csu
> stu
Hey Folks,
So now I'm working somewhere that we're trying to use Picobsd on the
Soekris boards (www.soekris.com). Right now there is a build problem I'm
trying to
solve. When picobsd goes to build the libraries etc. it chokes on the csu
stuff:
CC="cc" MKDEP
> This still doesn't answer my question -- how can I reproduce the problem?
>
> cd /foo/bar
> make grrr
>
> Something like that...
Whoops, sorry.
To reproduce this do:
cd /usr/src
./release/picobsd/build/picobsd --src /usr/src --init
yes, I know that --src is unnec
On Wed, Feb 27, 2002 at 09:49:28AM -0800, George V. Neville-Neil wrote:
> > You'll have to pay some money if you need a 24-hour responsiveness. :-)
> >
>
> The check is in the mail ;-)
>
> > What src/release PicoBSD script should I try to run to reproduce this?
> You'll have to pay some money if you need a 24-hour responsiveness. :-)
>
The check is in the mail ;-)
> What src/release PicoBSD script should I try to run to reproduce this?
>
-CURRENT as of Monday.
Things work fine in a checkout from 20 Feb 2002 and that's what
d.lib.mk,v 1.55 -- we
> no longer have users of it.
>
> This change was made by "ru." Alas this breaks the picobsd build since the
> statically built libraries need some way to know to get their includes from the
> directory you're building in. This does not affect a gener
IR}/usr/include magic in bsd.prog.mk
and bsd.lib.mk. Finish the removal of LDDESTDIR in bsd.lib.mk,v 1.55 -- we
no longer have users of it.
This change was made by "ru." Alas this breaks the picobsd build since the
statically built libraries need some way to know to get their includes
Hi Folks,
I'm now mirroring the CVS repository locally (with cvsup)
and then checking out the head of the tree with cvs co src to get
at -CURRENT. I'm trying to work with picobsd but I get the following
on the latest (24 Feb 2002, 22:25 Pacific Time) stuff when I just try
to
On Thu, 1 Nov 2001, Luigi Rizzo wrote:
> luigi 2001/11/01 08:52:35 PST
>
> Modified files:
> release/picobsd/mfs_tree/etc termcap
> Log:
> Add entries for "dumb" and "dialup" terminals, as the shell in HEAD
> refuses to start if
> Luigi, you cannot run dead air. Makefile.conf only handles that
> if the variable does not exist, not if the variable is empty.
ok my fault :)
luigi
> > > CONFIG=${CONFIG:-config}
> >
> > cheers
> > luigi
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubs
On Fri, Jun 22, 2001 at 12:26:39PM +0200, Luigi Rizzo wrote:
> > On line 336 of the script, you export dead air, resulting in
>
> and Makefile.conf handles that in a way
> similar to the one you show below.
Luigi, you cannot run dead air. Makefile.conf only handles that
if the variable does not
> On line 336 of the script, you export dead air, resulting in
and Makefile.conf handles that in a way
similar to the one you show below.
> CONFIG=${CONFIG:-config}
cheers
luigi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
On Thu, Jun 21, 2001 at 06:18:47PM +0200, Luigi Rizzo wrote:
> would you mind resubmitting a patch for the version of
> "picobsd" i committed this morning, also keeping in mind the
> following:
That patch was based off of your 8:49AM (revision 1.7) commit
this morning.
> *
> * Do we want NO_SWAPPING on or off in PicoBSD?
> I understand that many PicoBSD devices do not have swapspace.
> However, my understand of -current is that we do require
> swapping to work well.
given that in the vast majority of cases you don't have a choice..
On Thu, Jun 21, 2001 at 06:18:47PM +0200, Luigi Rizzo scribbled:
| would you mind resubmitting a patch for the version of
| "picobsd" i committed this morning, also keeping in mind the
| following:
|
| * it would be better to define a variable, say MD, which holds
| the string &
Hi,
would you mind resubmitting a patch for the version of
"picobsd" i committed this morning, also keeping in mind the
following:
* it would be better to define a variable, say MD, which holds
the string "vn" or "md", and is used in accessing the memory
devi
gt; | vnconfig has changed to mdconfig in -current, but the
> | > | picobsd build script still references vnconfig, also
> | > | CONFIG isn't defined anywhere in the script, resulting
> | > | in the process dying when it tries to configure the
> | > | kernel, a couple
On Thu, Jun 21, 2001 at 11:02:02AM -0400, Omachonu Ogali scribbled:
| On Thu, Jun 21, 2001 at 10:03:27AM -0500, Michael C . Wu wrote:
| > On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled:
| > | vnconfig has changed to mdconfig in -current, but the
| > | picobsd bui
On Thu, Jun 21, 2001 at 10:03:27AM -0500, Michael C . Wu wrote:
> On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled:
> | vnconfig has changed to mdconfig in -current, but the
> | picobsd build script still references vnconfig, also
> | CONFIG isn't defined anywh
On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled:
| vnconfig has changed to mdconfig in -current, but the
| picobsd build script still references vnconfig, also
| CONFIG isn't defined anywhere in the script, resulting
| in the process dying when it tries to configur
vnconfig has changed to mdconfig in -current, but the
picobsd build script still references vnconfig, also
CONFIG isn't defined anywhere in the script, resulting
in the process dying when it tries to configure the
kernel, a couple of punctuation mods here and there,
and dumped the &quo
Hi,
I suspect it is more likely that i get feedback from people on -current,
which is why this email is addressed there. I am Bcc-ing to -small in
case the people there are interested too.
Basically, i would like to come up with some easy way to cross-build
picobsd images, embedding the relevant
The ready-made PICOBSD-diskimages all seems to be based on FreeBSD 3.x
I also doesn't seem to be able to make picobsd from current sources, althugh I didn't
try that hard.
Is picobsd stale?
Leif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current&
Ok, parts of PicoBSD are finally working again. I've managed to get dial,
isp, and net working again. The only ones left to check out are bridge and
install, I'm not sure about router, does that still exist or was that
replaced by bridge? Bridge is too big to fit on a floppy so I&#x
The following patch is for -CURRENT. It at least gets past that dumb
floppy loop. The problem I'm having is that after the scripts, nothing
else is done, it just sits there with "Welcome to PicoBSD". Any ideas?
To Luigi: I made the changes you asked for, disregard that pa
My router-box got hosed during a installworld, and I thought I had to reinstall using
picobsd, so I tried building a custom version with scsi-support.
It failed, the problem was related to libcrypt, if I remember correctly.
I havent got the exact details, because I succeded to boot in single
Thanks everybody for the responses.
Incidentally, df still produces the right output, the message
i was seeing was coming from vfs_conf.c trying to mount the root...
cheers
luigi
---+-
Luigi RIZZO, [EMAIL PROTE
On Mon, Feb 07, 2000 at 01:04:27PM +0100, Luigi Rizzo wrote:
> and the like. On a recent -current snap, this returns
>
> ufs:fd0a
>
> I used the previous behaviour in picobsd's rc to mount
> the file system from the boot device,
>
> set `df /` ; dev="/dev/$8"
> ech
On Mon, 7 Feb 2000, Luigi Rizzo wrote:
> on 3.4R, when booting, a
>
> df /
>
> would return the name of the boot device, something like
>
> fd0a
> wd0a...
>
> and the like. On a recent -current snap, this returns
>
> ufs:fd0a
This may be cause
> ufs:fd0a
> set `df /` ; dev="/dev/$8"
How about something like
IFS=': '; set `df /`; IFS=' '
dev="/dev/$9"
-- Richard
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
on 3.4R, when booting, a
df /
would return the name of the boot device, something like
fd0a
wd0a...
and the like. On a recent -current snap, this returns
ufs:fd0a
I used the previous behaviour in picobsd's rc to mount
the file syst
I'm trying to build a `net' PicoBSD on a -current system and am
running into problems that appear to be inside make(1) (and how it
imports/exports/treats MAKEFLAGS).
I thought I'd try to shrink things by stripping the ISDN and RADIUS
support out of ppp (amongst other things), but
Hello,
I'm committing an update of the PicoBSD code tree that should allow it to
build on -STABLE and take advantage of loader's new features.
Luigi Rizzo did the majority of the work, I debugged. I have use of this
code thus why I'm sponsoring this commit.
Significant
Thank to all for replies. It seems that today current finaly have fixed (pccard
works
without patches).
Hovewer, sysinstall (and PicoBSD) broken with following symptoms:
cc -O2 -march=pentium -mpentium -pipe -Wall -I/usr/src/release/sysinstall/../../
gnu/lib/libdialog -I/usr/src/release
49 matches
Mail list logo
