[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#284439: marked as done (dpkg-cross: [PATCH] cross-config.m32r)

Your message dated Sat, 20 May 2006 11:38:01 +0900
with message-id <446E8109.3080801@fsij.org>
and subject line Problem fixed in 1.25
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: dpkg-cross
Version: 1.20.3 (CVS 20041206)
Severity: wishlist

Cross building coreutils package, I needed bunch of configure
variables.  I think that listing existence of these variables
helps dpkg-cross development, so here is a patch (for my own purpose).

Also, this patch include fix of configure variables for DB package.

Those are actually for m32r-linux, not m32r specific.  I'm considering
proper way to handle configure variables.  For now, I put those into
cross-config.m32r.

Index: cross-config.m32r
===================================================================
RCS file: /cvsroot/dpkg-cross/dpkg-cross/cross-config.m32r,v
retrieving revision 1.1
diff -u -3 -p -r1.1 cross-config.m32r
--- cross-config.m32r	15 Nov 2004 20:49:24 -0000	1.1
+++ cross-config.m32r	6 Dec 2004 11:21:59 -0000
@@ -24,10 +24,47 @@ ac_cv_search_clock_gettime=no
 # DB3
 db_cv_alignp_t=int
 db_cv_fcntl_f_setfd=yes
-db_cv_mutex=sh/gcc-assembly
-db_cv_spinlocks=sh/gcc
 db_cv_sprintf_count=yes
+db_cv_mutex="POSIX/pthreads/library"
 # Python
 ac_cv_malloc_zero=yes
 ac_cv_opt_olimit_ok=no
 ac_cv_olimit_ok=no
+
+# Coreutils
+ac_cv_func_chown_works=yes
+ac_cv_func_closedir_void=no
+ac_cv_func_fnmatch_gnu=yes
+ac_cv_func_fnmatch_works=yes
+ac_cv_func_getcwd_null=yes
+ac_cv_func_getgroups_works=yes
+ac_cv_func_getpagesize=yes
+ac_cv_func_lstat_dereferences_slashed_symlink=yes
+ac_cv_func_lstat_empty_string_bug=no
+ac_cv_func_malloc_0_nonnull=yes
+ac_cv_func_memcmp_working=yes
+ac_cv_func_realloc_0_nonnull=yes
+ac_cv_func_stat_empty_string_bug=no
+ac_cv_func_strcoll_works=yes
+ac_cv_func_strnlen_working=yes
+ac_cv_func_strtod=yes
+ac_cv_func_utime_null=yes
+ac_cv_func_utimes_null=yes
+am_cv_func_working_getline=yes
+fu_cv_sys_mounted_getmntent1=yes
+fu_cv_sys_stat_statfs2_bsize=yes
+gl_cv_func_getcwd_vs_path_max=yes
+gl_cv_func_tzset_clobber=no
+gl_cv_func_working_readdir=yes
+gl_cv_func_working_utimes=yes
+jm_ac_cv_func_link_follows_symlink=no
+jm_cv_func_gettimeofday_clobber=no
+jm_cv_func_nanosleep_works=yes
+jm_cv_func_svid_putenv=yes
+jm_cv_func_unlink_busy_text=yes
+jm_cv_func_working_re_compile_pattern=yes
+jm_cv_have_proc_uptime=yes
+utils_cv_func_mkdir_trailing_slash_bug=no
+utils_cv_func_mkstemp_limitations=no
+utils_cv_localtime_cache=no
+vb_cv_func_rename_trailing_slash_bug=no

--- End Message ---
--- Begin Message --- 
This problem has been fixed in 1.25.

Thanks,
--

--- End Message ---
Reply to: