astlinux-devel — The AstLinux development environment, compilation, etc

Re: [Astlinux-devel] making unionfs partition autodetected

[Kristian K. <kri...@gm...>]

On Thu, Mar 20, 2008 at 10:26 AM, Darrick Hartman (lists)
<dha...@dj...> wrote:
> I'm trying to make implementation of unionfs easier by adding an
>  autodetection to the init script.  Kris has this setup for ASTKD using
>  the findfs utility and relying on file system labels.  The problem right
>  now, is findfs is not in the initrd which actually mounts the unionfs
>  partition.  Does anyone know of a good way to implement the
>  functionality of findfs to locate the partition labeled as "ASTURW" or
>  do we need to investigate adding  findfs to the initrd if we want to
>  implement this?
>  --
>  Darrick Hartman
>  DJH Solutions, LLC
>  http://www.djhsolutions.com
>  http://www.djhsolutions.com/wiki
>

Darrick,

  When I was working on this before that's the only solution I could
come up with - adding findfs to the initrd...

-- 
Kristian Kielhofner

[Astlinux-devel] making unionfs partition autodetected

[Darrick H. (lists) <dha...@dj...>]

I'm trying to make implementation of unionfs easier by adding an 
autodetection to the init script.  Kris has this setup for ASTKD using 
the findfs utility and relying on file system labels.  The problem right 
now, is findfs is not in the initrd which actually mounts the unionfs 
partition.  Does anyone know of a good way to implement the 
functionality of findfs to locate the partition labeled as "ASTURW" or 
do we need to investigate adding  findfs to the initrd if we want to 
implement this?
-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com
http://www.djhsolutions.com/wiki

Re: [Astlinux-devel] dst cache overflow

[Ingmar S. <is...@es...>]

Doing a software upgrade which solves all bugs and is not introducing 
any new bugs would be just amazing :-)

You have to balance. If an upgrade doesn't improve quality, you may not 
want to upgrade. However, if an upgrade is solving an urgent problem you 
may want to consider doing it although you know that there is a downside 
as well.

As I see that you are following the kernel mailing list, would 2.6.23 do 
any better than 2.6.24? Would that be an option?

Note: the Geode LX / CS5536 patches have been incorporated into 2.6.24 - 
   no patching required. However, you can achieve the same with 2.6.23 + 
patches. I am just making this note since I know that some people here 
are using PC Engines Alix or Soekris net5501.

regards,

Ingmar

Philip Prindeville wrote:
> Seems upgrading to Linux 2.6.24 won't solve all of our problems after all...
> 
> 
> ========
> 
> Date:	Mon, 17 Mar 2008 02:25:13 +0100
> From: Tobias Diedrich <ra...@td...>
> To: Herbert Xu <he...@go...>, lin...@vg...,
>         lin...@vg..., da...@co...
> Subject: Re: dst cache overflow
> Message-ID: <200...@ya...>
> 
> Hi all,
> 
> just a reminder, the server is now running 2.6.24 and the leak is
> still there.  I noticed there is a slab leak debug option and turned
> it on, results should be visible in a few days I guess.
> 
> Offenders: Slabs TCPv6, size_2048 and size_512 grow over time.
> 
> I also noticed that the machine stops responding to pings after some
> time, which seems to coincide with a slight increase in leak speed.
> 
> Interstingly IPv4 pings give out first, IPv6 pings continue to work a bit
> longer, but eventually fail too. (Because sixxs starts sending 'your
> tunnel is down!' mails I actually wrote a userspace pingd as a
> workaround...)
> 
> /proc/net/snmp seems to indicate the kernel thinks it is still
> sending ping replies.
> 
> HTH,
> 

Re: [Astlinux-devel] dst cache overflow

[Philip P. <phi...@re...>]

Seems upgrading to Linux 2.6.24 won't solve all of our problems after all...


========

