ipcop-devel Mailing List for IPCop Firewall

Bugs item #2814920, was opened at 2009-06-30 20:58
Message generated for change (Tracker Item Submitted) made by gringotumadre
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=2814920&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: 1.4.21
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Santiago Piccinini (gringotumadre)
Assigned to: Nobody/Anonymous (nobody)
Summary: port forwarding not working with external alias

Initial Comment:
Port forwarding isn't working with external aliases. It only works with principal ip.

This problem is not present in version 1.4.20.

Always using the web interface.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=2814920&group_id=40604

I've successfully completed a full build using Fedora core 11 and the latest
SVN.   I started with a ./make.sh gettoolchain before I built anything
(since I'm on a x86_64 system).  Nothing special.  I'll burn a CD and look
at the install and let you know how it goes.

Eric Oberlander wrote:


> Thanks Gilles, that patch worked on linux-headers, and the toolchain
> build continued until it reached coreutils when it stopped with:
> 
> make[1]: Leaving directory
> `/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/coreutils-6.12'
> # su is not installed (because suid root)
> # install under a different name to run non-root tests later
> cd /home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/coreutils-6.12
> && cp -v src/su /tools/bin/su-tools
> `src/su' -> `/tools/bin/su-tools'
> cp: cannot create regular file `/tools/bin/su-tools': No such file or directory
> make: *** [/home/eric/ipcop/ipcop/trunk/log_i486/01_toolchain/coreutils-6.12]
> Error 1
> 
> I get the same error building the toolchain on Ubuntu 8.04. A problem with sudo?

Sort of I guess.
I've hit the same error, but have not found the time to look at details yet.


Olaf

-- 

A weizen a day helps keep the doctor away.

> This is related to a glibc-2.10 change.
> Try with this patch
> http://patchwork.kernel.org/patch/11166/
>
> We probably should apply the patch in both linux-headers and linux stages to be
> able to build the toolchain under glibc-2.10.
> I don't know if this sort of change qualify for linux-2.6.27_stable?
>
> Gilles

Thanks Gilles, that patch worked on linux-headers, and the toolchain
build continued until it reached coreutils when it stopped with:

make[1]: Leaving directory
`/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/coreutils-6.12'
# su is not installed (because suid root)
# install under a different name to run non-root tests later
cd /home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/coreutils-6.12
&& cp -v src/su /tools/bin/su-tools
`src/su' -> `/tools/bin/su-tools'
cp: cannot create regular file `/tools/bin/su-tools': No such file or directory
make: *** [/home/eric/ipcop/ipcop/trunk/log_i486/01_toolchain/coreutils-6.12]
Error 1

I get the same error building the toolchain on Ubuntu 8.04. A problem with sudo?

Sorry to be the messenger with bad news again :(

Eric

Selon Eric Oberlander <eri...@gm...>:

> Gilles
>
> I added the glibc-static package and was able to get past the first
> error in linux32.
>
> Unfortunately, the build only gets as far as linux-headers before the
> next error, which is:
>
> cd /home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux-2.6.27-headers
> && make headers_check
> make[1]: Entering directory
> `/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux-2.6.27-headers'
>   CHK     include/linux/version.h
>   UPD     include/linux/version.h
>   HOSTCC  scripts/basic/fixdep
>   HOSTCC  scripts/basic/docproc
>   HOSTCC  scripts/unifdef
> scripts/unifdef.c:209: error: conflicting types for 'getline'
> /usr/include/stdio.h:655: error: previous declaration of 'getline' was here
> make[2]: *** [scripts/unifdef] Error 1
> make[1]: *** [__headers] Error 2
> make[1]: Leaving directory
> `/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux-2.6.27-headers'
> make: ***
> [/home/eric/ipcop/ipcop/trunk/log_i486/01_toolchain/linux-headers-2.6.27.8]
> Error 2
>
> Am currently trying a clean rebuild to double check this.
>
> Eric
>
This is related to a glibc-2.10 change.
Try with this patch
http://patchwork.kernel.org/patch/11166/

We probably should apply the patch in both linux-headers and linux stages to be
able to build the toolchain under glibc-2.10.
I don't know if this sort of change qualify for linux-2.6.27_stable?

Gilles

Gilles

I added the glibc-static package and was able to get past the first
error in linux32.

Unfortunately, the build only gets as far as linux-headers before the
next error, which is:

cd /home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux-2.6.27-headers
&& make headers_check
make[1]: Entering directory
`/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux-2.6.27-headers'
  CHK     include/linux/version.h
  UPD     include/linux/version.h
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/docproc
  HOSTCC  scripts/unifdef
scripts/unifdef.c:209: error: conflicting types for 'getline'
/usr/include/stdio.h:655: error: previous declaration of 'getline' was here
make[2]: *** [scripts/unifdef] Error 1
make[1]: *** [__headers] Error 2
make[1]: Leaving directory
`/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux-2.6.27-headers'
make: *** [/home/eric/ipcop/ipcop/trunk/log_i486/01_toolchain/linux-headers-2.6.27.8]
Error 2

Am currently trying a clean rebuild to double check this.

Eric

2009/6/29 Gilles Espinasse <g....@fr...>:
> Once we know what to search on google, that's easy.
> https://fcp.surfsite.org/modules/newbb/viewtopic.php?topic_id=68420&forum=11
>
> There is a glibc-static package on Fedora.
>
> We should add a test if /usr/lib/libc.a exist on toolchain
> prerequisites.
>
> Gilles

I just found something similar on a Fedora mailing list where they
discussed splitting the static libs out of glibc-devel package...

Thanks Ivan & Gilles

Eric

----- "Ivan Kabaivanov" <ch...@ya...> a écrit :

> Eric Oberlander wrote:
> > Just a warning, in case you were thinking of upgrading from Fedora
> 10
> > to 11, the 1.9.5 toolchain build now fails in the first lfs script
> -
> > linux32, with the error message:
> >
> > patching file Makefile
> > cd
> /home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig
> > && make CFLAGS="-static -g -Wall -O2"
> > make[1]: Entering directory
> >
> `/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig'
> > gcc -static -g -Wall -O2 -o linux32 linux32.c
> > /usr/bin/ld: cannot find -lc
> >   
> 
> 
> Hi Eric,
> 
> linux32 is built statically, so I'm guessing you're missing
> /usr/lib/libc.a.
> 
> Follow Gilles' advice to see if you have it.  If you do miss it,
> there's 
> probably a RPM package you can install.  Not using a RPM-based distro
> 
> myself, I don't have a clue what that package might be.
> 
> IvanK.
> 
> 
> 
> > collect2: ld returned 1 exit status
> > make[1]: *** [linux32] Error 1
> > make[1]: Leaving directory
> >
> `/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig'
> > make: ***
> [/home/eric/ipcop/ipcop/trunk/log_i486/01_toolchain/linux32_1.orig]
> > Error 2
> >
> > Regards
> >
> > Eric
> >
Once we know what to search on google, that's easy.
https://fcp.surfsite.org/modules/newbb/viewtopic.php?topic_id=68420&forum=11

There is a glibc-static package on Fedora.

We should add a test if /usr/lib/libc.a exist on toolchain
prerequisites.

Gilles

Eric Oberlander wrote:
> Just a warning, in case you were thinking of upgrading from Fedora 10
> to 11, the 1.9.5 toolchain build now fails in the first lfs script -
> linux32, with the error message:
>
> patching file Makefile
> cd /home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig
> && make CFLAGS="-static -g -Wall -O2"
> make[1]: Entering directory
> `/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig'
> gcc -static -g -Wall -O2 -o linux32 linux32.c
> /usr/bin/ld: cannot find -lc
>   


Hi Eric,

linux32 is built statically, so I'm guessing you're missing /usr/lib/libc.a.

Follow Gilles' advice to see if you have it.  If you do miss it, there's 
probably a RPM package you can install.  Not using a RPM-based distro 
myself, I don't have a clue what that package might be.

IvanK.



> collect2: ld returned 1 exit status
> make[1]: *** [linux32] Error 1
> make[1]: Leaving directory
> `/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig'
> make: *** [/home/eric/ipcop/ipcop/trunk/log_i486/01_toolchain/linux32_1.orig]
> Error 2
>
> Regards
>
> Eric
>
> ------------------------------------------------------------------------------
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>   

----- Original Message ----- 
From: "Eric Oberlander" <eri...@gm...>
To: "IPCop devel" <ipc...@li...>
Sent: Sunday, June 28, 2009 11:02 AM
Subject: [IPCop-devel] Building 1.9.5 toolchain on Fedora 11


> Just a warning, in case you were thinking of upgrading from Fedora 10
> to 11, the 1.9.5 toolchain build now fails in the first lfs script -
> linux32, with the error message:
>
> patching file Makefile
> cd /home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig
> && make CFLAGS="-static -g -Wall -O2"
> make[1]: Entering directory
> `/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig'
> gcc -static -g -Wall -O2 -o linux32 linux32.c
> /usr/bin/ld: cannot find -lc
> collect2: ld returned 1 exit status
> make[1]: *** [linux32] Error 1
> make[1]: Leaving directory
> `/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig'
> make: ***
[/home/eric/ipcop/ipcop/trunk/log_i486/01_toolchain/linux32_1.orig]
> Error 2
>
> Regards
>
> Eric
>
could you give the result of
gcc  -print-search-dirs
find /usr/lib* -name libc.*

Usually libc is found in
/usr/lib/libc.so
/usr/lib/libc.a

    Gilles

On Sat, 27 Jun 2009 21:03:28 +0200
Michael Rasmussen <mi...@mi...> wrote:

> On Sat, 27 Jun 2009 18:42:15 +0200
> Michael Rasmussen <mi...@mi...> wrote:
> 
> > What to do next?
> > 
> I have now started a build on a Debian Lenny i686 using exactly the
> same approach as on the Sid x86_64. This seems to work as expected. When
> the build has finished I will try replicating this build on a Debian
> Lenny x86_64. It could be a problem related to the toolchain which,
> IMHO, should be build on an x86_64 machine for use on x86_64 builds.
> 
Status:
Lenny i686: IPCop builds with the available toolchain
Lenny x86_64: IPCop builds with the available toolchain

Why it does not build on Sid is still a mystery.


-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
You may be infinitely smaller than some things, but you're infinitely
larger than others.

Just a warning, in case you were thinking of upgrading from Fedora 10
to 11, the 1.9.5 toolchain build now fails in the first lfs script -
linux32, with the error message:

patching file Makefile
cd /home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig
&& make CFLAGS="-static -g -Wall -O2"
make[1]: Entering directory
`/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig'
gcc -static -g -Wall -O2 -o linux32 linux32.c
/usr/bin/ld: cannot find -lc
collect2: ld returned 1 exit status
make[1]: *** [linux32] Error 1
make[1]: Leaving directory
`/home/eric/ipcop/ipcop/trunk/build_i486/ipcop/usr/src/linux32-1.orig'
make: *** [/home/eric/ipcop/ipcop/trunk/log_i486/01_toolchain/linux32_1.orig]
Error 2

Regards

Eric

Hello,

i am the maintainer of OpenFWTK project (http://openfwtk.sf.net/), a set of application layer proxies for Unix. Some oldtimers may remember TIS FWTK, so my project is, like, FWTK on steroids (and it is BSD-licensed). I guess it should build smoothly with IPCop toolchain, though i haven't tried yet.

Despite little recent activity seen in the CVS, i have some major changes developed separately and not commited yet - and i am going to commit it really soon. Those include SSL MITM inspection and ICAP filtering (and yes, it works together), https only at the moment, but other protocols will be added later.

Unlike most opensource firewall projects it is *not* a bunch of poorly integrated random components under web interfaces which conceals lack of true consistency; instead it is quite an opposite thing: consistent framework with *no* fancy frontend.. which scares away most potential users.

I am willing to provide any assistance to help to integrate OpenFWTK into IPCop.. except doing that by myself as am quite busy with core development :-(

Are you interested?

On Sat, 27 Jun 2009 21:03:28 +0200
Michael Rasmussen <mi...@mi...> wrote:

> Lenny x86_64. It could be a problem related to the toolchain which,
> IMHO, should be build on an x86_64 machine for use on x86_64 builds.
> 
What distribution and version of that distribution are you using for
building the toolchain?

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
You may be infinitely smaller than some things, but you're infinitely
larger than others.

On Sat, 27 Jun 2009 18:42:15 +0200
Michael Rasmussen <mi...@mi...> wrote:

> What to do next?
> 
I have now started a build on a Debian Lenny i686 using exactly the
same approach as on the Sid x86_64. This seems to work as expected. When
the build has finished I will try replicating this build on a Debian
Lenny x86_64. It could be a problem related to the toolchain which,
IMHO, should be build on an x86_64 machine for use on x86_64 builds.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
You may be infinitely smaller than some things, but you're infinitely
larger than others.

On Sat, 27 Jun 2009 20:44:34 +0200
"Gilles Espinasse" <g....@fr...> wrote:

> 
> Could you run
> 
> [chroot-i486] root:/$ chown --version
> chown (GNU coreutils) 6.12
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> Written by David MacKenzie and Jim Meyering.
> 
> [chroot-i486] root:/$ echo $PATH
> /tools_i486/usr/bin:/bin:/usr/bin:/sbin:/usr/sbin:/tools_i486/bin:/usr/i486-
> linux/bin
> 
[chroot-i486] root:/$ chown --version
chown (GNU coreutils) 6.12
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html> This is free software: you are free
to change and redistribute it. There is NO WARRANTY, to the extent
permitted by law.

Written by David MacKenzie and Jim Meyering.
[chroot-i486] root:/$ echo $PATH
/tools_i486/usr/bin:/bin:/usr/bin:/sbin:/usr/sbin:/tools_i486/bin:/usr/i486-linux/bin


-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
You may be infinitely smaller than some things, but you're infinitely
larger than others.

----- Original Message ----- 
From: "Michael Rasmussen" <mi...@mi...>
To: <ipc...@li...>
Sent: Saturday, June 27, 2009 8:25 PM
Subject: Re: [IPCop-devel] [2.0] fails to build


> [chroot-i486] root:/$ ls -l home/
> total 0
> drwxr-xr-x 2 root root 6 Jun 27 18:16 nobody
>
> [chroot-i486] root:/$ chown -R nobody:nobody /home/nobody
> chown: changing ownership of `/home/nobody': Invalid argument
> [chroot-i486] root:/$ chown -R 99:99 /home/nobody
> chown: changing ownership of `/home/nobody': Invalid argument

Could you run

[chroot-i486] root:/$ chown --version
chown (GNU coreutils) 6.12
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie and Jim Meyering.

[chroot-i486] root:/$ echo $PATH
/tools_i486/usr/bin:/bin:/usr/bin:/sbin:/usr/sbin:/tools_i486/bin:/usr/i486-
linux/bin

    Gilles

----- Original Message ----- 
From: "Michael Rasmussen" <mi...@mi...>
To: "Gilles Espinasse" <g....@fr...>
Sent: Saturday, June 27, 2009 8:15 PM
Subject: Re: [IPCop-devel] [2.0] fails to build

>> chown -R 99:99 /home/nobody
>>
>$ grep nobody /etc/passwd
>nobody:x:65534:65534:nobody:/nonexistent:/bin/sh
>
>Still use 99:99 and not 65534:65534 ?
>
Yes
I speak of etc/passwd file inside the chroot.
At the point you are, you should be able to enter the chroot with ./make.sh
shell and
grep nobody /etc/passwd

We have nothing to do for users existing out of our chroot.

    Gilles

On Sat, 27 Jun 2009 19:58:52 +0200
"Gilles Espinasse" <g....@fr...> wrote:

> If the line CHMOD look good, clean the build and retry replacing in stage2
> by
> chown -R 99:99 /home/nobody
> 
If I do the following:
$ make.sh shell

Confirm we are root:
[chroot-i486] root:/$ whoami
root

$ cat /etc/passwd 
root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/bin/false
daemon:x:2:2:daemon:/sbin:/bin/false
mail:x:8:12:mail:/var/spool/mail:/bin/false
squid:x:23:23:ftp:/var/spool/squid:/bin/false
ntp:x:38:38::/etc/ntp:/bin/false
sshd:x:74:74:sshd:/var/empty:/bin/false
nobody:x:99:99:Nobody:/home/nobody:/bin/false
logwatch:x:102:102::/var/log/logwatch:/bin/false
dnsmasq:x:103:103::/:/bin/false
cron:x:104:104::/:/bin/false
syslogd:x:105:105::/var/empty:/bin/false
klogd:x:106:106::/var/empty:/bin/false
backup:x:107:107::/var/empty:/bin/false

[chroot-i486] root:/$ ls -l home/
total 0
drwxr-xr-x 2 root root 6 Jun 27 18:16 nobody

[chroot-i486] root:/$ chown -R nobody:nobody /home/nobody 
chown: changing ownership of `/home/nobody': Invalid argument
[chroot-i486] root:/$ chown -R 99:99 /home/nobody
chown: changing ownership of `/home/nobody': Invalid argument



-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
You may be infinitely smaller than some things, but you're infinitely
larger than others.

----- Original Message ----- 
From: "Michael Rasmussen" <mi...@mi...>
To: <ipc...@li...>
Sent: Saturday, June 27, 2009 6:53 PM
Subject: Re: [IPCop-devel] [2.0] fails to build

I have commited the fix for 'test_i486 does not exist' error.

> > Last 5 lines in log_i486/_build_02_base.log
> > # Nobody user
> > mkdir -p /home/nobody
> > chown -R nobody:nobody /home/nobody
> > chown: changing ownership of `/home/nobody': Invalid argument
> > make: *** [/usr/src/log_i486/02_base/stage2] Error 1
> Forgot one important info:
> /home is owned by root so /home/nobody cannot be created by the build
script.

I don't think that's the real problem.
I am building as non-root without issue.

CHMOD alias should give you the right to do that operation.
Or your CHMOD alias line is bad

Line should be
Cmnd_Alias CHMOD = /bin/chmod [0-9]*
/home/mir/Projekter/c/ipcop/build_i486/ipcop/*

Invalid argument make me think at a problem with owner nobody not know even
if /etc/passwd has been installed a few lines before.

If the line CHMOD look good, clean the build and retry replacing in stage2
by
chown -R 99:99 /home/nobody

If that fix the problem, then the next question will be to determine what
make this problem happen.

    Gilles

On Sat, 27 Jun 2009 18:42:15 +0200
Michael Rasmussen <mi...@mi...> wrote:

> Last 5 lines in log_i486/_build_02_base.log
> # Nobody user
> mkdir -p /home/nobody
> chown -R nobody:nobody /home/nobody
> chown: changing ownership of `/home/nobody': Invalid argument
> make: *** [/usr/src/log_i486/02_base/stage2] Error 1
Forgot one important info:
/home is owned by root so /home/nobody cannot be created by the build
script.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
You may be infinitely smaller than some things, but you're infinitely
larger than others.

On Sat, 27 Jun 2009 11:49:09 +0100
Eric Oberlander <eri...@gm...> wrote:

> 
> No Olaf, I need all the help I can get :)
> 
Ok, here comes?

Build environment:
Linux 2.6.30-1-amd64 #1 SMP x86_64 GNU/Linux
Debian Sid: latest patch level
Building toolchain cannot be done since glib-2.2.5 is not available so
fetching toolchain with make.sh gettoolchain

make.sh prefetch completed without errors

$ ./make.sh build
*** IPCop build .config not found. Using defaults
*** Checking for host prerequisites
Checking if we're using bash [ DONE ] 
Checking if we're running as non-root user [ DONE ]
Checking if we have sudo [ DONE ]
Checking if sudo is configured [ DONE ]
Building IPCop-1.9.5 for i486 on i486
*** Setting up our build environment
Setting our nice level to 10 [ DONE ]
mount: special device /home/mir/Projekter/c/ipcop/test_i486 does not
exist
Running compilation tests : no [ INFO ]
Stage toolchain already built (found log_i486/01_toolchain/strip)
[ DONE ]
*** Building base
options           version     time (sec)    status
stage2        [   svn-2450 ] [         7 ] [ FAIL ]

ERROR: Building stage2 [ FAIL ]
Check /home/mir/Projekter/c/ipcop/log_i486/_build_02_base.log for
errors if applicable

Last 5 lines in log_i486/_build_02_base.log
# Nobody user
mkdir -p /home/nobody
chown -R nobody:nobody /home/nobody
chown: changing ownership of `/home/nobody': Invalid argument
make: *** [/usr/src/log_i486/02_base/stage2] Error 1

What to do next?

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
You may be infinitely smaller than some things, but you're infinitely
larger than others.

----- Original Message ----- 
From: "Geo" <cap...@gm...>
To: <ipc...@li...>
Sent: Saturday, June 27, 2009 2:04 PM
Subject: Re: [IPCop-devel] [2.0]Add mounting /sys in make.sh


> On Saturday 27 June 2009 11:49:09 Eric Oberlander wrote:
> > 2009/6/27 Olaf Westrik <wei...@ip...>:
> > > Gilles Espinasse wrote:
> > >> Not hard to add the changes in make.sh.
> > >> But that will break existing configuration building as non-root.
> > >> I have added a specific test, so you will be warned and the entire
new
> > >> text to be copied in sudoer is displayed.
> > >> Does it look ok to you?
> > >
> > > Looks OK to me.
> > >
> > > OTOH I am not too worried about such sudoer changes without warnings.
> > > There are not that many people building and I would expect those that
do
> > > to find and solve the problem if the build breaks because of missing
(or
> > > wrong) sudoer.
> > >
> > >
> > > Olaf
> >
> > No Olaf, I need all the help I can get :)
> >
> > Eric
> >
> Eric,
>  I'm with you the more info is available to the "less gifted" (like me )
the
> better the messages generation can be removed when it all works perfectly.
>
If you build as non-root, and the new 'mount --bind /sys' is not configured,
you have the entire configuration to be copied displayed.
That's the same sort of message as at the first attempt to run make.sh.

    Gilles

On Saturday 27 June 2009 11:49:09 Eric Oberlander wrote:
> 2009/6/27 Olaf Westrik <wei...@ip...>:
> > Gilles Espinasse wrote:
> >> Not hard to add the changes in make.sh.
> >> But that will break existing configuration building as non-root.
> >> I have added a specific test, so you will be warned and the entire new
> >> text to be copied in sudoer is displayed.
> >> Does it look ok to you?
> >
> > Looks OK to me.
> >
> > OTOH I am not too worried about such sudoer changes without warnings.
> > There are not that many people building and I would expect those that do
> > to find and solve the problem if the build breaks because of missing (or
> > wrong) sudoer.
> >
> >
> > Olaf
>
> No Olaf, I need all the help I can get :)
>
> Eric
>
Eric,
 I'm with you the more info is available to the "less gifted" (like me ) the 
better the messages generation can be removed when it all works perfectly.



-- 
TTFN
   Caparo

2009/6/27 Olaf Westrik <wei...@ip...>:
> Gilles Espinasse wrote:
>
>> Not hard to add the changes in make.sh.
>> But that will break existing configuration building as non-root.
>> I have added a specific test, so you will be warned and the entire new text
>> to be copied in sudoer is displayed.
>> Does it look ok to you?
>
> Looks OK to me.
>
> OTOH I am not too worried about such sudoer changes without warnings.
> There are not that many people building and I would expect those that do
> to find and solve the problem if the build breaks because of missing (or
> wrong) sudoer.
>
>
> Olaf

No Olaf, I need all the help I can get :)

Eric