bug-autoconf
[Top][All Lists]
Advanced

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

Segfault while checking for suffix of executables


From: Strates, Jimmy
Subject: Segfault while checking for suffix of executables
Date: Tue, 29 Aug 2017 16:17:49 +0000

Hello Autoconf maintainers,

I seem to have an issue with my computer; this almost positively isn’t a bug in 
autoconf, but I can’t find the source.

I am using a Mac and installing packages through MacPorts; the other day, every 
package that used an autoconf configure script started segfaulting while 
“checking for suffix of executables…”. I’ve completely uninstalled everything 
in MacPorts and MacPorts, reinstalled MacPorts, and the problem persists.

I downloaded the autoconf 2.69 tarball (MacPorts is using autoconf 2.69) and 
ran the test suite with the MacPorts autoconf. The results were concerning…

[GNU Autoconf 2.69] testsuite: 1 24 226 232 233 263 264 267 268 269 270 271 272 
273 274 275 276 277 278 281 282 283 284 285 286 287 288 289 290 291 292 293 294 
295 296 297 298 299 300 301 302 303 306 307 308 311 312 313 314 315 316 317 318 
319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 
339 340 341 342 343 349 351 353 354 355 356 357 358 359 360 361 362 363 364 365 
366 367 368 369 370 371 372 374 376 379 380 382 384 385 386 387 388 390 393 394 
395 396 397 398 399 400 404 405 407 408 410 411 413 414 415 416 417 419 421 423 
424 425 426 429 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 
447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 
467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 
487 488 489 490 491 492 493 494 495 496 497 498 499 500 failed

I had similar results from building from the tarball source and testing its 
build output. the testsuite.log is attached

I would greatly appreciate if you would help me understand what is happening 
during the “checking for suffix of executables" step so that I may find the 
underlying issue. It seems to be a rather fundamental issue but I just don’t 
have the background knowledge to find it.

Thanks,
Jimmy Strates

Attachment: testsuite.log
Description: testsuite.log


reply via email to

[Prev in Thread] Current Thread [Next in Thread]