Date:	Mon, 17 Mar 2008 02:25:13 +0100
From: Tobias Diedrich <ra...@td...>
To: Herbert Xu <he...@go...>, lin...@vg...,
        lin...@vg..., da...@co...
Subject: Re: dst cache overflow
Message-ID: <200...@ya...>

Hi all,

just a reminder, the server is now running 2.6.24 and the leak is
still there.  I noticed there is a slab leak debug option and turned
it on, results should be visible in a few days I guess.

Offenders: Slabs TCPv6, size_2048 and size_512 grow over time.

I also noticed that the machine stops responding to pings after some
time, which seems to coincide with a slight increase in leak speed.

Interstingly IPv4 pings give out first, IPv6 pings continue to work a bit
longer, but eventually fail too. (Because sixxs starts sending 'your
tunnel is down!' mails I actually wrote a userspace pingd as a
workaround...)

/proc/net/snmp seems to indicate the kernel thinks it is still
sending ping replies.

HTH,

-- 
Tobias						PGP: http://9ac7e0bc.uguu.de
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to maj...@vg...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [Astlinux-devel] isdn

[Darrick H. <dha...@dj...>]

Thanks Ingmar.  I'm copying this to the -devel list so we have it in the 
archives.

I would say we're really close to being ready to branch trunk to 0.6. 
I'd like to hold off until Digium releases Asterisk 1.4.19 (they're at 
RC2 atm), but otherwise, I think we're very close.

Thanks,

Darrick

Ingmar Schraub wrote:
> Hi Darrick,
> 
> I checked all recent news on mISDN and oslec. My decision for this 
> Astlinux release is to stick with mISDN version 1.1.7 which is already 
> in trunk.
> 
> Once we upgrade to a newer kernel (2.6.23+) we will also need to upgrade 
> mISDN.
> 
> There is a newer mISDN version available (1.1.7.2) but here I can't 
> apply the oslec patch. I don't think it is currently worth spending a 
> lot of time to adjust the patch I once created for adding oslec support, 
> because oslec support got added to the mISDN 1.2 branch.
> 
> Now, updating to 1.2 is not what I like to do right now. It's a 
> different animal and the coders have re-written a lot of code. I know 
> that what we have in the Astlinux trunk works and that's the best choice 
> for now.
> 
> Starting with kernel 2.6.23+ we have to make changes to mISDN as well 
> (the 1.1.7 version would not compile even with this kernel). So I have 
> some work ahead. But I won't start it before we switch to a newer kernel.
> 
> To summarize: we are currently good to go with the mISDN support we have 
> in trunk.
> 
> cheers, Ingmar
> 
> Darrick Hartman wrote:
>> Ingmar,
>>
>> How was CeBit?  They rarely hold conferences that are worth anything 
>> close to where I live (Chicago is probably the closest).
>>
>> Have you had a chance to see if the isdn code in trunk looks sane?
>>
>> Thanks,
>>
>> Darrick
>>
>> Ingmar Schraub wrote:
>>> Hi Darrick,
>>>
>>> I am this week at Cebit / Hannover / Germany. Show ends on sunday. I 
>>> won't be able to do any work before monday.
>>>
>>> So either include what you have currently in trunk or please wait 
>>> until next week. I think, waiting for a few more days can't be a 
>>> problem since  no new release was done for the last few months.
>>>
>>> So let's see.
>>>
>>> regards from Cebit,
>>>
>>> Ingmar
>>>
>>> Darrick Hartman wrote:
>>>> Ingmar,
>>>>
>>>> We're getting very close to where we'll fork trunk into 0.6 and 
>>>> actually do some releases.  Would you have a chance to test the isdn 
>>>> code in trunk to ensure it functions properly?  I'm building some 
>>>> images tonight/tomorrow and will upload those sometime tomorrow.
>>>>
>>>> I'm inclined to call those files a release candidate.  If everything 
>>>> looks good, we'll release the images within the next week or so.  We 
>>>> would need to do some major work to come up with a reasonable 
>>>> changelog.
>>>>
>>>> Thanks,
>>>>
>>>> Darrick
>>
>>


-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com
Small Business IT Specialists
Office:  920.547.4535
    Cell:  920.901.3113

Re: [Astlinux-devel] [Astlinux-users] [1643/SQLite] Bug in makefile?

[Darrick H. (lists) <dha...@dj...>]

Try again now.  I fixed the package and bumped the version to the latest 
release.

Darrick Hartman (lists) wrote:
> Andrea Cristofanini wrote:
>> Fred
>> i got this too, i have done the same.
>> Ciao Andrea
>> Fred ha scritto:
>>> Hi
>>>
>>> It looks like there's a small bug in the makefile that triggers an error 
>>> when building AstLinux:
>>>
>>> cp -fpR 
>>> /home/compile/astlinux-trunk/build_i586/staging_dir/usr/lib/libsqlite3.so.* 
>>> /home/compile/astlinux-trunk/build_i586/root/usr/lib/
>>> cp: cannot stat 
>>> `/home/compile/astlinux-trunk/build_i586/staging_dir/usr/lib/libsqlite3.so.*': 
>>> No such file or directory
>>> make: *** [/home/compile/astlinux-trunk/build_i586/root/usr/bin/sqlite3] 
>>> Error 1
>>>
>>> There's actually "libsqlite3.so -> libsqlite3-3.5.6.so.0.8.6", so I guess 
>>> the makefile should be changed to use "cp -fpR 
>>> /home/compile/astlinux-trunk/build_i586/staging_dir/usr/lib/libsqlite3.so*" 
>>> instead (ie. no trailing dot).
>>>
>>> HTH
>>> Fred.
> 
> Guys thanks!  We'll look into this more.  Please join and use the new 
> -devel list so we don't bombard normal users with development issues 
> that don't affect the operation of the distributed Astlinux.  cdr_sqlite 
> will probably not be added to Astlinux until we go to Asterisk 1.6.
> 
> Darrick


-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-devel] arno problems

[Philip P. <phi...@re...>]

Kristian Kielhofner wrote:
> On Wed, Mar 12, 2008 at 2:44 PM, Philip Prindeville
> <phi...@re...> wrote:
>   
>> Like a lot of targets, it's best to do make xyzzy-clean before remaking
>>  xyzzy.
>>
>>
>>     
>
> [kris@admin1 astlinux-trunk]$ make arnofw-clean
> rm -f /home/kris/projects/astlinux-trunk/build_i586/root/usr/sbin/arno-iptables-firewall
> rm -rf /home/kris/projects/astlinux-trunk/build_i586/root/etc/arno-iptables-firewall
> \
>         /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall
>
> make again:
>
> ln -sf /tmp/etc/arno-iptables-firewall
> /home/kris/projects/astlinux-trunk/build_i586/root/etc/arno-iptables-firewall
> mkdir /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall
> \
>         /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/plugins
> /usr/bin/install -D -m 0755
> /home/kris/projects/astlinux-trunk/build_i586/arno-iptables-firewall_1.8.8n/arno-iptables-firewall
> \
>         /home/kris/projects/astlinux-trunk/build_i586/root/usr/sbin/arno-iptables-firewall
> /usr/bin/install -D -m 0644 package/arno-fw/arnofw.wrapper \
>         /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/astlinux.shim
> /usr/bin/install -D -m 0644
> /home/kris/projects/astlinux-trunk/build_i586/arno-iptables-firewall_1.8.8n/etc/arno-iptables-firewall/firewall.conf
> \
>         /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/firewall.conf
> /home/kris/projects/astlinux-trunk/toolchain_build_i586/bin/sed -i -r
> -e 's:^IPTABLES="[^"]*":IPTABLES="/usr/sbin/iptables":' \
>         -e 's:^(INT_IF|EXT_IF|MODEM_IF|INTERNAL_NET|NAT|NAT_INTERNAL_NET)=:#&:'
> \
>         /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/firewall.conf
> /home/kris/projects/astlinux-trunk/toolchain_build_i586/bin/sed -i -r
> -e 's:^LOCAL_CONFIG_FILE="":LOCAL_CONFIG_FILE="/etc/arno-iptables-firewall/astlinux.shim":'
> \
>         /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/firewall.conf
> /usr/bin/install -D -m 0755
> /home/kris/projects/astlinux-trunk/build_i586/arno-iptables-firewall_1.8.8n/etc/arno-iptables-firewall/custom-rules
> \
>         /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall
> /usr/bin/install: cannot overwrite directory
> `/home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall'
> with non-directory
> make: *** [/home/kris/projects/astlinux-trunk/build_i586/root/usr/sbin/arno-iptables-firewall]
> Error 1
> [kris@admin1 astlinux-trunk]$
>
>   

My version of "install" (of FC8) can figure out that:

install -D ... file dir

means to create a file called dir/`basename file` in that directory.  
Apparently yours behaves differently.  Try this patch (1646).

-Philip

Re: [Astlinux-devel] arno problems

[Kristian K. <kri...@gm...>]

On Wed, Mar 12, 2008 at 2:44 PM, Philip Prindeville
<phi...@re...> wrote:
> Like a lot of targets, it's best to do make xyzzy-clean before remaking
>  xyzzy.
>
>

[kris@admin1 astlinux-trunk]$ make arnofw-clean
rm -f /home/kris/projects/astlinux-trunk/build_i586/root/usr/sbin/arno-iptables-firewall
rm -rf /home/kris/projects/astlinux-trunk/build_i586/root/etc/arno-iptables-firewall
\
        /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall

make again:

ln -sf /tmp/etc/arno-iptables-firewall
/home/kris/projects/astlinux-trunk/build_i586/root/etc/arno-iptables-firewall
mkdir /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall
\
        /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/plugins
/usr/bin/install -D -m 0755
/home/kris/projects/astlinux-trunk/build_i586/arno-iptables-firewall_1.8.8n/arno-iptables-firewall
\
        /home/kris/projects/astlinux-trunk/build_i586/root/usr/sbin/arno-iptables-firewall
/usr/bin/install -D -m 0644 package/arno-fw/arnofw.wrapper \
        /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/astlinux.shim
/usr/bin/install -D -m 0644
/home/kris/projects/astlinux-trunk/build_i586/arno-iptables-firewall_1.8.8n/etc/arno-iptables-firewall/firewall.conf
\
        /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/firewall.conf
/home/kris/projects/astlinux-trunk/toolchain_build_i586/bin/sed -i -r
-e 's:^IPTABLES="[^"]*":IPTABLES="/usr/sbin/iptables":' \
        -e 's:^(INT_IF|EXT_IF|MODEM_IF|INTERNAL_NET|NAT|NAT_INTERNAL_NET)=:#&:'
\
        /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/firewall.conf
/home/kris/projects/astlinux-trunk/toolchain_build_i586/bin/sed -i -r
-e 's:^LOCAL_CONFIG_FILE="":LOCAL_CONFIG_FILE="/etc/arno-iptables-firewall/astlinux.shim":'
\
        /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall/firewall.conf
/usr/bin/install -D -m 0755
/home/kris/projects/astlinux-trunk/build_i586/arno-iptables-firewall_1.8.8n/etc/arno-iptables-firewall/custom-rules
\
        /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall
/usr/bin/install: cannot overwrite directory
`/home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall'
with non-directory
make: *** [/home/kris/projects/astlinux-trunk/build_i586/root/usr/sbin/arno-iptables-firewall]
Error 1
[kris@admin1 astlinux-trunk]$

-- 
Kristian Kielhofner

Re: [Astlinux-devel] arno problems

[Philip P. <phi...@re...>]

Like a lot of targets, it's best to do make xyzzy-clean before remaking 
xyzzy.


Kristian Kielhofner wrote:
> Hello everyone,
>
>   I'm getting the following error when re-running make with arnofw enabled:
>
> /usr/bin/install -D -m 0755
> /home/kris/projects/astlinux-trunk/build_i586/arno-iptables-firewall_1.8.8n/etc/arno-iptables-firewall/custom-rules
> \
>         /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall
> /usr/bin/install: cannot overwrite directory
> `/home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall'
> with non-directory
> make: *** [/home/kris/projects/astlinux-trunk/build_i586/root/usr/sbin/arno-iptables-firewall]
> Error 1
>
>   

[Astlinux-devel] arno problems

[Kristian K. <kri...@gm...>]

Hello everyone,

  I'm getting the following error when re-running make with arnofw enabled:

/usr/bin/install -D -m 0755
/home/kris/projects/astlinux-trunk/build_i586/arno-iptables-firewall_1.8.8n/etc/arno-iptables-firewall/custom-rules
\
        /home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall
/usr/bin/install: cannot overwrite directory
`/home/kris/projects/astlinux-trunk/build_i586/root/stat/etc/arno-iptables-firewall'
with non-directory
make: *** [/home/kris/projects/astlinux-trunk/build_i586/root/usr/sbin/arno-iptables-firewall]
Error 1

-- 
Kristian Kielhofner

Re: [Astlinux-devel] [astlinux-devel] broken uclib patch in current trunk

[Ingmar S. <is...@es...>]

Ciao Andrea,

you should not use the snapshot version of uClibc. Stay with the defined 
old 0.9.28 version.

regards,

Ingmar

Andrea Cristofanini wrote:
> Hey guys
> i'm expirencing problems :
> [andrea@mulo3 astlinux-trunk]$ make
> mkdir -p /home/andrea/astlinux-trunk/toolchain_build_i686
> bzcat /home/andrea/astlinux-trunk/dl/uClibc-snapshot.tar.bz2 | tar -C 
> /home/andrea/astlinux-trunk/toolchain_build_i686   -xf -
> toolchain/patch-kernel.sh 
> /home/andrea/astlinux-trunk/toolchain_build_i686/uClibc 
> toolchain/uClibc/ \*.patch
> 
> Applying uClibc-cpu-optimization.patch using plaintext:
> patching file Rules.mak
> Hunk #1 FAILED at 127.
> 1 out of 1 hunk FAILED -- saving rejects to file Rules.mak.rej
> Patch failed!  Please fix uClibc-cpu-optimization.patch!
> make: *** 
> [/home/andrea/astlinux-trunk/toolchain_build_i686/uClibc/.unpacked] Error 1
> You have new mail in /var/spool/mail/root
> [andrea@mulo3 astlinux-trunk]$
> 
> 
> Does someone else have see this too ?
> 
> Regards
> Andrea
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

[Astlinux-devel] [astlinux-devel] broken uclib patch in current trunk

[Andrea C. <and...@ze...>]

Hey guys
i'm expirencing problems :
[andrea@mulo3 astlinux-trunk]$ make
mkdir -p /home/andrea/astlinux-trunk/toolchain_build_i686
bzcat /home/andrea/astlinux-trunk/dl/uClibc-snapshot.tar.bz2 | tar -C 
/home/andrea/astlinux-trunk/toolchain_build_i686   -xf -
toolchain/patch-kernel.sh 
/home/andrea/astlinux-trunk/toolchain_build_i686/uClibc 
toolchain/uClibc/ \*.patch

Applying uClibc-cpu-optimization.patch using plaintext:
patching file Rules.mak
Hunk #1 FAILED at 127.
1 out of 1 hunk FAILED -- saving rejects to file Rules.mak.rej
Patch failed!  Please fix uClibc-cpu-optimization.patch!
make: *** 
[/home/andrea/astlinux-trunk/toolchain_build_i686/uClibc/.unpacked] Error 1
You have new mail in /var/spool/mail/root
[andrea@mulo3 astlinux-trunk]$


Does someone else have see this too ?

Regards
Andrea

Re: [Astlinux-devel] [Astlinux-users] [1643/SQLite] Bug in makefile?

[Darrick H. (lists) <dha...@dj...>]

Andrea Cristofanini wrote:
> Fred
> i got this too, i have done the same.
> Ciao Andrea
> Fred ha scritto:
>> Hi
>>
>> It looks like there's a small bug in the makefile that triggers an error 
>> when building AstLinux:
>>
>> cp -fpR 
>> /home/compile/astlinux-trunk/build_i586/staging_dir/usr/lib/libsqlite3.so.* 
>> /home/compile/astlinux-trunk/build_i586/root/usr/lib/
>> cp: cannot stat 
>> `/home/compile/astlinux-trunk/build_i586/staging_dir/usr/lib/libsqlite3.so.*': 
>> No such file or directory
>> make: *** [/home/compile/astlinux-trunk/build_i586/root/usr/bin/sqlite3] 
>> Error 1
>>
>> There's actually "libsqlite3.so -> libsqlite3-3.5.6.so.0.8.6", so I guess 
>> the makefile should be changed to use "cp -fpR 
>> /home/compile/astlinux-trunk/build_i586/staging_dir/usr/lib/libsqlite3.so*" 
>> instead (ie. no trailing dot).
>>
>> HTH
>> Fred.

