Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1417220 - Cast from pointer to integer of different size error when compiling ntirpc module on a i386 arch
Summary: Cast from pointer to integer of different size error when compiling ntirpc mo...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: nfs-ganesha
Classification: Retired
Component: ntirpc
Version: devel
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Matt Benjamin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-27 15:04 UTC by Victoria Martinez de la Cruz
Modified: 2020-06-24 11:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-24 11:21:52 UTC


Attachments (Terms of Use)
nfs-ganesha build trace on a i386 OS (52.97 KB, text/plain)
2017-01-27 15:04 UTC, Victoria Martinez de la Cruz
no flags Details

Description Victoria Martinez de la Cruz 2017-01-27 15:04:38 UTC
Created attachment 1245158 [details]
nfs-ganesha build trace on a i386 OS

Description of problem:

When trying to compile the ntirpc module on a i386 OS a casting error is hit. The attached trace adds more context.


Version-Release number of selected component (if applicable):


How reproducible: Always reproducible.


Steps to Reproduce:
1. Spin up a machine with an i386 OS
2. Try to follow installation instructions from https://github.com/nfs-ganesha/nfs-ganesha/wiki/BuildingV2#Building_Version_20

Actual results: Compilation error when trying to build the ntirpc module


Expected results: NFS-Ganesha build and installation


Additional info:

Comment 1 Kaleb KEITHLEY 2020-06-24 11:21:52 UTC
If this is still an issue please open an issue in the github tracker at https://github.com/nfs-ganesha/nfs-ganesha/issues


Note You need to log in before you can comment on or make changes to this bug.