-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to build on Ubuntu 22.04 #369
Comments
I did't try Ubuntu 22.04 at all, but it looks the linker complains something. Could you provide the output of following instructions?
|
@piste-jp-ibm |
I had the same issue with the building process on Ubuntu 22.04. In my case, I tried to install Autoconf 2.69 instead of version 2.71, and It works. Maybe there's something that changed the function's name, during an update to its version. |
Hi, I just compiled the main branch (2.5) it on Ubuntu 22.04 without issues.
After you can restart the compile process from a clean cloned repository |
The link command below doesn't includes any
I don't know the exact solution for this but you can see the issue #153. In |
#376 |
That sounds good! BTW when will a new release (tag) come out? |
On a freshly installed 22.04 this worked for me on master as well as on v2.4-stable:
|
Came across this thread and actually got it working. Thank you. |
Thank you @max-aigner! I was able to install However, I was still not able to mount tapes on this system. I've tried multiple working tapes to no avail... Here's what I'm seeing.
Any help appreciated. |
This is a FAQ. Try the
Also you can find the issues below if you search the issues by |
Thanks for your response. I can confirm that configuring I'm not an experienced user of tape systems so I hadn't realized that Scrutinizing the error codes a little more, it looks like the last value is actually meaningful. I'm guessing |
It's not an error code, but a message actually. Message is injected to the entire code, so you can know which line or block is executed. The trouble shooting info is provided from IBM. Check the link below. https://www.ibm.com/docs/en/spectrum-archive-sde/2.4.1.0?topic=troubleshooting
Exactly. As ideal code and logic, |
Hi I am also using Ubuntu 22.04. My mound command, which works, is as
follows:
ltfs -o devname=/dev/sg0 /ltfsmnt
Sean.
…On Sun, 25 Feb 2024 at 21:20, Atsushi Abe ***@***.***> wrote:
It's not an error code, but a message actually. Message is injected to the
entire code, so you can know which line or block is executed.
The trouble shooting info is provided from IBM. Check the link below.
https://www.ibm.com/docs/en/spectrum-archive-sde/2.4.1.0?topic=troubleshooting
Scrutinizing the error codes a little more, it looks like the last value
is actually meaningful. I'm guessing W means Warning and E means Error. Is
I Info?
Exactly.
As ideal code and logic, W shall be used for unexpected condition that
have a possibility to recover and E shall be used for error that cannot
continue the service anymore. We tried to move to such kind of direction
but it is not perfect at all, you need to check the code if you want to
know (or understand) what happens.
—
Reply to this email directly, view it on GitHub
<#369 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABYQRPICEUXOULOFH6MMAP3YVPWOZAVCNFSM6AAAAAASNLM22OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRTGIYDKNZWGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Close this because there is no activity long time. Please feel free to reopen if something new is found. |
Describe the bug
I'm trying to build ltfs on Ubuntu 22.04 and finally blocked there
To Reproduce
Steps to reproduce the behavior:
./autogen.sh
./configure
make
Expected behavior
LTFS built successfully
Desktop (please complete the following information):
Additional context
Here's what I got from terminal:
The text was updated successfully, but these errors were encountered: