search

roadlabs / alt-f

Automatically exported from code.google.com/p/alt-f
0 stars 1 forks source link

Can not recompile alt-f #87

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
After checkout of alf-f

url for ethtool is not valid & url for fakeroot is not valid 
after corecting this issue ( see patch in attachement ) 

i had a problem compiling libiconv ( see attachment ouput_iconv_fail )

i think there are a problem with the propagation of variable  STRIPPROG

Original issue reported on code.google.com by erwan....@gmail.com on 7 Apr 2012 at 4:39

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks for the url patches.

As for the iconv issue, I can't reproduce it, as I always do a fresh 
checkout/build before a new release (apart from the downloads step).

But the log you attached is not the log of the *first* build, when makefiles 
are created and variables set on them -- perhaps the first build failed and you 
restart the build? That is not supported by 'buildroot', you must remove the 
"binaries build_arm project_build_arm toolchain_build_arm" directories and 
start a fresh make (you can save the 'dl' directory or make it a link to 
another directory where you keep the downloads)

I attach my own (compressed) log, edited to use the same base directory that 
you are using, so you can diff them directly.

Thanks and please report back.

Original comment by whoami.j...@gmail.com on 9 Apr 2012 at 7:07

Attachments:

GoogleCodeExporter commented 9 years ago 
I'm seeing this problem as well.  The problem occurs when "make O=$BLDDIR" goes 
to do the ">>> libiconv 1.14 Installing to target" step:

/usr/bin/make -j6 DESTDIR=/alt-f/alt-f-build/project_build_arm/dns323/root  
install-strip -C /alt-f/alt-f-build/build_arm/libiconv-1.14/
make[1]: Entering directory `/alt-f/alt-f-build/build_arm/libiconv-1.14'
cd libcharset && /usr/bin/make install-strip prefix='/usr' exec_prefix='/usr' 
libdir='/usr/lib'

Eventually "/alt-f/alt-f-build/build_arm/libiconv-1.14/build-aux/install-sh -c 
-s iconv /alt-f/alt-f-build/project_build_arm/dns323/root/usr/bin/iconv" is 
called, and this process searches through $PATH for just "strip", and ends up 
getting /usr/bin/strip.

install-sh wants $STRIPPROG to be set, while the Makefiles are providing 
$STRIPCMD

Original comment by brandon....@gmail.com on 2 May 2012 at 5:31

GoogleCodeExporter commented 9 years ago 
[Please notice that I'm not looking at the makefiles/scripts, but only the log, 
as I can't reproduce the problem]

But in my logs, STRIPPROG is set as INSTALL_PROGRAM_ENV

>>> libiconv 1.14 Installing to target

...

make[3]: Leaving directory 
`/home/jcard/Alt-F/build-base/build_arm/libiconv-1.14'
/usr/bin/make  INSTALL_PROGRAM="/bin/sh 
/home/jcard/Alt-F/build-base/build_arm/libiconv-1.14/build-a
ux/install-sh -c -s" \
  install_sh_PROGRAM="/bin/sh /home/jcard/Alt-F/build-base/build_arm/libiconv-1.14/build-aux/install
-sh -c -s" INSTALL_STRIP_FLAG=-s \
  `test -z '/home/jcard/Alt-F/build-base/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-strip
' || \
    echo "INSTALL_PROGRAM_ENV=STRIPPROG='/home/jcard/Alt-F/build-base/build_arm/staging_dir/usr/bin/
arm-linux-uclibcgnueabi-strip'"` install
make[3]: Entering directory 
`/home/jcard/Alt-F/build-base/build_arm/libiconv-1.14/srclib'

... later on, install/strip iconv does not fails:

libtool: install: /bin/sh 
/home/jcard/Alt-F/build-base/build_arm/libiconv-1.14/build-aux/install-sh -c -s 
iconv /home/jcard/Alt-F/build-base/project_build_arm/dns323/root/usr/bin/iconv
make[3]: Leaving directory 
`/home/jcard/Alt-F/build-base/build_arm/libiconv-1.14/src'

Before, at the >>> libiconv configure step, I have in the logs:

STRIP="/home/jcard/Alt-F/build-base/build_arm/staging_dir/usr/bin/arm-linux-ucli
bcgnueabi-strip"

and latter on

checking for strip... 
/home/jcard/Alt-F/build-base/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnuea
bi-strip

Do you have a working solution for you, so I can test it?
Thanks

Original comment by whoami.j...@gmail.com on 2 May 2012 at 9:21

GoogleCodeExporter commented 9 years ago 
INSTALL_PROGRAM_ENV is provided by 
$BLDDIR/build_arm/libiconv-1.14/srclib/Makefile, in the install-strip target.  
That make process exits, and then the higher-level make moves on to "cd src && 
/usr/bin/make install-strip prefix='/usr' exec_prefix='/usr' 
libdir='/usr/lib'", which uses the makefile in 
$BLDDIR/build_arm/libiconv-1.14/src/Makefile.  The install-strip target in that 
Makefile doesn't provide INSTALL_PROGRAM_ENV.

The flaw seems to be in the libiconv Makefiles.  Are you sure install-sh isn't 
finding a useful 'strip' or 'gstrip' somewhere in your $PATH?  An "strace -s 
1500 -vv -e trace=file,process -f make O=$BLDDIR" would be interesting.

As a workaround, I've found giving STRIPPROG on the command line works.  Such 
as:
    make O=${BLDDIR} STRIPPROG=/alt-f/alt-f-build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-strip

Original comment by brandon....@gmail.com on 3 May 2012 at 4:12

GoogleCodeExporter commented 9 years ago 
I now see what you mean.

And yes, my system's 'strip' and 'install' are able to strip ARM binaries.
I'm on opensuse-12.1, what system are you running?

Please try the attached patch.

Original comment by whoami.j...@gmail.com on 5 May 2012 at 5:26

Attachments:

GoogleCodeExporter commented 9 years ago 
That patch worked great.  Complete build, no failures.  This is on Ubuntu 
11.10, by the way.  I don't know what the original bug poster is running on.

Original comment by brandon....@gmail.com on 9 May 2012 at 2:18

GoogleCodeExporter commented 9 years ago 
-closed by svn commit 1652

-the same might occur in other packages as well, as my system's 'strip' and 
'install' programs are able to strip ARM binaries.
I put my 'strip' apart, but can't do the same with 'install', so this issue 
might exists in other packages out of the base firmware, when using .config-pkgs

Thanks

Original comment by whoami.j...@gmail.com on 9 May 2012 at 5:11

GoogleCodeExporter commented 9 years ago 
Same probleme on package bash-4.2 .

======================================================================
make[1]: Leaving directory `/tmp/build/build_arm/bash-4.2'
>>> bash 4.2 Installing to target
/usr/bin/make -j6 DESTDIR=/tmp/build/project_build_arm/dns323/root  
install-strip -C /tmp/build/build_arm/bash-4.2/
make[1]: Entering directory `/tmp/build/build_arm/bash-4.2'
/usr/bin/make -w --jobserver-fds=3,4 -j INSTALL_PROGRAM='/usr/bin/install -c 
-s' \
                prefix=/usr exec_prefix=/usr \
                DESTDIR=/tmp/build/project_build_arm/dns323/root install
make[2]: Entering directory `/tmp/build/build_arm/bash-4.2'
mkdir -p -- /tmp/build/project_build_arm/dns323/root/usr/share/man/man1
mkdir -p -- /tmp/build/project_build_arm/dns323/root/usr/share/info
( cd ./po/ ; /usr/bin/make -w --jobserver-fds=3,4 - --jobserver-fds=3,4 -j 
DESTDIR=/tmp/build/project_build_arm/dns323/root installdirs )
make[3]: Entering directory `/tmp/build/build_arm/bash-4.2/po'
if test "bash" = "gettext-tools"; then \
          /bin/sh /tmp/build/build_arm/bash-4.2/./support/mkinstalldirs /tmp/build/project_build_arm/dns323/root/usr/share/gettext/po; \
        else \
          : ; \
        fi