Guys thanks!  We'll look into this more.  Please join and use the new 
-devel list so we don't bombard normal users with development issues 
that don't affect the operation of the distributed Astlinux.  cdr_sqlite 
will probably not be added to Astlinux until we go to Asterisk 1.6.

Darrick
-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-devel] Bug in configure script for tcpdump...

[Darrick H. <dha...@dj...>]

Philip Prindeville wrote:
> Seeing:
> 
> zcat /home/philipp/trunk2/dl/tcpdump-3.9.4.tar.gz | tar -C /home/philipp/trunk2/build_i586   -xf -
> touch /home/philipp/trunk2/build_i586/tcpdump-3.9.4/.unpacked
> ( \
>                 cd /home/philipp/trunk2/build_i586/tcpdump-3.9.4 ; \
>                 ac_cv_linux_vers= \
>                 BUILD_CC=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-gcc HOSTCC="gcc" \
>                 PATH=/home/philipp/trunk2/build_i586/staging_dir/bin:/home/philipp/trunk2/toolchain_build_i586/bin:/bin:/sbin:/usr/bin:/usr/sbin AR=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-ar AS=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-as LD=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-ld NM=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-nm CC=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-gcc GCC=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-gcc CXX=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-g++ CPP=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-cpp RANLIB=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-ranlib OBJCOPY=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-objcopy \
>                 CFLAGS="-Os -pipe -fomit-frame-pointer " \
>                 ./configure \
>                 --target=i586-linux \
>                 --host=i586-linux \
>                 --build=i386-pc-linux-gnu \
>                 --with-build-cc="gcc" \
>                 --prefix=/home/philipp/trunk2/build_i586/staging_dir \
>                 --libdir=/home/philipp/trunk2/build_i586/staging_dir/lib \
>                 --includedir=/home/philipp/trunk2/build_i586/staging_dir/include \
>                 --without-crypto \
>         )
> checking build system type... i386-pc-linux-gnu
> checking host system type... i586-pc-linux-gnu
> checking for i586-linux-gcc... /home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... yes
> ...
> checking netdnet/dnetdb.h usability... no
> checking netdnet/dnetdb.h presence... no
> checking for netdnet/dnetdb.h... no
> checking for netinet/if_ether.h... yes
> checking whether time.h and sys/time.h may both be included... yes
> checking Linux kernel version... (cached) 
> ./configure: line 3470: test: =: unary operator expected
> ./configure: line 3475: test: -lt: unary operator expected
> checking smi.h usability... no
> ...
> checking for inttypes.h... (cached) yes
> checking whether inttypes.h defines the PRI[doxu]64 macros... yes
> checking if sockaddr struct has sa_len member... no
> checking if unaligned accesses fail... ./configure: ./conftest: /lib/ld-uClibc.so.0: bad ELF interpreter: No such file or directory
> yes
> 
> 
> 
> seems there are some issues with the configure script.
> 
> It shouldn't be checking unaligned accesses if cross-compiling. Not sure 
> what the earlier error was. Looking at another issue or I'd dig into 
> this one.

