From: SourceForge.net <no...@so...> - 2006-01-28 21:35:33
|
Bugs item #1417614, was opened at 2006-01-28 16:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: build problems Status: Open Resolution: None Priority: 5 Submitted By: Pedro F. Giffuni (giffunip) Assigned to: Sam Steingold (sds) Summary: amd64 not the same as x86_64 ? Initial Comment: Hi; I am trying to build CLISP 2.37 in amd64-FreeBSD6. FreeBSD reports it self as amd64, not x86_64 as linux does: etoile# uname -m amd64 and this causes problems when building: ... gmake: *** No rule to make target `avcall-amd64.lo', needed by `avcall.lo'. Stop. *** Error code 2 Stop in /usr/ports/lang/clisp/work/clisp-2.37/amd64-portbld-freebsd6.0. *** Error code 1 ___________ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-01-31 15:21:56
|
Bugs item #1417614, was opened at 2006-01-28 22:35 Message generated for change (Comment added) made by hoehle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: build problems Status: Open Resolution: None Priority: 5 Submitted By: Pedro F. Giffuni (giffunip) Assigned to: Sam Steingold (sds) Summary: amd64 not the same as x86_64 ? Initial Comment: Hi; I am trying to build CLISP 2.37 in amd64-FreeBSD6. FreeBSD reports it self as amd64, not x86_64 as linux does: etoile# uname -m amd64 and this causes problems when building: ... gmake: *** No rule to make target `avcall-amd64.lo', needed by `avcall.lo'. Stop. *** Error code 2 Stop in /usr/ports/lang/clisp/work/clisp-2.37/amd64-portbld-freebsd6.0. *** Error code 1 ___________ ---------------------------------------------------------------------- >Comment By: Jörg Höhle (hoehle) Date: 2006-01-31 16:21 Message: Logged In: YES user_id=377168 No help at all, but may I suggest adding a category "ffcall" to the bug tracker, Sam? Some issues would go there. If you add an entry to the Makefiles, does it continue and pass tests? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-01-31 21:26:54
|
Bugs item #1417614, was opened at 2006-01-28 16:35 Message generated for change (Settings changed) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: build problems Status: Open Resolution: None Priority: 5 Submitted By: Pedro F. Giffuni (giffunip) >Assigned to: Bruno Haible (haible) Summary: amd64 not the same as x86_64 ? Initial Comment: Hi; I am trying to build CLISP 2.37 in amd64-FreeBSD6. FreeBSD reports it self as amd64, not x86_64 as linux does: etoile# uname -m amd64 and this causes problems when building: ... gmake: *** No rule to make target `avcall-amd64.lo', needed by `avcall.lo'. Stop. *** Error code 2 Stop in /usr/ports/lang/clisp/work/clisp-2.37/amd64-portbld-freebsd6.0. *** Error code 1 ___________ ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-01-31 10:21 Message: Logged In: YES user_id=377168 No help at all, but may I suggest adding a category "ffcall" to the bug tracker, Sam? Some issues would go there. If you add an entry to the Makefiles, does it continue and pass tests? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-02-06 19:42:49
|
Bugs item #1417614, was opened at 2006-01-28 16:35 Message generated for change (Comment added) made by giffunip You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: build problems Status: Open Resolution: None Priority: 5 Submitted By: Pedro F. Giffuni (giffunip) Assigned to: Bruno Haible (haible) Summary: amd64 not the same as x86_64 ? Initial Comment: Hi; I am trying to build CLISP 2.37 in amd64-FreeBSD6. FreeBSD reports it self as amd64, not x86_64 as linux does: etoile# uname -m amd64 and this causes problems when building: ... gmake: *** No rule to make target `avcall-amd64.lo', needed by `avcall.lo'. Stop. *** Error code 2 Stop in /usr/ports/lang/clisp/work/clisp-2.37/amd64-portbld-freebsd6.0. *** Error code 1 ___________ ---------------------------------------------------------------------- >Comment By: Pedro F. Giffuni (giffunip) Date: 2006-02-06 14:42 Message: Logged In: YES user_id=678384 Hi again; Not that I'm too sure how the clisp build works but this patch seems necessary. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-01-31 10:21 Message: Logged In: YES user_id=377168 No help at all, but may I suggest adding a category "ffcall" to the bug tracker, Sam? Some issues would go there. If you add an entry to the Makefiles, does it continue and pass tests? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-02-28 09:44:47
|
Bugs item #1417614, was opened at 2006-01-28 22:35 Message generated for change (Comment added) made by hoehle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: ffcall Group: build problems Status: Open Resolution: None Priority: 5 Submitted By: Pedro F. Giffuni (giffunip) Assigned to: Bruno Haible (haible) Summary: amd64 not the same as x86_64 ? Initial Comment: Hi; I am trying to build CLISP 2.37 in amd64-FreeBSD6. FreeBSD reports it self as amd64, not x86_64 as linux does: etoile# uname -m amd64 and this causes problems when building: ... gmake: *** No rule to make target `avcall-amd64.lo', needed by `avcall.lo'. Stop. *** Error code 2 Stop in /usr/ports/lang/clisp/work/clisp-2.37/amd64-portbld-freebsd6.0. *** Error code 1 ___________ ---------------------------------------------------------------------- >Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 10:44 Message: Logged In: YES user_id=377168 It's nice that a one-line patch to clisp/src/makemake.in fixes the build problem (surprising indeed!). Nevertheless, I believe the ffcall package must stand on its own and be prepared for the amd64 platform (i.e. CL_CANONICAL_HOST_FOR_FFCALL in ffcall/m4/general.m4 ought to be expanded, from what I understand). Therefore, I've changed the category of this bug report to ffcall. ---------------------------------------------------------------------- Comment By: Pedro F. Giffuni (giffunip) Date: 2006-02-06 20:42 Message: Logged In: YES user_id=678384 Hi again; Not that I'm too sure how the clisp build works but this patch seems necessary. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-01-31 16:21 Message: Logged In: YES user_id=377168 No help at all, but may I suggest adding a category "ffcall" to the bug tracker, Sam? Some issues would go there. If you add an entry to the Makefiles, does it continue and pass tests? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-02-28 14:08:36
|
Bugs item #1417614, was opened at 2006-01-28 16:35 Message generated for change (Comment added) made by giffunip You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: ffcall Group: build problems Status: Open Resolution: None Priority: 5 Submitted By: Pedro F. Giffuni (giffunip) Assigned to: Bruno Haible (haible) Summary: amd64 not the same as x86_64 ? Initial Comment: Hi; I am trying to build CLISP 2.37 in amd64-FreeBSD6. FreeBSD reports it self as amd64, not x86_64 as linux does: etoile# uname -m amd64 and this causes problems when building: ... gmake: *** No rule to make target `avcall-amd64.lo', needed by `avcall.lo'. Stop. *** Error code 2 Stop in /usr/ports/lang/clisp/work/clisp-2.37/amd64-portbld-freebsd6.0. *** Error code 1 ___________ ---------------------------------------------------------------------- >Comment By: Pedro F. Giffuni (giffunip) Date: 2006-02-28 09:08 Message: Logged In: YES user_id=678384 Actually ..the patch doesn't fix anything..I'll remove it. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 04:44 Message: Logged In: YES user_id=377168 It's nice that a one-line patch to clisp/src/makemake.in fixes the build problem (surprising indeed!). Nevertheless, I believe the ffcall package must stand on its own and be prepared for the amd64 platform (i.e. CL_CANONICAL_HOST_FOR_FFCALL in ffcall/m4/general.m4 ought to be expanded, from what I understand). Therefore, I've changed the category of this bug report to ffcall. ---------------------------------------------------------------------- Comment By: Pedro F. Giffuni (giffunip) Date: 2006-02-06 14:42 Message: Logged In: YES user_id=678384 Hi again; Not that I'm too sure how the clisp build works but this patch seems necessary. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-01-31 10:21 Message: Logged In: YES user_id=377168 No help at all, but may I suggest adding a category "ffcall" to the bug tracker, Sam? Some issues would go there. If you add an entry to the Makefiles, does it continue and pass tests? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-04-26 13:22:17
|
Bugs item #1417614, was opened at 2006-01-28 22:35 Message generated for change (Comment added) made by haible You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: ffcall Group: build problems >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Pedro F. Giffuni (giffunip) Assigned to: Bruno Haible (haible) Summary: amd64 not the same as x86_64 ? Initial Comment: Hi; I am trying to build CLISP 2.37 in amd64-FreeBSD6. FreeBSD reports it self as amd64, not x86_64 as linux does: etoile# uname -m amd64 and this causes problems when building: ... gmake: *** No rule to make target `avcall-amd64.lo', needed by `avcall.lo'. Stop. *** Error code 2 Stop in /usr/ports/lang/clisp/work/clisp-2.37/amd64-portbld-freebsd6.0. *** Error code 1 ___________ ---------------------------------------------------------------------- >Comment By: Bruno Haible (haible) Date: 2006-04-26 15:22 Message: Logged In: YES user_id=5923 FreeBSD reports itself as amd64, but clisp uses the output of GNU config.guess. A bug was reported about this to config-patches at gnu period org. They changed config.guess to report x86_64-unknown-freebsd6 instead of amd64-unknown-freebsd6. The updated config.guess was imported into clisp and ffcall. It should now work fine. (Untested. Can you test the clisp CVS?) ---------------------------------------------------------------------- Comment By: Pedro F. Giffuni (giffunip) Date: 2006-02-28 15:08 Message: Logged In: YES user_id=678384 Actually ..the patch doesn't fix anything..I'll remove it. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 10:44 Message: Logged In: YES user_id=377168 It's nice that a one-line patch to clisp/src/makemake.in fixes the build problem (surprising indeed!). Nevertheless, I believe the ffcall package must stand on its own and be prepared for the amd64 platform (i.e. CL_CANONICAL_HOST_FOR_FFCALL in ffcall/m4/general.m4 ought to be expanded, from what I understand). Therefore, I've changed the category of this bug report to ffcall. ---------------------------------------------------------------------- Comment By: Pedro F. Giffuni (giffunip) Date: 2006-02-06 20:42 Message: Logged In: YES user_id=678384 Hi again; Not that I'm too sure how the clisp build works but this patch seems necessary. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-01-31 16:21 Message: Logged In: YES user_id=377168 No help at all, but may I suggest adding a category "ffcall" to the bug tracker, Sam? Some issues would go there. If you add an entry to the Makefiles, does it continue and pass tests? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1417614&group_id=1355 |