make[3]: Leaving directory `/tmp/build/build_arm/bash-4.2/po'
/usr/bin/install -c -s -m 0755 bash 
/tmp/build/project_build_arm/dns323/root/usr/bin/bash
strip: Unable to recognise the format of the input file 
`/tmp/build/project_build_arm/dns323/root/usr/bin/bash'
/usr/bin/install: strip process terminated abnormally
make[2]: *** [install] Error 1
make[2]: Leaving directory `/tmp/build/build_arm/bash-4.2'
make[1]: *** [install-strip] Error 2
make[1]: Leaving directory `/tmp/build/build_arm/bash-4.2'
make: *** 
[/tmp/build/project_build_arm/dns323/autotools-stamps/bash_target_installed] 
Error 2
======================================================================

Original comment by erwan....@gmail.com on 20 May 2012 at 6:33

GoogleCodeExporter commented 9 years ago 
I have reopen the issue.

Can you please edit "package/bash/bash.mk" and add the following lines after 
BASH_TARGET_BINARY, as in 

BASH_TARGET_BINARY:=bin/bash

ifeq ($(BR2_ENABLE_DEBUG),y)
BASH_INSTALL_TARGET_OPT = DESTDIR=$(TARGET_DIR) install
else
BASH_INSTALL_TARGET_OPT = DESTDIR=$(TARGET_DIR) install-strip 
STRIPPROG="$(STRIPCMD)"
endif

As you can see the only difference to the libiconv patch above was replacing 
the LIBICONV with BASH, the package name.

As you seems to be building the packages tree, you will most likely find other 
identical issues; you can try to fix them using the same method.

Please continue reporting the problematic packages, as well as broken URL 
download sites.

Thanks,
Joao

Original comment by whoami.j...@gmail.com on 20 May 2012 at 8:57

GoogleCodeExporter commented 9 years ago 
It's not enough :(

======================================================================
make[1]: Leaving directory `/tmp/build/build_arm/bash-4.2'
>>> bash 4.2 Installing to target
/usr/bin/make -j6 DESTDIR=/tmp/build/project_build_arm/dns323/root 
install-strip 
STRIPPROG="/tmp/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-stri
p --remove-section=.comment --remove-section=.note" -C 
/tmp/build/build_arm/bash-4.2/
make[1]: Entering directory `/tmp/build/build_arm/bash-4.2'
/usr/bin/make -w --jobserver-fds=3,4 -j INSTALL_PROGRAM='/usr/bin/install -c 
-s' \
                prefix=/usr exec_prefix=/usr \
                DESTDIR=/tmp/build/project_build_arm/dns323/root install
make[2]: Entering directory `/tmp/build/build_arm/bash-4.2'
mkdir -p -- /tmp/build/project_build_arm/dns323/root/usr/share/man/man1
mkdir -p -- /tmp/build/project_build_arm/dns323/root/usr/share/info
( cd ./po/ ; /usr/bin/make -w --jobserver-fds=3,4 - --jobserver-fds=3,4 -j 
DESTDIR=/tmp/build/project_build_arm/dns323/root installdirs )
make[3]: Entering directory `/tmp/build/build_arm/bash-4.2/po'
if test "bash" = "gettext-tools"; then \
          /bin/sh /tmp/build/build_arm/bash-4.2/./support/mkinstalldirs /tmp/build/project_build_arm/dns323/root/usr/share/gettext/po; \
        else \
          : ; \
        fi
make[3]: Leaving directory `/tmp/build/build_arm/bash-4.2/po'
/usr/bin/install -c -s -m 0755 bash 
/tmp/build/project_build_arm/dns323/root/usr/bin/bash
strip: Unable to recognise the format of the input file 
`/tmp/build/project_build_arm/dns323/root/usr/bin/bash'
/usr/bin/install: strip process terminated abnormally
make[2]: *** [install] Error 1
make[2]: Leaving directory `/tmp/build/build_arm/bash-4.2'
make[1]: *** [install-strip] Error 2
make[1]: Leaving directory `/tmp/build/build_arm/bash-4.2'
make: *** 
[/tmp/build/project_build_arm/dns323/autotools-stamps/bash_target_installed] 
Error 2
======================================================================

