On 25/08/11 at 10:17 -0700, Steve Langasek wrote: > Hi there, > > On Wed, Aug 24, 2011 at 11:13:36PM +0200, Mònica Ramírez Arceda wrote: > > > During a rebuild of all packages in sid, your package failed to build on > > amd64. > > > Relevant part: > > > gcc -L/usr/lib cmd_alias.o cmd_bcp.o cmd_buf.o cmd_connect.o cmd_do.o > > > cmd_echo.o cmd_exit.o cmd_for.o cmd_func.o cmd_go.o cmd_help.o > > > cmd_history.o cmd_if.o cmd_input.o cmd_jobs.o cmd_kill.o cmd_lock.o > > > cmd_loop.o cmd_misc.o cmd_read.o cmd_reconnect.o cmd_redraw.o cmd_reset.o > > > cmd_return.o cmd_rpc.o cmd_set.o cmd_shell.o cmd_show.o cmd_sleep.o > > > cmd_wait.o cmd_warranty.o cmd_while.o var_ctlib.o var_date.o var_debug.o > > > var_dsp.o var_hist.o var_misc.o var_passwd.o var_readline.o var_thresh.o > > > dsp.o dsp_bcp.o dsp_conv.o dsp_desc.o dsp_horiz.o dsp_html.o dsp_meta.o > > > dsp_none.o dsp_out.o dsp_pretty.o dsp_vert.o dsp_x.o sqsh_alias.o > > > sqsh_args.o sqsh_avl.o sqsh_buf.o sqsh_cmd.o sqsh_compat.o sqsh_ctx.o > > > sqsh_debug.o sqsh_env.o sqsh_error.o sqsh_expand.o sqsh_fd.o > > > sqsh_filter.o sqsh_fork.o sqsh_func.o sqsh_getopt.o sqsh_global.o > > > sqsh_history.o sqsh_init.o sqsh_job.o sqsh_readline.o sqsh_sig.o > > > sqsh_sigcld.o sqsh_stdin.o sqsh_strchr.o sqsh_tok.o sqsh_varbuf.o > > > sqsh_main.o -ldl -lm -lXm -lXt -lXext -lX11 -lreadline -lcurses > > > -lreadline -o sqsh > > > cmd_bcp.o: In function `bcp_signal': > > > /build/sqsh-k3G3RC/sqsh-2.1/src/cmd_bcp.c:1102: undefined reference to > > > `ct_cancel' > > This build failure doesn't make any sense. Of course these symbols aren't > going to be found if sqsh isn't being linked against libct and libcs as in > the above commandline; but there's no reason why these should be missing. > > And I have just re-tested locally; sqsh builds fine for me here. > > So there seems to be something wrong with that rebuild environment that > causes sqsh to fail to detect libct. Is this reproducible in a retry? Can > you or anyone else reproduce this locally, and tell me why /usr/lib/libct.a > is missing or not detected?
Hi Steve, I just retried on my laptop, and it failed again (different machine, different chroot, etc). Could you diff your build log with the one from the bug report? - Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