Generally tests are not supported when cross-compiling (so the 
./conftest might be causing the issues (I haven't tested and won't have 
time today to do so either)... just taking a wild guess.

[Astlinux-devel] Bug in configure script for tcpdump...

[Philip P. <phi...@re...>]

Seeing:

zcat /home/philipp/trunk2/dl/tcpdump-3.9.4.tar.gz | tar -C /home/philipp/trunk2/build_i586   -xf -
touch /home/philipp/trunk2/build_i586/tcpdump-3.9.4/.unpacked
( \
                cd /home/philipp/trunk2/build_i586/tcpdump-3.9.4 ; \
                ac_cv_linux_vers= \
                BUILD_CC=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-gcc HOSTCC="gcc" \
                PATH=/home/philipp/trunk2/build_i586/staging_dir/bin:/home/philipp/trunk2/toolchain_build_i586/bin:/bin:/sbin:/usr/bin:/usr/sbin AR=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-ar AS=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-as LD=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-ld NM=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-nm CC=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-gcc GCC=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-gcc CXX=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-g++ CPP=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-cpp RANLIB=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-ranlib OBJCOPY=/home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-objcopy \
                CFLAGS="-Os -pipe -fomit-frame-pointer " \
                ./configure \
                --target=i586-linux \
                --host=i586-linux \
                --build=i386-pc-linux-gnu \
                --with-build-cc="gcc" \
                --prefix=/home/philipp/trunk2/build_i586/staging_dir \
                --libdir=/home/philipp/trunk2/build_i586/staging_dir/lib \
                --includedir=/home/philipp/trunk2/build_i586/staging_dir/include \
                --without-crypto \
        )
checking build system type... i386-pc-linux-gnu
checking host system type... i586-pc-linux-gnu
checking for i586-linux-gcc... /home/philipp/trunk2/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
...
checking netdnet/dnetdb.h usability... no
checking netdnet/dnetdb.h presence... no
checking for netdnet/dnetdb.h... no
checking for netinet/if_ether.h... yes
checking whether time.h and sys/time.h may both be included... yes
checking Linux kernel version... (cached) 
./configure: line 3470: test: =: unary operator expected
./configure: line 3475: test: -lt: unary operator expected
checking smi.h usability... no
...
checking for inttypes.h... (cached) yes
checking whether inttypes.h defines the PRI[doxu]64 macros... yes
checking if sockaddr struct has sa_len member... no
checking if unaligned accesses fail... ./configure: ./conftest: /lib/ld-uClibc.so.0: bad ELF interpreter: No such file or directory
yes



seems there are some issues with the configure script.

It shouldn't be checking unaligned accesses if cross-compiling. Not sure 
what the earlier error was. Looking at another issue or I'd dig into 
this one.

[Astlinux-devel] Default shell, minimum environment, etc.

[Philip P. <phi...@re...>]

I was wondering:

Are there any circumstances when "awk" won't be present on a built 
system?  Or is it a requirement?  Is there any way to flag a component 
as non-optional in the Config.in files?

And... what about Bash?  Can we make it the required shell (and link 
/bin/sh to it) to simplify scripting?

Thanks,

-Philip