Original comment by erwan....@gmail.com on 27 May 2012 at 11:28

GoogleCodeExporter commented 9 years ago 
What system are you running?

Can you please post the output of your system's

   install --version
   install --help

Please try the attached patch. You have to run configure again, so you have to 
run first
   make O=$BLDDIR bash-dirclean

The patch includes the previous patch, so you might have conflicts and need to 
apply it manually.

Thanks

Original comment by whoami.j...@gmail.com on 28 May 2012 at 6:33

Attachments:

GoogleCodeExporter commented 9 years ago 
debian squeeze / 6.0.4 
================================================================================
# install --version
install (GNU coreutils) 8.5
Copyright (C) 2010 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.

================================================================================
# install --help
Usage: install [OPTION]... [-T] SOURCE DEST
  or:  install [OPTION]... SOURCE... DIRECTORY
  or:  install [OPTION]... -t DIRECTORY SOURCE...
  or:  install [OPTION]... -d DIRECTORY...

This install program copies files (often just compiled) into destination
locations you choose.  If you want to download and install a ready-to-use
package on a GNU/Linux system, you should instead be using a package manager
like yum(1) or apt-get(1).

In the first three forms, copy SOURCE to DEST or multiple SOURCE(s) to
the existing DIRECTORY, while setting permission modes and owner/group.
In the 4th form, create all components of the given DIRECTORY(ies).

Mandatory arguments to long options are mandatory for short options too.
      --backup[=CONTROL]  make a backup of each existing destination file
  -b                  like --backup but does not accept an argument
  -c                  (ignored)
  -C, --compare       compare each pair of source and destination files, and
                        in some cases, do not modify the destination at all
  -d, --directory     treat all arguments as directory names; create all
                        components of the specified directories   
  -D                  create all leading components of DEST except the last,
                        then copy SOURCE to DEST
  -g, --group=GROUP   set group ownership, instead of process' current group
  -m, --mode=MODE     set permission mode (as in chmod), instead of rwxr-xr-x
  -o, --owner=OWNER   set ownership (super-user only)
  -p, --preserve-timestamps   apply access/modification times of SOURCE files
                        to corresponding destination files
  -s, --strip         strip symbol tables
      --strip-program=PROGRAM  program used to strip binaries
  -S, --suffix=SUFFIX  override the usual backup suffix
  -t, --target-directory=DIRECTORY  copy all SOURCE arguments into DIRECTORY
  -T, --no-target-directory  treat DEST as a normal file
  -v, --verbose       print the name of each directory as it is created
      --preserve-context  preserve SELinux security context
  -Z, --context=CONTEXT  set SELinux security context of files and directories
      --help     display this help and exit
      --version  output version information and exit
The backup suffix is `~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX.
The version control method may be selected via the --backup option or through
the VERSION_CONTROL environment variable.  Here are the values:   

  none, off       never make backups (even if --backup is given)  
  numbered, t     make numbered backups
  existing, nil   numbered if numbered backups exist, simple otherwise
  simple, never   always make simple backups

Report install bugs to bug-coreutils@gnu.org
GNU coreutils home page: <http://www.gnu.org/software/coreutils/> 
General help using GNU software: <http://www.gnu.org/gethelp/>
For complete documentation, run: info coreutils 'install invocation'

================================================================================

Original comment by erwan....@gmail.com on 4 Jun 2012 at 3:10

GoogleCodeExporter commented 9 years ago 
ok for bash .

now i have a problem with python2.7

======================================================================
/tmp/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-ar rc 
libpython2.7.a Modules/config.o Modules/getpath.o Modules/main.o 
Modules/gcmodule.o
/tmp/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-ar rc 
libpython2.7.a Modules/threadmodule.o  Modules/signalmodule.o  
Modules/posixmodule.o  Modules/errnomodule.o  Modules/pwdmodule.o  
Modules/_sre.o  Modules/_codecsmodule.o  Modules/_weakref.o  
Modules/zipimport.o  Modules/symtablemodule.o  Modules/xxsubtype.o
/tmp/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-ranlib 
libpython2.7.a
/tmp/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc  -Xlinker 
-export-dynamic -o python \
                        Modules/python.o \
                        -L. -lpython2.7 -lpthread -ldl  -lpthread -lutil   -lm
./libpython2.7.so: warning: the use of LEGACY `utimes' is discouraged, use 
`utime'
./hostpython: error while loading shared libraries: libpython2.7.so.1.0: cannot 
open shared object file: No such file or directory
make[1]: *** [sharedmods] Error 127
make[1]: Leaving directory `/tmp/build/build_arm/Python-2.7.2'
make: *** [/tmp/build/build_arm/Python-2.7.2/python] Error 2
root@hst201:~/alt-f-read-only#

