octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #62087] GPIB interface unsupported despite ins


From: Zander Borders
Subject: [Octave-bug-tracker] [bug #62087] GPIB interface unsupported despite installation of linux-gpib package
Date: Sun, 20 Feb 2022 23:20:39 -0500 (EST)

Follow-up Comment #3, bug #62087 (project octave):

[comment #1 comment #1:]
> If you execute the following commands in Octave, it should display the
pre-processor and linker flags that are used by default when compiling .oct
files:
> 
> mkoctfile -p CPPFLAGS
> mkoctfile -p LDFLAGS
> 
> 
> If the paths where you installed the gbip libraries aren't included in these
flags, try setting the corresponding environment variables before compiling
the package. E.g. in Octave:
> 
> setenv("CPPFLAGS", [strtrim(mkoctfile("-p", "CPPFLAGS")), "
-I/usr/local/include"]);
> setenv("LDFLAGS", [strtrim(mkoctfile("-p", "LDFLAGS")), "
-L/usr/local/lib"]);
> pkg install -forge instrument-control
> 
> 
> Does that help?

[comment #1 comment #1:]
> If you execute the following commands in Octave, it should display the
pre-processor and linker flags that are used by default when compiling .oct
files:
> 
> mkoctfile -p CPPFLAGS
> mkoctfile -p LDFLAGS
> 
> 
> If the paths where you installed the gbip libraries aren't included in these
flags, try setting the corresponding environment variables before compiling
the package. E.g. in Octave:
> 
> setenv("CPPFLAGS", [strtrim(mkoctfile("-p", "CPPFLAGS")), "
-I/usr/local/include"]);
> setenv("LDFLAGS", [strtrim(mkoctfile("-p", "LDFLAGS")), "
-L/usr/local/lib"]);
> pkg install -forge instrument-control
> 
> 
> Does that help?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62087>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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