======================================================================

Original comment by erwan....@gmail.com on 9 Jun 2012 at 12:44

GoogleCodeExporter commented 9 years ago 
Can you please try the attached patch? It builds the host python statically.

Please remove $BLDDIR/build_arm/Python-2.7.2 before doing a new make.

Haven't you come across more broken download links?

Thanks

Original comment by whoami.j...@gmail.com on 10 Jun 2012 at 11:54

Attachments:

GoogleCodeExporter commented 9 years ago 
now ok for python 2.7

a patch for netsnmp
a patch for libusb

now a problem for compiling foomatic

==============================================================================
Finished configuring.
Type 'make' to build the package
then 'make install' to install it.
touch /tmp/build/build_arm/foomatic-db-engine-4.0.4/.configured
/usr/bin/make -j6 -C /tmp/build/build_arm/foomatic-db-engine-4.0.4 inplace
make[1]: Entering directory `/tmp/build/build_arm/foomatic-db-engine-4.0.4'
chmod a+rx ./makeDefaults
gcc -g -O2 -o foomatic-combo-xml foomatic-combo-xml.c
./makeDefaults --inplace
gcc -g -O2 -I/tmp/build/build_arm/staging_dir/usr/include/libxml2 -lxml2 -lz 
-lm -o foomatic-perl-data foomatic-perl-data.c
if [ x--inplace = x--inplace ] ; then touch .testing-stamp ; fi
chmod a+rx ./makeMan
./makeMan
/usr/bin/ld: cannot find -lxml2
collect2: ld returned 1 exit status
make[1]: *** [foomatic-perl-data] Error 1
make[1]: Leaving directory `/tmp/build/build_arm/foomatic-db-engine-4.0.4'
make: *** [/tmp/build/build_arm/foomatic-db-engine-4.0.4/.build] Error 2
==============================================================================

Original comment by erwan....@gmail.com on 16 Jun 2012 at 10:23

Attachments:

GoogleCodeExporter commented 9 years ago 
For foomatics, you have to install your system's libxml2 development package 
first, something like libxml2-dev or libxml2-devel.

You have to delete the $BLDDIR/build_arm/foomatic-db-engine-4.0.4 directory (or 
remove its '.configured' stamp file) in order for "make O=..." to rerun the 
package 'configure' in order to find the correct includes and libraries.

Ideally I could provide a libxml2-host package target for this (and other 
cases) and add it as a dependency to foomatic, and install the libmlx2-host 
files in $BLDDIR/build_arm/host_dir, but (sometimes) I'm just too lazy.

Sometimes BuildRoot 'leaks', i.e., it uses the system's includes when the 
target's should be used and vice-verse.

Other packages might need other devel packages installed, but one need to be 
careful with the above leaks.

A side issue that I would like you to verify: when I removed my system's 
'strip', to try to diagnose the first report, I didn't noticed immediately that 
the atd package binaries were not installed. Can you please verify if they are 
installed in your rootfs? Does 

   find $BLDDIR/project_build_arm/dns323/root -name atd

returns any file?

Thanks for your collaboration and patches.

Original comment by whoami.j...@gmail.com on 16 Jun 2012 at 4:12

GoogleCodeExporter commented 9 years ago 
for you information , net-snmp has changed version , 5.5.1 can not be 
downloaded  but 5.5.2  .
see
http://sourceforge.net/projects/net-snmp/files/net-snmp/ .

Original comment by erwan....@gmail.com on 21 Jul 2012 at 10:18

GoogleCodeExporter commented 9 years ago 
Thanks, fixed by svn commit 1785

No further issues?

Original comment by whoami.j...@gmail.com on 21 Jul 2012 at 10:10

GoogleCodeExporter commented 9 years ago 
problem on php compiling 

a extract of log the building

Original comment by erwan....@gmail.com on 25 Jul 2012 at 2:12

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have not yet SVN commit .config-pkgs, as it contains other unrelated changes.

I have however just committed some other php changes, so you have to 'svn 
update' first.
Then, please do a 

  make O=$BLDDIR menuconfig

then select

Package Selection for the target
Interpreter languages / Scripting
php
PHP Extensions
PDO
select PDO_SQLite
select PDO_MySQL

after saving and exiting, the command 'grep -i pdo .config' should output

BR2_PACKAGE_PHP_EXT_PDO=y
BR2_PACKAGE_PHP_EXT_PDO_SQLITE=y
# BR2_PACKAGE_PHP_EXT_PDO_SQLITE_EXTERNAL is not set
BR2_PACKAGE_PHP_EXT_PDO_MYSQL=y

You can then do a
   make O=$BLDDIR php-dirclean # remove the php directory because of the patch reject
   make O=$BLDDIR

Thanks

Original comment by whoami.j...@gmail.com on 25 Jul 2012 at 7:16

GoogleCodeExporter commented 9 years ago 
after building now problem on foomatic

Original comment by erwan....@gmail.com on 13 Aug 2012 at 2:50

Attachments:

GoogleCodeExporter commented 9 years ago 
You have already reported this issue when compiling foomatic-db. The indicated 
solution was to install your system's libxml2 development package.

Anyway, I added a dependency on foomatic-db that builds a libxml2 for the host 
that solves the problem and avoids the need to install libxml2-devel in your 
system.

Please try the attached patch and afterwards execute

   rm -rf $BLDDIR/build_arm/foomatic-db-engine-4.0.4
   make O=$BLDDIR

Thanks

Original comment by whoami.j...@gmail.com on 15 Aug 2012 at 8:10

Attachments:

GoogleCodeExporter commented 9 years ago 
after install libxml2-devl . ok for build foomatic-db-engine

I had a problem with gs ( my patch for fixing url )

After i have a problem when building git .
a conflict between object.h from git and object.h from python .

Original comment by erwan....@gmail.com on 25 Aug 2012 at 12:21

Attachments:

GoogleCodeExporter commented 9 years ago 
I have made some changes to python dependent programs/modules that shall solve 
the git build. Please do a svn update and try again.
I have made other changes that I hope will not break things for you.

Thanks for the gs url patch, applied.

Original comment by whoami.j...@gmail.com on 30 Aug 2012 at 12:40

GoogleCodeExporter commented 9 years ago 
I had some regression on the building of kernel .

Build fail on mdadm compilation .

see in attachement the output of make

Original comment by erwan....@gmail.com on 6 Sep 2012 at 7:02

Attachments:

GoogleCodeExporter commented 9 years ago 
Fixed by svn commit 1830: mdadm: fix build target

I have rebuild (not downloaded) all packages from scratch and all went fine, 
that's again your turn :-)

Thanks for your continued availability and support.

Original comment by whoami.j...@gmail.com on 6 Sep 2012 at 6:27

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
My patch for fixing urls for source and php compilation 

File impacted;

.config-pkgs
package/hplip/hplip.mk   
package/nuts/nuts.mk  
package/multimedia/mediatomb/mediatomb.mk
package/multimedia/mt-daapd/mt-daapd.mk

Original comment by erwan....@gmail.com on 8 Sep 2012 at 8:30

Attachments:

GoogleCodeExporter commented 9 years ago 
Now , i have problem with openssh_hook_pot_install 

#/usr/bin/install -D -m 755 package/openssh/S50sshd 
/tmp/build/project_build_arm/dns323/root/etc/init.d/S50sshd
sed 's/#.*Ciphers /Ciphers aes128-cbc,/' 
/tmp/build/project_build_arm/dns323/root/etc/ssh/ssh_config
sed: can't read /tmp/build/project_build_arm/dns323/root/etc/ssh/ssh_config: No 
such file or directory
make: *** 
[/tmp/build/project_build_arm/dns323/autotools-stamps/openssh_hook_post_install]
 Error 2

Original comment by erwan....@gmail.com on 8 Sep 2012 at 12:29

Attachments:

GoogleCodeExporter commented 9 years ago 
> Now , i have problem with openssh_hook_pot_install

I can't reproduce this.

From the logs you seems to be compiling the base firmware (using .config-base), 
not the packages (using .config-pkgs).
Are you reusing the same tree (O=...) for both? This can lead to problems.

Original comment by whoami.j...@gmail.com on 12 Sep 2012 at 6:17

GoogleCodeExporter commented 9 years ago 
Thanks for the URL fixups, svn commit 1833: hplip, nuts, mediatomb, mt-daapd: 
fix URL download sites, contributed by erwan.mas

Regarding the openssh issue:

openssh is enabled on both the base firmware and packages configuration files.
-For the base firmware BR2_PACKAGE_OPENSSH_SFTP_ONLY is defined, and only the 
sftp-server is installed after build time (OPENSSH_HOOK_POST_BUILD), although 
the whole package is marked as installed (see 
$BLDDIR/project_build_arm/dns323/autotools-stamps/openssh_*)
-For the package configuration a full install is performed, and the openssh 
Makefile target "install" deploys target "install-sysconf" that actually 
installs ssh_config, sshd_config and moduli.

Actually the OPENSSH_HOOK_POST_INSTALL sed command (the one that is failing in 
your build) is missing a '-i' flag, it should read as 'sed -i 's/#.*Ciphers...'

Original comment by whoami.j...@gmail.com on 13 Sep 2012 at 2:05

GoogleCodeExporter commented 9 years ago 
I reuse the same builddir ( bad idea ) it's why :)
I fix-it 

My patch for fixing urls for source and php compilation 

File impacted;
--- .config-pkgs
--- package/parted/parted.mk
--- package/openvpn/openvpn.mk

Original comment by erwan....@gmail.com on 14 Sep 2012 at 7:32

Attachments:

GoogleCodeExporter commented 9 years ago 
I had a problem when compiling unrar , problem when stripping .

In attachement my log ( first part compiling the kernel , second part compiling 
all packages ) .

Original comment by erwan....@gmail.com on 14 Sep 2012 at 5:27

Attachments:

GoogleCodeExporter commented 9 years ago 
unrar: please try the attached patch

urls: thanks again, committed. The buildroot makefile has a 'spyder' target, 
that is supposed to check all download sites, but I wasn't able to make it work 
only for the configured packages.

I also attach my current .config-pkgs, there are a few more packages for you to 
try.

The end is near, 'unrar' is near the alphabet end :-)

Original comment by whoami.j...@gmail.com on 14 Sep 2012 at 7:08

Attachments:

GoogleCodeExporter commented 9 years ago 
build fail arround minidlna 
 ... letter 'm' is far away from the aplhabet end .

in attachement the log of my lastest build

Original comment by erwan....@gmail.com on 19 Sep 2012 at 10:13

Attachments:

GoogleCodeExporter commented 9 years ago 
> build fail arround minidlna

Now fixed in svn, thanks.
This is a regression, given that libintl is now built (because of midnight 
commander), but seems to be incompatible with minidlna. This might happen with 
other packages as well.

>... letter 'm' is far away from the alphabet end.

In the previous build you was at letter 'u' (really at letter s, building 
sabnzbget that needs unrar), grossly about half a dozen packages away from the 
finish line...

The newly introduced packages introduced a regression; if you want to know how 
many packages are still missing to be built, execute the command:

ls $BLDDIR/build_arm | wc -l

This gives 151 packages total.

Original comment by whoami.j...@gmail.com on 20 Sep 2012 at 2:20

GoogleCodeExporter commented 9 years ago 
Funny ... after many tries ... the build finish without error 

But when i try to find a a package if find nothing .

find /tmp/build  -name \*ipk

Original comment by erwan....@gmail.com on 21 Sep 2012 at 7:53

GoogleCodeExporter commented 9 years ago 
You have to read the howtocreatepackages wiki, 
code.google.com/p/alt-f/wiki/HowToCreatePackages

You have done step 0. As you are not creating new packages, only building them, 
you can do a './mkpkg -all', and packages will be created in the 'pkgs' folder.

But read the wiki.

Original comment by Joao.fs....@gmail.com on 22 Sep 2012 at 12:13

GoogleCodeExporter commented 9 years ago 
To build all packages i need to do this :

    cp .config-pkgs .config
    ./mkprepare.sh 
        make O=$BLDDIR menuconfig

        ./mkpkg.sh -setroot
        make O=$BLDDIR 
        ./mkpkg.sh -all

Can you confirm ?

Original comment by erwan....@gmail.com on 26 Sep 2012 at 1:56

GoogleCodeExporter commented 9 years ago 
After a sucessefull built you only need to do a './mkpkg.sh -all'.

Thus:

    cp .config-pkgs .config
    ./mkprepare.sh 
        make O=$BLDDIR menuconfig
        make O=$BLDDIR 
        ./mkpkg.sh -all

The 'dev-bundle' package will fail, as its build is not automated.
The packages will be found in the 'pkgs' folder.

If you want to setup a package feed of yourself, copy all 'pkgs' folder files 
to, say, ~erwan/public_html/Alt-F, and enter 
'http://<server_name_or_IP/~erwan/Alt-F' as the Feed in the Alt-F package 
manager web page.

Original comment by whoami.j...@gmail.com on 26 Sep 2012 at 11:23

GoogleCodeExporter commented 9 years ago 
I have some errors during the building of somes packages :

Creating package avahi
Fail creating avahi package (./usr/lib/locale/bg/LC_MESSAGES not found)

Creating package davfs2
Fail creating davfs2 package (./etc/davfs2/certs not found)

Creating package foomatic-db
Fail creating foomatic-db package 
(./usr/share/ppd/Brother/HL-2170W-pxlmono.ppd.gz not found)

Creating package foomatic-filters
Fail creating foomatic-filters package (./usr/lib/cups/filter/foomatic-rip not 
found)

Creating package git
Fail creating git package (./usr/lib/perl5 not found)

Creating package libglib12
Fail creating libglib12 package (./lib/libglib-1.2.so.0 not found)

Creating package nano
Fail creating nano package (./usr/share/nano/man-html not found)

Creating package python
Fail creating python package (./usr/lib/python2.7/lib-dynload/_bsddb.so not 
found)

Creating package samba-extra
Package samba-extra is not configured, exiting.

Original comment by erwan....@gmail.com on 1 Nov 2012 at 4:46

GoogleCodeExporter commented 9 years ago 
Some of those errors are expectable, as the files that contains the package 
file list (e.g. ipkgfiles/nano.lst) where created on a certain point of the 
development process, and you are using trunk, which is evolving.

Other are errors. e.g. when the git package was created, there was no perl 
package, meanwhile pearl appeared and now git detects it but it is not on its 
dependency list...

samba-extra is too recent, it does not appears as configured in .config-pkgs, 
etc.

I will keep this list as a reference for when I will rebuild packages, but I 
will take no action for now.

Thanks for all your work.

Original comment by whoami.j...@gmail.com on 1 Nov 2012 at 6:34

GoogleCodeExporter commented 9 years ago 
All download URL in SVN are now fixed. But they are always changing...
As for distro/packages specific issues, please continue reporting.

Thanks for your persistence and all your work.

Original comment by whoami.j...@gmail.com on 21 Mar 2013 at 5:35